Microsoft Teams AI Interview Alerts Without Adding Slack

Microsoft Teams AI interview alerts are how a GCC hiring room hears that a screen finished without installing a second chat tool for one vendor. A TA manager in Chennai told me this plainly last monsoon: “We will not roll out Slack so your product can say hello.” Their recruiters, the hiring managers, and the offer tracker already lived in one Teams channel. If the verdict did not show up there, it did not show up.

That constraint is common in Indian IT services and in captive centres. Slack is not the default room. Teams is. HireQwik can post into either. The Teams path has one trap that Slack does not, and it got sharper in 2026.

Why a Teams-only team still gets HireQwik interview results

You do not install a HireQwik bot from the Teams app store and hope. You create a webhook for the channel, paste that address into HireQwik, and choose which events may use it. The same notifications page covers Slack and Teams. The sink type is a dropdown. Pick Microsoft Teams, paste one URL, save.

The event that matches “the interview is done” is Candidate screened. It fires on the first move into the screened state. The card names who sat the screen, the job title, and the outcome label if that label is already stored. Running the evaluator again on that same meeting does not post a second card, so a regenerated score does not flood the room.

If you also want a note when someone books a slot, that is a different tick, Booking confirmed. If you want a note when a resume first clears a match line, that is the high-score alert, and it is about the resume, not the call. A Teams room that is already busy should not take all three on the first day. Start with the event someone will act on before lunch.

The shape of these HireQwik messages is the same idea in Slack. This page is the Teams-specific way the address is born, and why an old address dies quietly.

Which Teams address HireQwik will accept

HireQwik checks the host. Two hosts pass: webhook.office.com, and logic.azure.com. Anything else is refused on save, which is what you want. A link you copied from the Teams channel bar is not a webhook, and it should not be stored as one.

The host check is not the whole story. Microsoft has been retiring Office 365 connectors inside Teams. Their developer blog says the final cutoff rolled out from 18 May 2026 through 22 May 2026, and that connector-based webhooks had to move to Power Automate Workflows before that window. The write-up is Retirement of Office 365 connectors within Microsoft Teams.

So a webhook.office.com URL can still pass HireQwik’s host check and then deliver nothing, because Microsoft stopped accepting it. The address you want in October 2026 is the Workflows one, on logic.azure.com. In Teams, use the Workflows app and a template that posts to a channel when a webhook request is received. Copy that URL once. Clear the HireQwik field. Paste it once. Ask the IT owner which channel that flow may post into before you save it. A flow pointed at a team the recruiters cannot open is a green test in the wrong room.

Microsoft’s webhook overview is the background if your IT team asks why the old connector page is gone. You do not need to build a Teams app. You need one incoming address for one channel.

HireQwik sends Teams a simple MessageCard whose body is the same text Slack would get. Workflows can render that text. Do not expect buttons on the card. There are none. The action is the link.

What a finished HireQwik interview looks like in the channel

Picture a private channel called Hiring Voice. An admin has Candidate screened on, and nothing else about candidates. A screen of about 15 to 20 minutes ends. Within minutes, once the score exists, Teams shows a short card: the candidate’s name, the role title, the verdict, and a link that opens the meeting inside HireQwik.

A Strong Go in that card means the same thing it means in the product: the interview verdict, not a compliment. Someone still has to decide. The card does not approve them, does not mail them, and does not show the transcript to everyone in the channel.

If the meeting id is present, the link opens meeting details. People who click and lack access see the access rule, not a back door. That matters in a GCC channel that includes a business head who should not scroll every applicant. Give that person a single shared scorecard when they need one person. Keep the webhook pointed at the recruiter room.

A campus-style overnight resume ping is a different event and a different sentence. If your Teams room is for interview outcomes, leave the resume line off or you will train the room to ignore cards. The campus cut of these alerts is for the sheet-and-morning pattern. Do not mix it into an interview channel just because both can use Teams.

How to prove the HireQwik Teams sink before a live drive

Save is not proof. Send test is proof.

An admin presses Send test. HireQwik tries every destination that is switched on and reports ok or not for each. The text is placeholder copy about a person who does not exist. It runs without a finished call, and the Candidate screened tick can still be empty. Prove the pipe first. Turn the live event on after the placeholder shows up in the room you expect.

If the test is not ok, do not start the drive and “watch for the first candidate.” Fix the URL. The usual Teams causes, in the order I would check them:

1. The URL is an old Office connector on webhook.office.com, retired on Microsoft’s side.
2. The address was pasted over itself. HireQwik refuses a box that holds two web addresses stuck together. A single wrong address can still be saved, which is why the test exists.
3. The Workflows flow was saved against a channel the recruiter cannot see, or the flow is turned off inside Power Automate.
4. The sink row in HireQwik is disabled. A disabled row is stored and does not fire.

A failed test does not damage the interview. Scoring does not wait on Teams. The risk is only that you believe you are covered when the room is silent.

One HireQwik destination, even when five recruiters hire

Teams makes it tempting to build a channel per recruiter. HireQwik’s alert setup does not follow that map. An admin chooses the sinks for the organisation. A member cannot retarget them. The point is one place the team hears that a screen finished, including for a role whose owner is on leave.

Role ownership still matters inside the app. It decides whose inbox shows the candidate. It does not decide which Teams channel gets the card. If north and south must not see each other’s names, do not put both drives on the same webhook. Use the digest email to each role owner, and keep the Teams card for the drive that is truly shared.

Who can change workspace settings is the access question. Notifications sit with the admin, next to other workspace-wide settings. When an admin leaves, the remaining admin needs to know which Teams flow they connected. Write the channel name in your runbook. The URL itself is a secret. Do not paste it into the same channel it posts to.

What I would hand a GCC TA lead on day one

Create a private Teams channel that only the recruiting pod can read. Build a Workflows webhook into that channel. In HireQwik, add one Microsoft Teams sink, paste the logic.azure.com address, tick Candidate screened, save, and send the test. Leave Booking confirmed off until a coordinator asks for it. Leave the high-score alert off until you have seen a day’s resume spread. Leave credit warnings on. They are not interview noise. Finding out at 6 p.m. that screens halted for a balance reason is a worse surprise than one billing note.

Teams will show these cards under the Flow bot name. HireQwik does not paint a custom avatar onto that card. Judge delivery by the words, not by the icon. A plain bot picture with the right sentence is a success.

Then do one real interview on a demo role and confirm the verdict card arrives once. If it arrives twice, something else is posting. HireQwik’s screened event is built not to repeat for the same completed row.

If IT has to approve Workflows, start that ticket before the drive, not on the morning the first panel sits down. The demo form is the right place to ask us to sit in on that test. Bring the channel name. Do not bring the webhook URL into email if you can avoid it. We can watch the test result from the product without the secret sitting in an inbox.