Dynamics 365 Customer Service omnichannel, decoded for SMEs

What "omnichannel" actually means in Dynamics 365

Dynamics 365 Customer Service omnichannel means one agent workspace handling conversations across many channels — live chat, voice, SMS, social messaging, and Microsoft Teams — alongside cases, with unified routing, presence, and capacity management deciding who gets what work and when. Microsoft calls this unified agent experience the Copilot Service workspace, the multisession companion to the Customer Service workspace used for case-only work.

The defining trait is that asynchronous channels (SMS, persistent chat, Facebook, LINE, WhatsApp, Teams) land in the same inbox as live conversations and cases. An agent can pick up a chat, reply to an SMS thread, and action a case record without switching apps. That is the practical difference between a true omnichannel platform and a set of disconnected channel tools.

It is important to state what omnichannel is not: it is not a replacement for Customer Service. It is a channel-handling and routing layer that attaches to the case-management core. You license it through the Dynamics 365 Contact Center SKUs, which can sit on top of a Customer Service license, run standalone (without case management), or arrive bundled inside Customer Service Premium.

• →One agent workspace (Copilot Service workspace) across chat, voice, SMS, social, and Teams.
• →Unified routing, presence, capacity profiles, and workstreams decide work distribution across channels.
• →Async channels land in the same inbox as live conversations and cases — no app-switching.
• →Omnichannel is a channel layer, not a case-management replacement; it is licensed via the Contact Center SKUs.

Live Chat: the real-time embeddable widget

Live Chat is the real-time engagement channel in Dynamics 365 Customer Service omnichannel — an embeddable chat widget placed on a website that connects customers to agents in real time. It is the channel most SMEs start with because it is visible, low-friction, and does not require telephony licensing or PSTN setup.

Pre-conversation surveys, operating-hours rules, queue position feedback, file attachment, co-browse, and agent-to-agent consult and transfer are all built in. Chat conversations can be auto-converted to cases for after-hours follow-up, which closes the loop between the conversation and the case-management core.

For an SME, live chat is typically the fastest path to a measurable omnichannel win: deflection from phone, faster first response, and a clean handoff into a tracked case when the chat cannot resolve the issue in session.

• →Embeddable real-time chat widget for a website, connecting customers to agents live.
• →Includes pre-chat surveys, operating hours, queue position, attachments, co-browse, consult and transfer.
• →Chats can be auto-converted to cases for follow-up after the session ends.
• →Typically the highest-ROI first channel for SMEs — no telephony or PSTN required.

Voice: native PSTN calling with AI assistance

The voice channel delivers native PSTN calling inside Dynamics 365, carried on Azure Communication Services, with real-time AI-powered live call transcription, sentiment analysis, and AI-based suggestions surfaced to the agent during the call. Inbound, outbound, call transfers, queues, music on hold, and recording are native. Voice capabilities are powered by Azure Communication Services and priced separately from the Contact Center seat.

Voice is licensed through the Dynamics 365 Contact Center Voice SKU ($95 per user/month), which adds voice on top of the digital messaging SKU. Operationally it is the heaviest channel to stand up because it touches telephony: number provisioning, carrier setup, compliance recording, and emergency-calling requirements.

Most SME service teams should defer voice until they have a clear case volume that justifies a contact-center tier. Starting with chat and SMS, then layering voice as the team matures, is the standard Flectic recommendation — voice is the last channel to switch on, not the first.

• →Native PSTN calling inside Dynamics 365, carried on Azure Communication Services.
• →Real-time AI transcription, sentiment analysis, and suggestions during the live call.
• →Licensed via the Dynamics 365 Contact Center Voice SKU ($95/user/month) on top of the digital SKU.
• →Operationally heavy: number provisioning, compliance, emergency calling — defer until volume justifies it.

SMS: asynchronous messaging via Azure Communication Services or Twilio

SMS is an asynchronous channel in Dynamics 365 Customer Service omnichannel — customers text in, agents reply when capacity allows, and the conversation persists. The supported providers are Azure Communication Services and Twilio, both of which require their own provider subscription and phone-number provisioning separate from the Dynamics 365 license.

Because SMS is async, it suits use cases where immediate real-time presence is not required: appointment reminders, status updates, follow-up on a resolved case, or out-of-hours triage. It also tends to see higher open and response rates than email for short, time-sensitive messages, which makes it a strong complement to live chat rather than a competitor to it.

Cost note: SMS usage is billed per message through the provider (Azure Communication Services or Twilio), not through Microsoft. The channel itself is part of the Contact Center Digital messaging entitlement, so budget for both the seat license and the provider usage.

• →Asynchronous SMS channel; conversations persist and agents reply when capacity allows.
• →Supported providers: Azure Communication Services and Twilio (separate subscription required).
• →Strong for reminders, status updates, and out-of-hours triage; complements live chat rather than competing with it.
• →Per-message usage flows through ACS or Twilio; the channel seat is part of Contact Center Digital.

Social and messaging channels: Apple, Facebook, WhatsApp, LINE

Dynamics 365 Customer Service omnichannel supports a set of social and messaging channels that let customers reach the team on the platforms they already use. Supported channels include Apple Messages for Business, Facebook Messenger, WhatsApp, and LINE. A custom messaging channel extension supports additional platforms such as Telegram for teams with bespoke requirements.

Each social channel has its own provider account requirements and approval process (Apple Messages for Business in particular has a formal registration). WhatsApp can now be configured through Azure Communication Services as a Microsoft first-party provider, so a separate Twilio account is no longer required for WhatsApp — though Twilio remains a supported alternative for SMS and messaging. The digital messaging channels are covered by the Dynamics 365 Contact Center Digital SKU ($95 per user/month).

For most SMEs, social channels are a phase-two addition — useful once a support team has live chat working and wants to meet customers on consumer messaging apps, but rarely the right first integration for a small support desk.

• →Supported: Apple Messages for Business, Facebook Messenger, WhatsApp, and LINE.
• →Custom messaging channel extension supports additional platforms such as Telegram.
• →Apple Messages for Business requires formal registration; WhatsApp can use Azure Communication Services as a first-party provider (Twilio optional).
• →Covered by the Contact Center Digital SKU ($95/user/month) — typically a phase-two addition for SMEs.

What the digital messaging add-on covers (and what it does not)

"Digital messaging" is the licensing term Microsoft uses for every non-voice channel in the Contact Center family. The Dynamics 365 Contact Center Digital SKU ($95 per user/month) is the entitlement that unlocks live chat, SMS, the social and messaging apps, and Microsoft Teams as a customer-facing channel — everything except native PSTN calling. If a team wants chat and async messaging but has no need for in-app telephony, this single SKU is the entire channel layer.

Microsoft offers a 30-day Digital Messaging trial with 25 user licenses, which lets an SME stand up live chat and one or two messaging channels on real traffic before committing to paid seats. After the trial, paid Digital Messaging licenses must be assigned for agents to keep receiving conversations.

What the digital messaging add-on does NOT include is the voice layer. Native inbound and outbound PSTN calling, call queues, IVR, and live call transcription sit in the Contact Center Voice SKU ($95), which layers on top of Digital to form the combined Contact Center product ($110). Usage charges are separate from both per-seat SKUs: SMS is billed per message and voice per minute through the provider (Azure Communication Services or Twilio), not through Microsoft's seat pricing.

• →Digital Messaging ($95) unlocks every non-voice channel: live chat, SMS, social apps, and Teams.
• →A 30-day trial with 25 licenses lets you pilot channels on real traffic before paying.
• →Voice is a separate add-on ($95) that combines with Digital to form Contact Center ($110).
• →SMS and voice usage are billed per message or per minute through Azure Communication Services or Twilio, not per seat.

Dynamics 365 Customer Service omnichannel licensing and pricing

As of August 1, 2025, the legacy "Omnichannel for Customer Service" SKUs were removed from sale; the equivalent capability is now purchased through the Dynamics 365 Contact Center family. The full licensing picture spans both the Customer Service core (which holds cases) and the Contact Center channel layer (which holds conversations). The table below maps every SKU an SME is likely to encounter, its price, and what it actually includes.

There are three ways an SME buys the channel layer. First, standalone: Contact Center Digital ($95) or the combined Contact Center ($110) can be purchased without a Customer Service license — but then you get routing and channels without case management, which suits call-center teams using a third-party CRM. Second, as an attach to Customer Service Enterprise ($105), where the Contact Center add-on is discounted to roughly $90 per user/month. Third, bundled: Dynamics 365 Customer Service Premium ($195 per user/month) includes both Customer Service Enterprise and the full Contact Center capability in one SKU.

Note that Customer Service Professional ($50) does not support the Contact Center channel add-on at all — channels require moving up to Enterprise first. For teams already on Business Central, Customer Service Enterprise can be attached for about $20 per user/month, the lightest entry into Microsoft case management before any channel layer is added. A promotional discount that ran on these SKUs through June 30, 2026 has now concluded, so standard per-seat pricing applies.

The practical SME takeaway: if you already pay for Customer Service Enterprise and want to add channels, the Premium SKU ($195) is usually the cleanest path because it removes the attach math. If you only need digital channels (chat plus SMS plus social) and already handle cases elsewhere, Contact Center Digital standalone ($95) is the lightest entry. Flectic models both paths against your actual seat count before you commit.

• →Legacy "Omnichannel for Customer Service" SKUs were removed from sale August 1, 2025; buy the equivalent via Contact Center SKUs.
• →Customer Service tiers: Professional $50, Enterprise $105, Premium $195 (Enterprise plus Contact Center bundled).
• →Channel layer: Contact Center Digital $95, Voice $95, combined Contact Center $110, or ~$90 attached to Enterprise.
• →Customer Service Professional ($50) does not support the channel add-on — channels require Enterprise first.
• →A promo that ran through June 30, 2026 has concluded; standard per-seat pricing now applies.

When is the omnichannel add-on worth the cost for an SME?

The honest SME question is not "is omnichannel good?" but "does the added seat cost pay back?" The licensing math is straightforward: a team on Customer Service Enterprise ($105 per user/month) that adds the full channel layer pays roughly $200 per user/month (Enterprise plus Contact Center Digital), or $195 for the same combination bundled as Customer Service Premium. A team on Customer Service Professional ($50) has no omnichannel path at all, because Professional does not support the Contact Center add-on, so channels require moving up to Enterprise first.

The add-on earns its cost when at least one of these is true: customers already contact you across more than one channel (phone plus chat plus messaging apps), your phone volume is high enough that deflection to chat or async messaging would cut handle time, or you need unified routing so the same agent pool handles cases and conversations without a separate helpdesk tool. In those cases the per-seat premium is quickly offset by fewer missed messages, lower average handle time, and consolidated tooling.

It is usually the wrong time to buy the add-on when your support volume runs through a single channel (email or cases only), your team is too small to benefit from routing rules and capacity profiles, or you have not yet built the case-management discipline the channel layer depends on. In that scenario, Customer Service Enterprise alone, or even Business Central with the $20-per-user Enterprise attach, delivers more value than channels no one is staffed to answer. Flectic models both paths against your actual seat count and channel volume before you commit.

• →Adding channels to CS Enterprise costs roughly $200/user/month, or $195 bundled as Customer Service Premium.
• →Customer Service Professional ($50) does not support the Contact Center add-on — channels require Enterprise first.
• →Worth it when you have multi-channel volume, phone-deflection upside, or need unified routing across cases and conversations.
• →Not worth it for single-channel, low-volume teams who lack the case-management discipline channels depend on.

How to provision and set up omnichannel for Customer Service

Provisioning omnichannel for Customer Service happens in the Power Platform admin center and the Contact Center admin app, not inside the Customer Service workspace itself. The high-level sequence is the same whether you are turning on a single live-chat widget or a full multi-channel contact center: enable the app, build the workstreams that define how conversations flow, configure the channels, set up queues, and write the routing rules that decide which queue receives which conversation.

Step 1 — Enable the app. In the Power Platform admin center, open your environment, go to Resources > Dynamics 365 apps, find Omnichannel for Customer Service or Dynamics 365 Contact Center, and install or enable it. Then assign the matching Contact Center Digital, Voice, or combined licenses to the agents who will handle conversations.

Step 2 — Create workstreams. A workstream is the container that defines a channel type (Messaging, Voice, or a Record such as cases), the work distribution mode (Push auto-assigns to available agents; Pick lets agents claim from a queue), and the operating hours. You typically create one workstream per channel or channel group — for example a persistent-chat workstream and an SMS workstream.

Step 3 — Configure channels. Inside each workstream, add the channel instances: a live-chat widget with pre-conversation survey, position-in-queue, and operating-hours rules; a provisioned SMS number; or a WhatsApp, Apple, or Facebook account. For SMS and voice you provision phone numbers through Azure Communication Services or Twilio; for WhatsApp you can use Azure Communication Services as a first-party provider without a separate Twilio account.

Step 4 — Set up queues and capacity. Create queues, assign agents, and set each agent's capacity profile, which caps how many concurrent conversations of each type they can hold. Capacity profiles are what let a single agent juggle several async chats while holding only one live voice call.

Step 5 — Write routing rules. Classification and route-to-queue rules inspect each incoming conversation (channel, language, skills, customer status) and send it to the right queue. Unified routing is the engine behind this — one rule framework spanning channels, cases, and records.

Step 6 — Configure presence and test. Define presence states (Available, Busy, Do not disturb) tied to capacity, then run test conversations through each channel to confirm routing, presence, and the Copilot Service workspace before going live.

• →Enable the app in Power Platform admin center > Resources > Dynamics 365 apps, then assign Contact Center licenses.
• →Build workstreams: one per channel, each setting channel type, work distribution (Push or Pick), and operating hours.
• →Add channel instances — chat widget, SMS number, WhatsApp via Azure Communication Services, or social accounts.
• →Create queues, assign agents, and set capacity profiles that cap concurrent conversations per agent.
• →Write route-to-queue and classification rules with unified routing; configure presence; test before go-live.

Where SMEs should start with omnichannel

The most common SME mistake is treating omnichannel as an all-or-nothing switch-on. It is not. The channels that deliver the fastest payback — live chat and SMS — are also the cheapest to stand up and the lightest to license. Voice, social, and Teams collaboration layer in later, after the team has routing discipline and case-handling habits in place.

Flectic's recommended sequencing for a Dynamics 365 SME is: (1) start with Live Chat on the highest-traffic support page, (2) add SMS for async follow-up and out-of-hours triage, (3) bring in the digital messaging channels (Apple, Facebook, WhatsApp) once chat volume justifies a second channel, and (4) layer Voice last, when inbound call volume clearly warrants a contact-center tier. This sequencing keeps licensing lean and avoids paying for voice seats before the team is ready to use them.

Designed to deliver up to 3x faster than a typical gold-plated contact-center rollout, this phased approach also keeps the platform-neutral option open: if a channel turns out to fit Odoo better than Dynamics 365 for a specific workflow, Flectic can implement it on either side without re-platforming the whole service desk.

• →Start with Live Chat on the highest-traffic support page — lowest licensing cost, fastest payback.
• →Add SMS for async follow-up and out-of-hours triage as the second channel.
• →Layer social messaging (Apple, Facebook, WhatsApp) once chat volume justifies a second channel.
• →Switch on Voice last, only when inbound call volume clearly warrants a contact-center tier.

Frequently asked questions