What the roadmap says
- Status: Rolling out.
- Preview: October 2026.
- General availability: November 2026.
- Cloud: Worldwide standard multi-tenant.
- Platform: Web.
The roadmap page lists an October 21 announcement of CCI in public preview. Coverage from Alphabold describes CCI as adding conversational self-service, quality assurance, authentication and operational insights to supported contact centers, without necessarily replacing existing infrastructure. Microsoft's description says it took the agentic capabilities built into Dynamics 365 Contact Center and extended them to other contact centers through an open connector.
GA versus preview
The November "What's new" entry and the setup guides don't line up neatly.
- Microsoft Learn's "What's new" page is titled as a preview. It lists Genesys Cloud among the initial integrations in its October 2026 section.
- The captured November 2026 section of that page lists contact center integrations, quality and operational insights, biometric authentication, and Copilot Studio and Azure AI Foundry integration as generally available.
- The voice connector guide is labeled preview. Microsoft says preview features aren't intended for production use.
- The chat connector guide is also labeled preview.
Check the label on the specific connector and channel you plan to use. Don't assume the roadmap's November GA date covers every Genesys capability.
Genesys keeps the call
CCI is an integration layer. It isn't a replacement for Genesys routing. Microsoft's documentation is explicit about who owns what.
- Genesys: It stays in control of the call, and the Audio Connector doesn't transfer call ownership.
- Architect flow: It runs the IVR and routing logic and invokes the Audio Connector.
- Microsoft voice endpoint: It authenticates the WebSocket connection and bridges audio to the bound Copilot Studio voice agent.
- Copilot Studio agent: It handles speech and DTMF input and returns transfer or end signals.
- Transfers: Genesys executes queue routing, representative handling and external transfers.
- CCI: It creates the connection but isn't in the runtime call path.
- Telephony: The integration doesn't add session border controllers, SIP trunks or direct telephony interconnections to Microsoft.
Voice setup, step by step
Prerequisites
- Administrator access to CCI and Genesys Cloud.
- A published Copilot Studio voice agent.
- Permission to install Genesys AppFoundry integrations and edit Architect flows.
- A secure place for the generated application ID and secret.
- The identified Genesys DIDs, routes, queues and flows.
Steps
- In CCI, open Connections and create a Genesys Cloud CX connection. Bind it to the intended voice agent.
- Copy the generated voice endpoint, API key and client secret. The primary key is the secret you enter in Genesys.
- In Genesys Cloud, install the Audio Connector from AppFoundry. On the Configuration tab, enter the generated audio hook URL as the Base Connection URI. Enter the App ID and primary key as credentials. Save, then set the integration to Active.
- Associate the inbound DID with a call route and send it to the intended Architect flow.
- Add the Call Audio Connector action and set Connector ID to
call.conversationId. This keeps the connector session tied to the live call. - Configure the flow to act on the action and target the agent returns. Genesys then performs an ACD queue transfer or an external PSTN transfer.
Multiple agents
Each voice agent that must be available at the same time needs its own CCI connection. Genesys picks the agent per call by setting Flow.ConnectorId before jumping to a reusable task.audioconnector task. You can rebind a single connection to a different agent. That switches the agent for all later calls and doesn't support per-call switching. Microsoft recommends keeping separate route-to-connection-to-agent mappings for development, test and production, and rotating credentials.
Passing context
- Genesys keys must match Copilot Studio global variable names exactly, including case.
- Create an initialization topic and call it from Conversation Start, before any greeting.
- Documented examples include
call.anifor the caller's number,call.calledAddressfor the dialed number, andconversation.idfor correlation. - Return custom values with the case-sensitive
dialogContext.additionalContextItems.<VariableName>format. For a global variable, use only the variable name. - Set returned values before the transfer or escalation step. Genesys exposes them as task variables.
You can run a Genesys-first IVR and invoke the agent only for selected calls. You can also invoke the agent early for conversational triage. In both patterns Genesys keeps control of the call. A Genesys-first design suits regulatory prompts or existing IVR logic.
Bandwidth planning
The voice connector sends raw PCMU audio in binary WebSocket frames. Microsoft's figures:
| Measure | Value |
|---|---|
| Frame | 1,600 bytes every 200 ms |
| Media rate | About 64 Kbps per call, each direction |
| Framing overhead | About 2–10 bytes per frame |
| 1,000 concurrent calls | About 64 Mbps in, 64 Mbps out (about 128 Mbps full duplex) |
Microsoft says the profile needs no extra Azure-side configuration. Customer network capacity has to scale with call volume. Genesys Cloud organizations also have an integration limit. Treat connections as environment-level assets and reuse them where you can.
Chat connector
The chat guide is also preview. Genesys owns the conversation and routing. Its Bot Connector sends each customer message through CCI to the Copilot Studio agent and returns the reply.
- Content: Plain text only. Cards, images and quick replies aren't supported.
- Requirements: A Genesys messaging channel, a published agent, CCI preview enrollment, and at least one supported language on the channel.
- Outcomes: The agent can return
AgentTransferorResolved. Genesys routes to a representative or ends the conversation. - Credentials: The HTTPS chat webhook URL, application ID and secret are case-sensitive. The WebSocket Secure URL is for voice only.
- Timeouts: Session context defaults to a 30-minute idle timeout, with a one-hour maximum. Each message resets the timer.
- Synchronous limit: Replies that arrive after the response window may not be delivered.
- Asynchronous option: A separate Digital Bot Connector handles asynchronous replies. It is in private preview.
The "30 minutes" in the roadmap is easy to confuse with this idle timeout. They are unrelated.
Troubleshooting
- Authentication error: Re-copy the App ID and primary key into Genesys. Save, then reactivate the integration.
- Wrong agent answers: Check
Flow.ConnectorIdand the agent binding on the CCI connection. - Session loses continuity: Set Connector ID to
call.conversationId. - Input variables missing: Check case-sensitive name matches. Make sure the initialization topic runs before any greeting.
- Output variables blank: Use the
dialogContext.additionalContextItems.prefix and set values before the transfer. - Can't create another integration: You may have hit the Genesys integration limit. Reuse or remove one.
Before go-live, test speech, DTMF, queue transfers, external transfers and error paths.
Analysis
Reusing an existing Genesys deployment is the main selling point. Genesys keeps ACD routing, compliance and workforce operations, and Microsoft supplies the AI conversation layer. The catch is that the "30 minutes" figure covers connection mechanics at best. Real projects also involve agent design, Architect flow changes, credential handling, network sizing and testing. The preview labels on the voice and chat guides mean that production readiness should be confirmed first. Other platforms such as Five9, Cisco and Avaya are mentioned in coverage, but the technical guidance covers Genesys Cloud and a universal connector.
References
- Microsoft Contact Center Intelligence: connecting to Genesys. Microsoft 365 Roadmap · 2026-11-17T20:22:25.841076Z
- Configure the Genesys Cloud Voice Connector for Contact Center Intelligence (preview) learn.microsoft.com
- Microsoft Contact Center Intelligence (CCI): Features, Integrations, Benefits & Use Cases alphabold.com