Threll.ai
Integration and telephony platform

A voice agent is going into Teams. The checklist before you connect it.

Microsoft has started certifying voice agents for Teams Phone – and in the same document drew a line around which setups it will support. For any business running its telephony in Teams, that is a clause in the contract before it is a new feature.

4 min read
Close-up of a man in a dark shirt standing at an office staff kitchen counter, listening with a mobile phone to his ear, afternoon light through the blinds striping his cheek while two colleagues talk out of focus behind him

For most businesses, the switchboard is no longer something you buy from a telecoms supplier. It is Teams. The number sits in Teams Phone, the queues are Teams queues, and the people who answer are in the same client they hold their meetings in.

The question about a voice agent is therefore not only which agent you should have. It is what happens inside Teams when it answers – and who clears up when it doesn't work.

On 17 August, AudioCodes' Voca CIC was certified for Microsoft's Teams Unify integration model for Voice Agents, among the first solutions under the new Microsoft Teams Voice Agent Certification Program. The certification covers the agent answering incoming calls, providing information, authenticating callers and capturing intent – and then routing the call to the right Teams Phone destination: an auto attendant, a call queue, an individual Teams user or a live contact centre agent. The context is meant to travel with it, so the caller explains themselves once.

The most useful part sits further down Microsoft's own documentation page, under the heading “Support boundaries”. Microsoft supports voice agent solutions only from certified partners. If there are issues, the partner must be contacted first, and Microsoft may reject support cases where a non-certified solution is in use.

That is not a feature note. It is an allocation of responsibility, and it belongs in your contract before the agent is in your call queue. The list of certified providers is short so far, and the programme is still marked “coming soon” in the documentation. That is early enough that the questions below are worth asking yourself.

Six things to settle before you connect it

Check Why it decides something A usable answer
How is the agent connected to the telephony? A certified Teams integration, a SIP trunk to a carrier and a separate number outside Teams give you three different troubleshooting paths “Like this – and here is where what we own ends”
Who owns the ticket when a call drops? Microsoft points to the partner first One name, one channel, one response time
What travels with a handover? The caller should not have to repeat themselves What the human actually sees as the phone rings
Where does the call land when nobody answers? The queue behind the agent is still a queue A defined endpoint, not “they'll probably call back”
Whose name is the number in? A number in Teams and a number with the agent vendor port differently Yours
What happens on termination? The setup has to come apart again Notice period, log export, and who switches off what

Want to talk it through with someone who has done this before?

Fifteen minutes on a call. We will tell you honestly whether a voice agent fits your setup – and what has to be settled before it goes live.

Book Meeting (opens in a new window)+47 24 12 66 30

15 minutes · no obligation · pick your own time

Certification answers an operations question, not a quality one

A certification programme says the solution has been tested against the platform's requirements for data handling, security, latency and accuracy of responses. That is worth something, and it is bounded.

It says nothing about how well the agent understands a caller reading out a company registration number in a broad regional accent, or what it does when someone changes subject mid-sentence. The two questions blur easily because they arrive in the same meeting, but they have different answers and different evidence. The first is read in a contract. The second has to be measured on your own traffic, and no demo has ever failed the test.

The handover is where the setup breaks

Everything in the certification text about routing is about the same moment: the point where the agent gives up.

Teams makes that part easier than it was, because the destination already exists – the queue, the auto attendant, the person. That is also why it is easy to skip. It looks done once the endpoint is picked from a dropdown, but who actually takes the call at half past four on a Friday is not in that dropdown.

The same holds when it is not the agent that gives up but one of the layers underneath it: the fallback path belongs on the phone number itself, not inside the agent.

The platform moves. The question moves with it.

This is the second time in a short stretch that voice AI has turned up as a tick-box inside something the business already pays for. First as a feature in the telephone network, now as a certified add-on in the collaboration platform.

The direction is the same, and it is good for the buyer: the threshold falls, and the generic gets cheap. The consequence is the same too. What still has to be bought separately is what the platform cannot know – who called, what they bought in March, and what needs writing back into the line-of-business system once the call ends. That is also where the price stops being a licence and starts being a unit.

Threll.ai builds voice agents in Norwegian, Swedish and Danish. A voice agent wired correctly to Teams and incorrectly to your business systems has moved the waiting. It has not removed it.

Related Articles

Continue reading more articles

See all articles