#hiring · Connected

Your turn arrives as a DM that says why it's you.

Review and decide without leaving Slack: a private channel for each application, a checkmark to advance, an X to start a rejection, and @KitBot for the summary. Each security report gets a thread of its own, and the DM that pulls you in names the stage or role that made it your turn.

Included in every seat @KitBot reads history only in channels it belongs to. Your DMs and other channels stay private.

The alert should lead to a decision.

Application alerts are easier to use when the discussion and next action stay with them.

Updates pile up in the hiring channel.

Separate posts for every stage change, review, and interview make it harder to follow one candidate.

A small decision takes several steps.

An alert arrives in Slack. You open the ATS, find the candidate, take action, then return to tell the team.

Feedback gets separated from the record.

A teammate shares useful feedback in Slack, but someone still has to copy it to the candidate record.

Threaded hiring notifications

One application. One Slack thread.

A new application creates one card. Later events become replies beneath it, so you can follow the history without searching the channel.

  • A new application creates the root message in the channel you chose.
  • Stage moves, reviews, interviews, candidate replies, offers, rejections, and withdrawals stay in the same thread.
  • Open one thread to see what changed, who acted, and where the candidate stands.

Six hiring events. One channel post. The context stays attached without filling #hiring with alerts.

Give each application a private team channel.

When a candidate moves past their first stage, a private channel opens with the hiring team invited and the candidate's details pinned. The candidate cannot join. Rejection or withdrawal archives the channel.

  • Created when a candidate passes their first stage
  • Pinned card with stage, source, and fields AI pulled from the resume; ask @KitBot for a full summary
  • Hiring team auto-invited to the channel
  • Quick links to candidate profile and job posting
  • Auto-archived on rejection or withdrawal

Open a private channel for your next candidate.

A channel opens when a candidate passes the first stage.

Get started free

React to advance, reject, or leave a signal.

In a candidate channel, a checkmark advances and an X starts a confirmed rejection; thumbs, eyes, and the hourglass leave a note. In your hiring channel, a thumbs-up advances and a thumbs-down rejects, both after you confirm. Every action is saved with your name.

React to take action

Sarah Chen advanced to Phone Screen

Confirmation requested: React with X again to reject Sarah Chen

Rejection requires a second reaction to confirm.

Signal noted: Positive impression from Alex

Signal noted: Concern flagged by Alex

Signal noted: Under review by Alex

Signal noted: On hold by Alex

Try emoji actions

Actions appear on the candidate's timeline in Kit.

#hire-sarah-chen
Answers in the channel

Ask @KitBot about the candidate.

Mention @KitBot to read application details, review scores, and stage history. Request a stage change or save a note in the thread. Notes appear in Kit with the author and a 'via Slack' label.

Candidate tools

Summarize candidate Get review scores List applications Advance candidate Save note More candidate tools

What Kit brings to Slack.

Check what your team can read and do from Slack, and which permissions each feature needs.

Capability Kit What to check elsewhere
Application updates One thread per application Do updates stay in one thread?
Candidate channels Auto-created, candidate card pinned Who creates and archives channels?
In-channel assistant @KitBot with candidate tools Can it read the candidate record?
Emoji workflow Advance, reject, signal Which reactions change a record?
Home Tab dashboard Priority queue with interviews Can you see today's interviews?
Pricing Included in every seat Is the integration an extra charge?

Keep hiring updates where your team reads them.

Find today's work, route applications by role, and read each candidate's history in one thread.

Today's work in the Home Tab

See today's interviews and join links, pending reviews, and candidates waiting for a decision. On-call members also see security alerts.

One thread for the application history

Stage changes, reviews, interviews, offers, rejections, and withdrawals appear beneath the original application card. Updates stay in that thread even if channel routing changes later.

Candidate details in the card

Read candidate details, profile links, resume summaries, and action buttons in the message.

Per-job channel routing

Route engineering applications to #eng-hiring, sales to #sales-hiring. A setup wizard suggests channels. A fallback catches everything else.

One Slack connection for hiring, security, and outreach

Use the same Slack connection for hiring updates, security report cards, and outreach replies.

Connect your Slack workspace.

Choose permissions, route notifications, then enable candidate channels.

1

Connect your workspace

Click Add to Slack, choose an access level, and approve the permissions listed by Slack.

2

Choose your channels

Use the suggested channels or choose your own. Route notification types separately or send them to one channel.

3

Turn on candidate channels

Turn on candidate channels in Settings. Each one opens when a candidate passes their first stage.

Choose what Kit can access in Slack.

Notifications only

Posts to the public channels you select. Kit cannot read messages, see private channels, or look up members.

Collaboration

Adds personal DMs, member lookup by email, @KitBot mentions, and emoji-reaction actions. Still no access to private channels.

Full

Needed for candidate channels

Adds private candidate channels, pinned summaries and bookmarks, and the channel history that gives @KitBot its thread context.

Your Slack admin can grant fewer permissions than a level requests. Kit enables features based on the permissions granted.

Keep the discussion with the candidate record.

Candidate channels connect your team's Slack discussion to the application record. Summaries, reviews, and decisions stay accessible from the same thread.

Beyond hiring

Security reports get the same treatment.

Turn on Security and each new report gets a card in your security channel; restricted reports stay out of Slack. Assign and acknowledge from the card, with updates kept in its thread.

  • One report, one live card updated in place, with the full record in its thread
  • Acknowledge stops the acknowledgment clock. Appeals get their own decision buttons, and the reminder DM lets you snooze a stalled report
  • Every action checks your linked Slack identity and Kit permissions
See how Kit handles security reports
#security-reports
K
Kit APP 9:02 AM

New report: Stored XSS in the invite flow

High First response due in 6h
Assign to me Acknowledge View report
Kit 9:14 AM

Maya Torres acknowledged the report. SLA clock stopped.

Permissions, channels, and stray emoji.

What permissions does the Slack app request?

Choose an access level when you install. Notifications only can post to selected public channels. Collaboration adds direct messages, member lookup, mentions, and emoji actions. Full adds private candidate channels and history access for channels Kit belongs to. The consent screen lists the permissions before you approve them.

Does @KitBot have access to all our Slack messages?

No. @KitBot responds when mentioned and reads the surrounding thread for context. It can read history only in channels Kit belongs to, including candidate channels and channels you invite it to. It cannot read your DMs or other channels.

Will candidate channels clutter our workspace?

A channel opens only once a candidate passes their first stage, and it archives automatically when the candidate is rejected or withdraws.

What happens if someone accidentally reacts with the wrong emoji?

Rejection always asks for a second reaction on a confirmation message. In a candidate channel, a checkmark advances right away and notifies the candidate; in your hiring channel, a thumbs-up asks you to confirm first. Signal reactions in a candidate channel (thumbs, eyes, hourglass) leave a note without changing the stage.

Can I route different jobs to different channels?

Yes. Route each job posting to its own channel: engineering to #eng-hiring, sales to #sales-hiring. A fallback "all" channel catches everything else. Restricted postings never post to Slack.

Can I use emoji reactions without candidate channels?

Yes. On new-application cards in your hiring channel, a thumbs-up advances and a thumbs-down rejects, each after you confirm. There, other emoji do nothing. Candidate channels add the checkmark, the X, and signal reactions that leave a note.

Do I need a paid Slack plan?

No. Works with Slack's free plan. The only limit is Slack's own message-history cap on free plans.

Can I manage candidates directly in Slack?

Yes. Read summaries and reviews, check scores, advance candidates, reject with confirmation, and save notes. Kit records these actions on the candidate's timeline.

Review your next candidate in Slack.

Start a 30-day free trial (card required) and connect your workspace. Cancel anytime.

Candidate channels, @KitBot, and emoji actions. Included in every seat.

Connect Slack