This is a preview, not a finished product. Microsoft's announcement leaves several practical questions open, and those are what a pilot should test.
What Microsoft announced
Microsoft announced CCI on October 21, 2026. CCI is a set of AI tools built to run on top of contact centre platforms Microsoft doesn't supply. It extends the agentic features of Dynamics 365 Contact Center to other platforms through an open connector. Microsoft's blog names Five9, Cisco Webex Contact Center and Avaya as example vendors. It doesn't publish a full supported-vendor list or the technical requirements for the connector.
The trade press describes the same positioning. CX Today says the idea is to retain the existing telephony, routing, phone numbers, and agent desktop while adding Microsoft's conversational agents, quality tools and biometric authentication.
Availability, per Microsoft:
- Global public preview, except in Austria.
- No general-availability date has been given.
- Organizations can start a 30-day trial environment through the CCI product page, according to CX Today.
The three agents
Microsoft organizes CCI around three agents:
- Customer Assist Agent. It resolves issues on its own or helps human representatives in real time. It covers voice and digital channels. Builders can choose deterministic flows for calls that must follow a fixed path, generative conversations for open-ended questions, or a hybrid. When your organization's criteria call for a person, there's a built-in handoff to a human rep through the contact center or Microsoft Teams. Microsoft doesn't say what those criteria can be.
- Quality Assurance Agent. It scores interactions against quality, compliance and brand standards. You can define custom guardrails for things like greetings, brand compliance and sentiment.
- Service Operations Agent. It's marked "coming soon" for CCI. It's meant to help configure, monitor and optimize the contact center and manage costs.
You build agents in a new customer conversation harness, and you can also begin configuration from Copilot Studio. Agents can be grounded in Microsoft IQ, knowledge sources and more than 1,700 connectors. Microsoft doesn't say which connectors or data sources a given tenant will get.
Quality scoring: what's live and what isn't
This is the easiest place to overread the announcement.
- Available now: evaluation of historical self-service conversations, using built-in and custom metrics.
- Coming soon: real-time evaluation and coaching, plus contact-center agent assist. No dates have been given.
- The 100% claim: Microsoft says you can measure up to 100% of conversations instead of sampling. That is a capability claim, not a promise about accuracy.
- MAS: Microsoft says CCI is held to the same Multimodal Agent Score bar as Dynamics 365 Contact Center. No scores or methodology were published for CCI, so treat this as Microsoft's own assertion.
Voice biometrics
CCI supports voice biometric enrollment and authentication. Customers can opt to use a voiceprint to verify identity during a live call. If the conversation escalates to a human, Microsoft says the authentication carries over.
The announcement doesn't cover consent flows, retention, security controls, regional availability or fallback when a voiceprint fails. Voiceprints are biometric data and are regulated in many jurisdictions, so involve legal and privacy teams before any pilot.
Pricing and governance
Microsoft says CCI's agentic capabilities are usage-based through Copilot Credits. It gives no CCI-specific credit rates. Its footnote says some contact center vendors charge for API access or voice-channel licenses, and CCI doesn't include those costs.
"No rip-and-replace" therefore describes how the integration works, not a promise of zero cost or effort. A pilot budget should include two things:
- Microsoft credit consumption.
- Whatever your current vendor charges for API or voice access.
For context, Microsoft Learn describes usage-based Copilot Credits as measured consumption. CX Today reports that Microsoft says CCI uses consumption-based pricing. Learn says administrators use the Cost management dashboard in the Microsoft 365 admin center for spending policies, limits, alerts and monitoring. The Learn page doesn't list CCI among the services it covers, so don't assume those controls apply to CCI until Microsoft's CCI documentation confirms it.
Microsoft also pitches Agent 365 as the control plane for deploying, monitoring and governing agents across the enterprise, including the contact center. It says Agent 365 had nearly 40 million registered agents across tens of thousands of companies as of July 2026. Agent 365 is available standalone or as part of Microsoft 365 E7. Those figures are Microsoft's own.
Customer evidence
Microsoft cites two customers:
- Thomas Jefferson University says it started previewing agents in its HR Service Desk workflow in September. Six weeks later it was preparing to go live. The agents handle questions on enrollment, eligibility, coverage and billing.
- Siemens Healthineers says it is layering CCI onto its Genesys and ServiceNow platforms. Its goal is faster resolution of routine and complex remote-support issues.
Both are customer statements. Neither includes measured results such as resolution rates, wait times, cost or satisfaction. CX Today calls these early proof points and says a harder test lies ahead.
Strategic read
Constellation Research reads the move as a way to introduce enterprises to Microsoft's AI agent and context layer, connect to systems already in place, and potentially migrate them to Dynamics 365 Contact Center. That is analyst interpretation, not something Microsoft said. It is plausible, though, since CCI reuses Dynamics 365 Contact Center's agents.
Both sides of that are worth weighing:
- For buyers: you can try conversational AI without ripping out telephony, routing or agent desktops, and Microsoft's governance tooling comes with it.
- Against: it is a preview, a lot of the roadmap isn't shipped, connector depth is undocumented, and your total cost depends on third-party fees.
Suggested pilot checklist
Microsoft's own suggested start is to sign in to the CCI portal, connect your existing contact center, and configure one agent for a single high-volume self-service scenario. Based on the gaps above, a sensible pilot would also check:
- Whether your contact center vendor is supported and what it charges for API and voice access.
- How human handoff behaves, including whether context and authentication carry over.
- Which quality metrics you need, remembering that evaluation is historical for now.
- Legal, consent and retention requirements before enabling voice biometrics.
- Credit consumption on a limited call type, before you widen the scope.
- Which agents run in the contact center, and how they'll be governed through Agent 365.
Microsoft will be showing more of this at Ignite in November, according to CX Today, so expect the missing details then.