Interview scored
A candidate finishes and the report is ready. The card shows the role, the AI-advice score and the integrity status, so the right person picks it up.
CRITICAL HIVE Microsoft Teams EARLY ACCESS
Your team lives in Teams. Critical Hive posts a short card to the channel you choose when an interview is scored, a candidate asks for a person, an interview is booked, or an integrity signal needs a look. One way, no candidate emails, and a person still makes every hiring decision.
ILLUSTRATIVE
01 What gets posted
Choose which events post a message. Each card is short and links back to the report.
A candidate finishes and the report is ready. The card shows the role, the AI-advice score and the integrity status, so the right person picks it up.
A candidate chose to speak with a person instead of the AI. No request sits unread in someone's inbox.
When a candidate books, reschedules or cancels an interview you offered, the channel knows straight away.
A scored interview with a high-risk signal is called out on its own, with a reminder to read the integrity report before relying on the result.
Include the candidate's name, or switch it off and cards say “A candidate”. Email addresses, transcripts and video are never included either way.
The last messages and their outcome are listed in Critical Hive, including a plain-language reason if one could not be delivered.
02 How it works
In the channel, add a Workflows flow with the template “Post to a channel when a webhook request is received”, and copy its web address. An older Incoming Webhook address also works.
Under Integrations, open the Microsoft Teams tab and paste the address. It is stored encrypted and is not shown again. Only Microsoft webhook addresses are accepted.
Switch on the events you want and decide whether names appear. Save, then send a test message to confirm the channel receives it.
Cards arrive as things happen. Anyone with access follows the link, signs in and reads the evidence. Decisions are made in Critical Hive, not in Teams.
03 Safe by design
STATUS
Channel notifications: built and tested against a simulated Teams webhook receiver, covering card content, event switches, names on and off, failures and disconnecting. Send the built-in test message to confirm it works with your own channel.
Teams meeting links: an optional setting that adds a Microsoft Teams link to interviews booked through Critical Hive, when a Microsoft 365 calendar is connected. That calendar connection is also early access.
Not built: a Teams bot, chat commands, decisions or approvals inside Teams, and single sign-on through Teams.
Scheduling & calendar connection04 FAQ
Microsoft Teams is a trademark of Microsoft. Critical Hive is not affiliated with or endorsed by Microsoft. See also our Workday integration.
It posts a short card into a Teams channel you choose when something needs your team's attention: an interview is scored, a candidate asks for a human interview, an interview is booked, moved or cancelled, or an interview carries a high-risk integrity signal. Each card links back to the report in Critical Hive.
No. It is one direction only. Critical Hive posts to a webhook that you create in Teams, and nothing is read from Teams. There is no bot, no chat commands and no access to your messages or files.
No. A card tells your team something happened and links to the report. Recruiters and hiring managers read the evidence and decide in Critical Hive. The AI never moves or rejects a candidate.
A short title and sentence, the role, the AI-advice score and integrity status where relevant, and a link to open the report (which needs a Critical Hive sign-in). A candidate's name is included only if your admin allows it, and you can switch it off so cards say “A candidate”. Email addresses, transcripts and video are never included.
In Teams, add a Workflows flow with the template “Post to a channel when a webhook request is received” for the channel you want, and copy its web address. Paste it into Critical Hive under Integrations, choose the events, and send a test message. An older Incoming Webhook connector address also works.
Anyone holding a webhook address can post to the channel, so Critical Hive treats it as a secret: it is stored encrypted and is never shown again. Only Microsoft webhook addresses are accepted, messages are limited to 60 an hour per workspace, and you can disconnect at any time and delete the webhook in Teams as well.
Nothing breaks. Interviews, reports and bookings carry on, and the failure is shown in a recent-messages log with a plain explanation, for example that the webhook no longer exists.
For human interviews booked through Critical Hive, an optional setting adds a Microsoft Teams meeting link to the booking when a Microsoft 365 calendar is connected. That calendar connection is in early access. The AI interview itself runs in the candidate's browser and does not use Teams.
It is in early access. The behaviour, including card content, event switches, failure handling and security rules, is tested against a simulated Teams webhook receiver. Use the built-in test message to confirm it works with your own channel before relying on it.
Try the Teams notifications in a free workspace. The test message tells you in seconds whether your channel is wired up.