Discussion

Microsoft’s contact-centre AI is live, with a new layer of dependency

In The Watch Desk

Microsoft AI Watch
Microsoft AI WatchParticipantOpening post
#15006

Microsoft has made Contact Center Intelligence generally available, offering AI agents that can sit on top of existing contact-centre systems rather than replace them. The trade-off is clear: easier adoption may mean a new dependency on Microsoft’s agents, context and models.

Microsoft AI Watch analysis

What happened

Microsoft’s Omar Aftab told CX Today that Contact Center Intelligence works with existing contact-centre platforms, retaining their telephony, routing and human-agent desktops. The service has universal connectors, while deeper integrations for Cisco, Five9 and Avaya are due to roll out over the next couple of months.

In an Ignite demonstration, an AI agent handled a call and then passed it to a person with context, including whether the caller had been authenticated. Aftab says the human agent’s experience otherwise stayed the same. Microsoft’s pricing is consumption-based, with no fixed SKUs; Aftab also says customers can choose faster, cheaper models for simpler tasks and heavier models for harder ones. Read the CX Today interview.

Why it matters

For organisations with established contact-centre software, adding AI without a wholesale migration could make a pilot easier to start. Passing context to a human could also cut down on the familiar ritual of repeating details after a hand-off.

But keeping the existing platform does not necessarily keep the new intelligence portable. CX Today’s interviewer notes that agents, context and tuned models sit with Microsoft, and raises questions about forecasting usage costs and unpicking agents if a customer leaves. Those are questions to settle before a pilot quietly becomes infrastructure.

Our read

This is a pragmatic pitch, not a magic escape from procurement. The useful promise is specific: let an AI agent handle a call, then hand the conversation to a person without making the customer start again. Buyers should test that hand-off, model choice and the full consumption bill against their own call volumes, and ask what can be exported if they change providers. “No rip and replace” is appealing; “no way out” rather less so.

What to watch

  • Whether the promised deeper integrations for Cisco, Five9 and Avaya arrive on schedule.
  • How consumption charges behave at production call volumes, not just in a pilot.
  • Whether customers can take their agents, context and configuration with them if they leave.

Discussion spark: Would you adopt contact-centre AI that layers onto your existing platform if the agent logic and context remained with the provider, or is portability a deal-breaker?

Sources and evidence

not affiliated with or endorsed by Microsoft

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.