Microsoft Teams integration

In most organisations the people who can answer the hardest customer questions are not in the contact centre. They are product specialists, underwriters, engineers or account managers, and they collaborate in Microsoft Teams. A Genesys Cloud Microsoft Teams integration gives agents a direct route to them. Instead of putting the customer on hold, emailing a colleague and promising a callback, the agent checks who is available, consults or transfers, and resolves the issue in the same conversation. First-contact resolution improves, customers are spared repeat calls and specialists receive context rather than a cold transfer.

The integration also benefits the wider business. Back-office staff keep working in the Teams environment they know, while the contact centre retains its routing, recording and reporting. Identity can be governed once, through Microsoft Entra ID, rather than maintained manually in two places. QVCCS helps you decide how far to take the integration: some organisations simply want visibility of expert presence, others want full call transfer, and some want selected staff to handle contact centre work from within Teams using the embedded client. We capture that scope in a Business Requirements Document, shaped around your service model and existing Microsoft investment.

The Microsoft Teams integration is installed from AppFoundry, has separate pricing and requires Microsoft Teams licensing. Once Microsoft Entra ID users are provisioned into Genesys Cloud through SCIM, agents see a Teams badge in directory search, and Teams presence updates are pushed to Genesys Cloud, so an expert who is not logged in to Genesys Cloud appears as available on Teams. Agents transfer calls to Teams contacts as blind or consult transfers, and users can create Teams meetings from Genesys Cloud chat. Pushing Genesys Cloud presence back into Teams is not native; Genesys publishes developer blueprints for that pattern.

Each part touches a different team. Telephony requires BYOC and a SIP connection to Microsoft Teams Direct Routing, which Genesys documents with or without a customer-managed session border controller, using the Microsoft Connect integration model and Teams dial plans; Microsoft Calling Plans are not compatible. SCIM provisioning needs Teams-specific attribute mappings for telephone number and object ID, and can be scoped by security group. The Genesys Cloud for Microsoft Teams app embeds the Genesys Cloud client inside Teams for calls, callbacks, outbound dialling, email, messages and ACD voicemail. QVCCS shows how these parts fit together in one High-Level Design.

Presence needs thought. Teams and Genesys Cloud CX use different status models, and Genesys displays the Genesys Cloud presence for users who are logged in to it, and Teams presence for those who are not. We define which users are provisioned and visible, whether any Genesys-to-Teams presence update is worth building from the published blueprints, and how routing should behave as statuses change. Directory search and transfers need similar care, including which Teams users agents may see, how experts are grouped and what context travels with a transfer. Only one PBX phone integration can be enabled per user, so organisations running several UC platforms need a clear model.

The Direct Routing connection deserves the same rigour as any carrier connection. QVCCS designs number plans, Teams dial plans, call routing and codecs, considers media paths for call quality, and defines what happens if either side is unavailable. Session capacity is limited by your SBC licensing where an SBC is used, so we size it with your voice team. For identity, we map Entra ID attributes, including the Teams telephone number and object ID, to Genesys Cloud users, agree how roles, divisions and groups are assigned, and plan prompt deprovisioning of leavers. Every decision goes into the design decision log, so Microsoft, telephony and contact centre teams know where responsibility sits.

A Teams integration fails when telephony, identity and contact centre work are delivered in isolation, so QVCCS musters one team from its own bench across all three and owns the outcome end to end. A Solution Architect writes the High-Level Design and the Interface Control Document between the platforms. An IT Systems, Telecoms & SIP Engineer is the pivotal role here, designing BYOC, Direct Routing and dial plans with your voice team and sizing any SBC. A Senior Developer configures SCIM mappings and any presence blueprint, a Systems Integration Tester proves every call path, and a Project Manager keeps your Microsoft, telephony and identity owners working to one plan and one RAID log.

Testing follows the real paths a customer can take, traced through the Requirements Traceability Matrix to the SIT test pack. We verify presence for provisioned users, blind and consult transfers to individuals, call quality across Direct Routing, and negative paths such as an expert who does not answer, an unprovisioned user or an unavailable SBC. We test provisioning by creating, changing and removing users in Entra ID, and confirm that reporting captures expert involvement. Back-office experts take part in UAT as well as agents, because a transfer that works technically still fails if the specialist does not recognise the call or know what context to expect.

Microsoft Teams and Genesys Cloud CX both release changes frequently, and your organisation will keep adding experts, departments and numbers. QVCCS aligns support and maintenance to your consumption model, as the specialist layer behind your provider's support or with SLA-based cover up to 24x7x365 when contracted directly, and designs monitoring of trunk health and integration status so problems are detected early. Our release readiness reviews assess changes on both platforms, including updates to the Genesys Cloud for Teams app that need new Microsoft Graph permissions, and we keep provisioning scopes and dial plans aligned with organisational change. Over time, that might include bringing more of the business into customer service, guided by the same certified people who designed the foundation.

Measuring the value of expert access helps you decide where to invest next. We use Genesys Cloud CX interaction data, transfer records and wrap-up codes to show how often agents involve Teams experts, which queues depend most on back-office help and how those conversations end. QVCCS helps you build performance views around these questions and review them with operations and departmental leaders. The insight often reveals knowledge gaps that training or knowledge articles could close, or expert groups that deserve their own routing. Our consultants turn those findings into a prioritised backlog, then design, build and test each improvement with the same care as the original integration.