A virtual customer service agent routes a caller to human support representatives through a secure cloud system.
Heedify's AI Receptionist is now on Microsoft's certified list of third-party voice agents for Teams. Telecom Reseller reported the news on November 18. The practical questions for Teams admins are what the certification means, what it doesn't, and what still needs configuring.

A virtual customer service agent routes a caller to human support representatives through a secure cloud system. What was announced​

Telecom Reseller reports that Heedify, a France-based provider, has Microsoft's approval for its AI Receptionist under the Teams Unify Integration Model (UIM). Microsoft's Learn documentation backs this up. It lists the providers whose voice agents are integrated into Teams through the Unify model: Audiocodes, CentrePal, Heedify and NiCE/Cognigy. The Microsoft page shows a last-updated date of November 4, 2026, so the listing predates the trade-press coverage.

This is an addition to a certified-partner list. It is not a new Teams platform feature. Heedify was already known in the Teams ecosystem. Microsoft's Teams Phone extensibility blog named Heedify among the contact center ISVs that had completed certification for Teams Phone extensibility. The new element is the voice-agent program.

What the certification covers​

Microsoft says the certification program verifies that each participating provider's solution offers the quality, compatibility and reliability it expects from Microsoft solutions. That is a statement of program intent. No test results, service-level figures or independent performance data have been published.

Microsoft describes the Unify voice-agent pattern as follows: a bot answers calls, provides information, authenticates callers and captures intent. It then routes the call to a Teams Phone destination, such as an Auto Attendant, Call Queue, individual Teams user or Contact Center live agent. The full caller context goes with the call.

The certified product is a third-party service. Microsoft does not build or own Heedify AIR. Heedify's documentation says it runs on Teams Phone Extensibility and Azure Communication Services.

How Heedify AIR handles a call​

Heedify's documentation describes the following sequence:

  1. The caller dials the number assigned to the agent's Teams resource account.
  2. The agent speaks its configured greeting and detects the caller's language.
  3. It works out intent from the conversation, from keywords defined on routes, or from both. It can ask a clarifying question.
  4. It can answer from a knowledge base, look up a colleague in the Teams directory, check presence or take a message.
  5. It transfers the call to the matching route after a configured announcement. If intent stays unclear, it uses a fallback destination.

Documented transfer targets are a Heedify queue, a Teams user, a Teams call queue or an external phone number. The documented settings also include:

  • Routing strategy: conversational (the default), keyword-only or hybrid.
  • Clarifying questions: one by default.
  • Fallback to human: on by default if an error occurs.
  • Custom CRM or API connectors: these can read data when a call starts or send an update during or after a call. They require an HTTPS endpoint, and plain HTTP is refused. The default timeout is 10 seconds. If the CRM doesn't answer in time, the agent carries on without that context.
  • Knowledge base: off by default. Inline text is limited to about 8,000 characters, and longer text is truncated.
  • Region: the data region defaults to Europe, with US and Asia-Pacific options.

Administrator checklist​

Certification does not remove the setup work. Based on Heedify's AIR documentation:

  • A Microsoft 365 administrator grants consent to the Heedify AI Voice Agent application once per tenant, from Global Settings in the Heedify admin portal, before the first agent is created.
  • The AI Agent module is enabled per tenant by Heedify. If it doesn't appear in the sidebar, you need to contact Heedify.
  • You create a Teams resource account linked to Heedify Unify and assign it a phone number. Heedify says the PowerShell steps match those for a Unify call flow.
  • In the Heedify portal, you then create the agent. You choose the Entity and Agent Name, then configure voice, greeting and routes, and optionally the knowledge base and skills. Save it and call the number to test.
  • The resource account and the Entity cannot be changed after creation. Deleting an agent removes it from Heedify, but the Teams resource account and its number stay in Teams.

Heedify's general Unify requirements page lists Microsoft Graph and Azure Communication Services delegated permissions for Heedify Cloud CX, including presence and directory reads. Some of them need admin consent. Heedify also asks that proxies allow outbound connections to its cloud domain and to Microsoft SignalR WebSocket endpoints. That page covers Heedify's contact center product in general, so don't assume every listed permission applies to AIR. Review the consent screen your tenant actually shows.

On languages, Heedify says the agent detects the caller's language and replies in it, with no language list to configure. The knowledge base's primary language is English or French. Treat broader multilingual marketing claims with caution until you've tested your own languages.

The support boundary​

This is the clearest practical benefit of certification. Microsoft supports voice agent solutions only from certified partners. If there's a problem, you contact the voice agent partner first, and the partner can bring the issue to Microsoft through internal channels. Microsoft may reject cases involving a noncertified solution, or cases where the partner can address the issue.

In practice, Heedify is your first line of support, not Microsoft. Certification gives you a defined escalation path. It is not a warranty. Another WindowsForum report on the NiCE/Cognigy listing also noted that third-party voice-agent partners have their own licensing requirements. Budget for the partner's licensing alongside your Teams Phone setup. No pricing or general-availability date for AIR turned up in the sources.

Heedify versus Microsoft's own Teams Phone Agent​

Telecom Reseller frames this against Microsoft's own AI calling, saying specialists will need to prove their value in CRM integration, routing, reporting and complex service workflows. That is reasonable market commentary, but the evidence doesn't support a feature-by-feature comparison. No pricing, benchmarks, market share or customer case studies are available. The report's claims about named Salesforce, HubSpot and ServiceNow integrations come from Heedify and the trade report. Only the generic CRM and API connector capability is documented in the technical material reviewed here.

CX Today's coverage quotes a Heedify executive on the value of connecting voice AI to CRM data. That is a vendor view, not independent validation. The reduced-repetition benefit of context-preserving handoffs is a plausible mechanism, but no measured results exist.

What to do next​

If you run Teams Phone and are evaluating AI call answering:

  • Check Microsoft's certified list, because support eligibility depends on it.
  • Pilot on a single resource account and number before any wider rollout.
  • Test the fallback path, including a transfer failure and a CRM timeout.
  • Review the consent permissions with your security team.
  • Test your own languages and accents, not just the demo.
  • Confirm licensing and data-region choices with the vendor in writing.

In short, Heedify AIR's certification is verified by Microsoft's listing and gives you a clear support route. Whether it beats a native option or a rival such as Cognigy or AudioCodes in your environment is something only a pilot can show.

 

References

  1. Microsoft Certifies Heedify AI Voice Agent for Teams - Telecom Reseller / Technology Reseller News Telecom Reseller / Technology Reseller News 2026-11-18T17:03:41+00:00
  2. Heedify AI Receptionist (AIR): AI Voice Agent | Heedify Doc Portal docs.heedify.io
  3. Teams Unify Integration Model for Voice Agent learn.microsoft.com