Front pagesponsored · Microsoft
Contact Center23m · 22:49 GMT · 2 min read
Omar Aftab, VP for Conversational AI and Contact Center AI at Microsoft says Contact Center Intelligence is a partner to your CCaaS, not a replacement for it. I grabbed him straight out of his Ignite session to test that promise on the customer, the agent and the exit door.
Press one for billing. Press two for everything else. Now tell us who you are, again.
Omar Aftab, who leads Contact Center Intelligence (CCI) at Microsoft, says that routine “hasn’t changed much in the last 20 years,” and he’s right. I interviewed him at Ignite in San Francisco, straight out of his session and just after CCI went generally available, to ask whether this is a helping hand for CCaaS vendors or a displacement strategy.
“You Don’t Have to Replace Your Entire Contact Center”
Aftab’s pitch is simple. CCI layers on top of whatever you run, so you keep your telephony, your routing and your human agent desktop. Universal connectors work with any contact center, and Cisco, Five9 and Avaya get deeper prebuilt integrations rolling out over the next couple of months. His answer to my land-grab question was direct: “partners to the CCaaS providers, not competitors.”
The Agent Finds Out What the Bot Already Knew
In the Ignite demo, an AI agent handled the call, then passed it to a human. Aftab says the human experience was “entirely unchanged, except that the AI agent passed along the context,” including whether the caller had been authenticated.
That passes my lens test. The customer stops repeating themselves. The agent stops starting from zero. Meanwhile, at the desk, someone finally gets a call that begins at the second sentence.
“Imagine If You Talked to Your Friend That Way”
Aftab’s critique of service today is the best line of the interview. Brands ask who you are, forget your last conversation and ignore your last channel. “Somehow this is what we’ve normalized,” he told me. Hard to argue. We’ve all sat in that queue.
The Brain Is the Part You Can’t Easily Move
Now the operational truth. Telephony and routing stay swappable underneath, which is the selling point. But the intelligence layer, meaning the agents, the context and the tuned models, sits with Microsoft. Pricing is consumption based, with “no SKUs,” so starting is easy. Forecasting the bill at volume, and unpicking the agents if you leave, are questions I’d want answered before the pilot becomes policy. It’s the same lock-in question I put to Deva Rajamohan when Dynamics 365 moved into Copilot.
Publisher’s aside: “no rip and replace” has a way of turning into “no choice” eventually.
Aftab’s Best Case
Fair is fair. Platform refresh cycles run for years, while customer expectations shift monthly. The gap, he argued, keeps getting “larger and larger,” and layering AI closes it without a migration. He also says some preview customers went live on their own, and he pitches model choice: a faster, cheaper model for simple tasks, a heavier one for hard ones. That’s a real case.
Verdict
Layering AI on what you already run is the pragmatic move, and for most buyers probably the right one. Just remember that “don’t replace anything” also means “don’t leave anything,” and the new dependency is the one doing the thinking.
