What HireQwik Slack and Teams Alerts Actually Send

AI screening Slack Teams alerts exist so a top verdict is not stuck in a closed tab until evening. That showed up on a Wednesday in June, in a Hyderabad office where the TA lead was in back-to-back campus panels. Three voice screens had already finished before lunch. The verdicts were on the HireQwik dashboard. Nobody had looked. She found them at 7:40 p.m., after two of the three candidates had stopped answering.

The screen itself was not the delay. The delay was the gap between “the call ended” and “a human noticed.” SHRM’s 2026 recruiting brief puts median time-to-fill for nonexecutive roles at 39 calendar days, across data from more than 4,600 organizations. That number is the whole funnel. The hour after a strong screen is a much smaller slice, and it is the slice a chat ping can actually protect.

What a HireQwik Slack or Teams alert is for

HireQwik already writes the outcome into the inbox. A recruiter who lives in that inbox does not need a second copy. Most TA leads do not live there. They live in a hiring channel, a placement war-room, or a Teams room that also holds the offer spreadsheet.

The alert is a nudge into that room. It is not another scorecard. Debate belongs in the app, not in the channel. The useful version is short enough that a lead can read it between panels and decide whether to open the app.

From March through April 2026 the pilot’s finished voice screens came to 1,099, spread over 14 campaigns. Review still depended on someone opening the queue. A ping does not judge the person. It stops that queue from being invisible.

The HireQwik events that can reach a channel

On Setup, then Notifications, an admin can turn on a short list of events. Three of them are about candidates. They start switched off. Saving a webhook with every box unticked will not tell you about a hire.

High-score alert. This one fires when a resume row is ingested and the match score clears a line the admin sets. The default line is 0.85, which is 85 percent. It is a resume-match ping, not an interview verdict. The moment is early: the sheet has been read, the score exists, the voice call may not have happened yet.

Booking confirmed. This fires when the candidate picks a slot. It is the “they showed up in the calendar” note, useful when a coordinator is chasing no-shows and needs to know who actually booked.

Candidate screened. This fires when a voice interview is first marked screened. If a verdict exists, the line names it. A later pass over the same finished row does not send a second copy. That matters on a drive where someone regenerates a score: the channel should not fill with repeats of a call you already saw.

A fourth hiring note is optional and easy to confuse with the three above. Each role can email its owner a morning roundup, nine o’clock India time unless you change the hour, plus a poke when positive interview outcomes have stacked up with nobody deciding. Mirroring that note into chat is its own tick, and that tick also starts off. The mailbox can be busy while the channel stays quiet.

Credit warnings are different again. Low balance, exhausted balance, spend bands, and expiry start on, because a stalled screen is a billing problem, not a candidate problem. If the only messages you see are about credits, the candidate ticks are still off.

What the HireQwik chat message includes

I have watched teams expect a mini profile in Slack and then feel let down. The Slack and Teams text is deliberately thin.

A screened candidate reads as the name, which opening, and the outcome, then a link. If there is no verdict yet, the line falls back to a match percent. A high-score row reads as the name, the percent, and the role, then the same kind of link. A booking line says they booked a slot for that role.

What is not in the chat text: the resume, the transcript, the phone number, the email address. A custom webhook is a different sink. That payload can carry the email and is signed so the receiving system can check it came from HireQwik. The Slack message and the Teams card do not.

The link is the point. If the event has a meeting id, it opens that meeting. Otherwise it opens the resume row. Whoever clicks still has to be allowed to see that candidate. A channel full of people is not a permission grant. How scorecards are shared with a hiring manager is the path for someone who should read one person and should not have a workspace login.

Slack’s own webhook docs describe an incoming webhook as a URL that posts a JSON body into one channel. HireQwik uses that shape. You create the URL in Slack, pointed at the channel you want, and paste that URL. You do not paste a browser link to the channel.

Why HireQwik candidate alerts start switched off

An empty channel after a successful save is the most common “it is broken” report I get, and it is often not broken. The three candidate events default to off so a new workspace does not dump every booking into a general channel on day one.

The order that works:

1. Add a sink. Pick Slack or Microsoft Teams. Paste one webhook URL. Leave it enabled.
2. Tick only the events you will act on this week. For a drive that is already interviewing, that is usually Candidate screened. For a sheet that is still landing, add the high-score alert.
3. Save.
4. Press Send test. The sample is obviously fake, and the text says so. It fires immediately, and it ignores the event ticks, so you can prove the address while those ticks are still off.

If Send test lands and a genuine top verdict does not, the event tick is the next place to look, not the URL.

Where a HireQwik alert link actually opens

The channel is shared. The record is not. I care about that split because the hiring room often includes a founder, a coordinator, or an agency partner who should not browse every applicant.

The message gives them a name and a reason to care. The app gives them the rest, if their seat allows it. A member’s list is the jobs assigned to them, together with any job that still has no owner. An admin sees the organisation. Clicking a link you are not allowed to open does not quietly widen your seat.

There is a boring week-one habit that prevents the mute. For the first five interviewing days, keep one event only, and ask the TA lead each evening whether the ping changed a decision or only added noise. If it only added noise, drop that event. A channel people trust is worth more than a complete log.

That is also why the destination is workspace-wide. Several recruiters on one HireQwik workspace still share one alert setup. The admin picks the channel once. A recruiter cannot point their own roles at a private room the rest of the team cannot see. If you need a hiring manager to read one person, send the scorecard. Do not add them to the alert channel to solve a single review.

A dead HireQwik webhook does not stop the screen

This part is easy to miss, and it is the right failure. If Slack is down, the URL is wrong, or the channel was archived, the interview still scores. Booking still confirms. The sheet still ingests. The alert is fire-and-forget. A broken ping must never become a broken screen.

The cost of that choice is silence. HireQwik will not pop an error inside the candidate’s call because your webhook 404’d. The only honest check is Send test, which reports each sink as ok or not. Trust that result over the Saved banner.

The HireQwik switches I would leave on

For a team that already runs voice screens, I would leave Candidate screened on, pointed at one private hiring channel, and leave Booking confirmed off unless a coordinator is actively chasing the calendar. I would turn the high-score alert on only after someone has looked at a day’s score spread and chosen a line. The default 0.85 is only where the box begins, not a promise that 85 percent means “call them now” for every role.

I would leave the digest email on, because it is the morning list, and I would copy it into chat only if the channel is not already noisy. Credit warnings can stay on. They are rare, and a screen that stops for lack of credits is worse than one extra message.

If you want this wired before the next drive, book a walkthrough from the demo form and bring the channel name with you. The setup is short. The decision is which events deserve a human’s attention, and that decision should be yours, not a default.