Omnichannel digital messaging, voice, and Copilot with Dynamics 365 and Microsoft as a carrier

This architecture supports the broadest possible contact center scenarios. Using this approach, Microsoft products are used for all omnichannel customer engagements. Microsoft supplies Public Switched Telephone Network (PSTN) connectivity and Microsoft Copilot Studio enables self-service activities. There is a complete end-to-end experience for agents and supervisors in Dynamics 365 Customer Service and the ability to engage other employees using Microsoft Teams. Potential use cases include the following examples:

  • Retailers providing online sales and support

  • Healthcare providers offering support for patient questions

  • Financial Services companies providing help and advice for banking, investments, mortgages, etc.

  • Internally facing help desks for employees

Architecture

The following diagram illustrates the architecture. Choose the magnifier icon for a more detailed view.

Architecture for Dynamics 365 Customer Service and Omnichannel Engagement for digital messaging, voice, Microsoft-supplied PSTN

Dataflow

  1. Customers engage via the channel of their choice, including Microsoft Teams as a channel for internal facing contact centers (such as employee helpdesks).

  2. Azure Communications Services provides PSTN services for both voice and SMS channels.

  3. Microsoft Copilot Studio provides self-service automation in the form of Interactive Voice Response (IVR) and/or messaging chat bots.

  4. Work is routed to agents, who use the Customer Service workspace within Dynamics 365 Customer Service.

  5. Both the agent and supervisor experiences are built upon and integrated with Power Platform. Dataverse stores all core data and events for the customer data platform.

  6. Supervisors interact with the built-in capabilities of Dynamics 365 Customer Service, including insights, forecasting, and scheduling.

  7. Using Context IQ, Teams collaboration is enabled between Dynamics 365 users and Teams users, including the ability to collaborate one-on-one or through swarms. Users can also consult or transfer calls to Teams users.

Components

Assumptions

In all Digital Contact Center Platform architectures, wherever possible, we assume that all or most solution components use the core capabilities of Microsoft Azure, including, but not limited to, compute, storage, identity, security, management, and compliance.