For years, IVR has mostly meant one thing: menus.
Press 1 for this.
Press 2 for that.
Listen carefully, because the options have changed.
It worked, sort of. But nobody really loved it.
That is why I think Customer Intent Agent for voice is one of the more interesting moves Microsoft has made in Dynamics 365 Contact Center.
The voice capability entered public preview on August and is GA now. Microsoft describes it as using agentic AI to automate customer interactions on the voice channel with more natural conversation, more accurate identification of caller intent, and the ability to escalate to a service representative when needed.
What makes this more interesting is that voice is not happening in isolation.
Microsoft’s broader Customer Intent Agent capability is built around discovering intents from past interactions between representatives and customers, creating an intent library, and then using that to guide both self-service and assisted service scenarios. Microsoft’s overview says it can determine intent, ask follow-up questions, gather missing details, and query the knowledge base for solutions. The voice setup guidance says the same intent model is now being used in voice experiences as well.
That is a very different model from traditional IVR.
Old IVR assumed you had to predefine the path and force the customer into it. This new direction is much closer to listening first, identifying what the customer is actually trying to do, and then guiding the conversation from there.
I think that is the real shift.
Microsoft says Customer Intent Agent for voice can navigate conversations naturally, gather the information needed from the caller, offer suggestions and solutions, and escalate when required. It is also powered by knowledge of the business, customers, and their conversations through Dynamics 365 intent core services.
In plain language, that means Microsoft is trying to turn voice automation from a menu system into a conversation system.
That does not mean every IVR goes away overnight. It also does not mean every organization should hand the front door over to AI without guardrails.
But it does mean the design centre is changing.
The old question used to be:
“How do we build the right menu tree?”
The better question now is probably:
“How do we help the system understand intent quickly and keep the conversation moving naturally?”
That is a much more modern self-service question.
I also think this matters because voice has lagged behind digital channels for a long time when it comes to intelligent automation. Chat and messaging have been easier places to experiment. Voice has usually been harder because the user experience breaks down fast when automation feels rigid or confused.
Microsoft is clearly trying to fix that by building voice on top of the same intent foundation it is using more broadly across Contact Center. The official documentation highlights both self-service and assisted-service value, with ongoing intent detection, follow-up prompts, and tailored solutions in real time.
That is important. Because the real future here is not “AI or human.” It is better handoff between AI and human.
Let the system identify the issue.
Let it collect what it can.
Let it solve simple things when appropriate.
And when it cannot, hand the conversation over with context instead of dumping the customer back at the start.
That is the kind of voice experience people actually want.
My take?
This is not just a new IVR feature. It is Microsoft signaling that voice self-service should start behaving more like an intelligent conversation layer instead of a static routing tree.
And honestly, that feels overdue.
The companies that get the most value from this will probably be the ones that do not treat it as a magic switch. They will start with the right intents, the right knowledge, the right guardrails, and the right escalation model. Microsoft’s own documentation makes clear that the intent library is built from historical support conversations and cases, which means the quality of that underlying service data is going to matter.
But the direction itself is the interesting part.
IVR is no longer just about routing.
It is starting to become about understanding.
And that is a much better place for contact center self-service to go.