Dynamics 365 omnichannel licensing, untangled

The Pricing Page Names the SKUs - It Does Not Show the Stack

Search 'dynamics 365 omnichannel pricing' and almost every result quotes the three Contact Center SKUs - $110, $95, and $95 per user/month - and stops. Those numbers are real, but they answer the wrong question. The question buyers actually face is not 'what does a Contact Center seat cost?' It is 'how do those seats combine with my Customer Service base, and which combination is cheapest for my team?' That composition question is the one Microsoft's pricing page does not draw for you, and it is where the real money is decided.

The deeper confusion is naming. Microsoft's own product is now called Dynamics 365 Contact Center, but most documentation, URLs, and older contracts still say 'Omnichannel for Customer Service.' They are the same capability under two names, and the add-on packaging changed when the name did - which is why a quote for a 'Digital Messaging add-on' and a quote for 'Contact Center Digital' describe the same entitlement under different-era naming. Most pricing pages never resolve this, so buyers compare old quotes to new SKUs and reach wrong conclusions.

This page is the licensing deep-dive that sits underneath our broader Dynamics 365 Customer Service omnichannel product guide and our Customer Service pricing overview. Those pages cover channel design and case-tier math; this one covers how to license the channel layer—Contact Center seats, Copilot Studio capacity, and Azure telephony—without overpaying. Flectic is platform-neutral: we ship Dynamics 365 and Odoo for SMEs across Canada, the UK, and the US, so the honest answer is sometimes a Dynamics 365 Premium bundle and sometimes Odoo at a fraction of the per-seat cost.

"Omnichannel for Customer Service" and "Contact Center" Are the Same Thing

The single biggest source of confusion in this SERP is that the product has two names. 'Omnichannel for Customer Service' is the legacy capability name - the unified routing, presence, multisession Copilot Service workspace, and channel handling that sits on top of Customer Service. 'Dynamics 365 Contact Center' is the current product that ships the exact same feature set. Microsoft rebranded the offering, but the documentation footprint was not rewritten, so Microsoft Learn URLs, partner blogs, and older contracts still lead with 'omnichannel.' When you see both terms in search results, you are looking at one product, not two.

The packaging changed alongside the name, and that is the second layer of confusion. Under the older model, omnichannel was a set of add-on SKUs that attached to Customer Service Enterprise - colloquially the Chat add-on, the Digital Messaging add-on, and the Voice Channel add-on, each carrying its own capacity. Under the current model those add-ons were consolidated into three Dynamics 365 Contact Center SKUs: a combined product and separate Digital and Voice products. The capability is continuous; the SKU you buy and the name on the invoice are what shifted.

The practical takeaway for a buyer holding a two-year-old quote: a line item reading 'Digital Messaging add-on' and a line item reading 'Dynamics 365 Contact Center Digital' describe the same entitlement. Do not assume the new quote is more expensive just because the SKU name changed - compare the per-seat price and the included capacity, not the label.

Named User, Not Concurrent: Every Conversing Agent Needs a Seat

Before any SKU math, get the licensing model right: Dynamics 365 Contact Center is a per-user, named-user license. Every named agent who picks up a live chat, voice call, SMS thread, or social message needs a Contact Center seat, in addition to (or instead of) a Customer Service seat. Licenses cannot be shared across people for concurrent peak-hour coverage—if two agents work alternating shifts on the same physical desk, each still needs their own named seat. Partner licensing guides state this explicitly: each license is assigned to a named user and concurrent use is not permitted; when someone leaves, you reassign the seat, you do not float it across simultaneous logins.

This is the opposite of how some adjacent Microsoft products price—Dynamics 365 Customer Insights, for example, is tenant-level with unlimited users—so buyers who generalize from a tenant-level or concurrent CCaaS model reach a wildly wrong seat count. Older Omnichannel for Customer Service conversations sometimes blurred capacity add-ons (sessions, concurrent conversations) with user seats; under Contact Center the user seat is still named, while conversation and bot volume meter separately through Copilot Studio capacity and Copilot Credits.

Two cost consequences follow. First, seat count is the primary cost lever, so over-seating is the primary waste. Supervisors who only monitor queues, quality analysts who only review recordings, and back-office case workers who never touch a live channel do not need a Contact Center seat—they need Customer Service (or less). Licensing 'just in case' users on the channel SKU is the most common way SMEs inflate this bill. Second, the Contact Center seat is additive to the case-management seat unless you buy a bundle, which is exactly why the Premium stack math matters so much. The rule of thumb Flectic applies when scoping: count only the agents who actively converse across a channel in a normal shift. Everyone else stays on a Customer Service seat alone. That single discipline typically trims 15–30% off the Contact Center line before any SKU optimization.

The Three Contact Center SKUs: $110, $95, $95

Microsoft sells the omnichannel capability through three Dynamics 365 Contact Center SKUs, all billed per user per month, paid yearly. List prices, re-verified August 2026 against Microsoft's Contact Center pricing page: Dynamics 365 Contact Center is $110/user/month - the combined all-in-one product that spans digital and voice channels. Dynamics 365 Contact Center Digital is $95/user/month and adds digital messaging and chat channels. Dynamics 365 Contact Center Voice is $95/user/month and adds native voice capabilities. These are the per-user license lines before any attach discount, consumption charge, or capacity add-on.

The features track the split. The Digital SKU covers self-service chatbots, live and persistent chat across messaging and social channels, real-time translation, and conversation summarization. The Voice SKU covers inbound voice routing, voicemail, recording and transcription, conversation summarization, and outbound dialing and calling. The combined Contact Center SKU delivers both plus self-service IVR - it is the only SKU that includes interactive voice response, which matters if your self-service menu is telephony-based rather than chat-based.

The critical arithmetic most pricing pages omit: buying Digital ($95) and Voice ($95) as two separate add-ons costs $190/user/month, while the combined Contact Center SKU costs $110/user/month. If your team needs both digital and voice - the definition of true omnichannel - the combined SKU is roughly $80/user/month cheaper than stacking the two. Never buy the two add-ons side by side when you need both; the combined product exists precisely to prevent that.

Channels in the Seat vs Capacity You Buy Separately

A Contact Center seat is an entitlement for a named agent to work channels—not an all-you-can-consume conversation plan. The three SKUs define which channel families the agent may handle; digital messaging volume, chatbot sessions, AI agents, and PSTN carriage meter on different bills. Competitors that only reprint the $110 / $95 / $95 list prices leave buyers blind to this second and third layer.

Use the matrix below as a budgeting checklist. Self-service chatbots and digital messaging volume are licensed through Microsoft Copilot Studio capacity (Microsoft footnotes 2 and 7). Voice software sits in the Voice or combined SKU, but PSTN minutes and numbers sit on Azure Communication Services (footnotes 3 and 8). The four Dynamics customer-service AI agents require Copilot Credits on a la carte Contact Center SKUs; Customer Service Premium includes base Copilot Credit capacity for those agents instead.

When you read 'chat included' on a partner quote, force the clarification: included as an agent entitlement, or included as metered conversation capacity? Those are different cost lines. The same split applies to IVR: interactive voice response is a combined-SKU software feature, while voice-bot minutes and call-intelligence minutes are capacity entitlements described in the Dynamics 365 Licensing Guide and can still generate overage once volume exceeds the per-user pool.

Three Ways to Acquire the Same Channel Capability

The same Contact Center capability can be purchased three different ways, and the path you choose changes both the per-seat price and whether case management is included. Understanding the three paths is the difference between a clean license stack and an overbuilt one. The choice is driven by where your cases live and what you already license, not by feature differences - the channel features are identical across the paths.

First, standalone. Dynamics 365 Contact Center SKUs can run on their own without a Customer Service license. Microsoft ships prebuilt integrations with Salesforce, Dynamics 365, and other CRMs, so a contact-center team whose cases live in a non-Microsoft CRM can license the channel layer alone and embed it. You get routing, channels, and the Copilot Service workspace, but no Dynamics 365 case management - your cases stay in the host CRM. This path suits pure call-center teams that already standardized elsewhere.

Second, attach. When the Contact Center SKU is purchased together with Dynamics 365 Customer Service Enterprise, Microsoft applies a discount—stated directly in footnote 1 on the pricing page: 'Discount pricing available when purchased with Dynamics 365 Customer Service Enterprise licenses.' The Customer Service pricing page adds that attach discount pricing is also available when purchased with Microsoft Copilot for Service licenses. The channel layer then sits on the Customer Service case core, giving one agent both case management and channels. A second attach pattern matters for multi-product users: Customer Service Enterprise itself can attach at a reduced rate when a user already holds a qualifying Dynamics 365 base such as Sales Enterprise, Finance, Field Service, or Commerce—so a field technician who also takes inbound Contact Center calls may stack base Field Service + Customer Service attach + Contact Center rather than paying full list for every line. Third, bundled. Dynamics 365 Customer Service Premium ($195/user/month) ships Customer Service Enterprise and the full Contact Center capability in a single SKU, with base Copilot Credit capacity included. The detailed attach mechanic across the wider suite is covered in our Dynamics 365 attach licensing guide; for omnichannel specifically, the question is which of these three paths matches your estate.

Premium Is Usually Cheaper Than Enterprise Plus Contact Center a la Carte

The composition arithmetic is the single most overlooked lever in Dynamics 365 omnichannel licensing, and it resolves to a surprisingly clean rule. Build the stack at list price: Customer Service Enterprise ($105/user/month) plus Contact Center ($110/user/month) purchased separately equals $215/user/month. Customer Service Premium ($195/user/month) bundles Customer Service Enterprise and the full Contact Center capability in one SKU. Premium is therefore roughly $20/user/month cheaper than the a la carte stack - before counting the Copilot Credit capacity Premium includes and the a la carte stack does not.

Stack that against a real team. A 25-seat omnichannel team on the a la carte Enterprise-plus-Contact-Center stack pays (105 + 110) x 25 x 12 = $64,500 per year. The same team on Premium pays 195 x 25 x 12 = $58,500 per year - a $6,000 annual saving on license alone, plus included Copilot Credit capacity that the a la carte stack would bill separately. For any organization that needs both case management and any channel, Premium is almost always the cheaper and simpler choice, and the gap widens once you account for credits.

The crossover works the other way in two scenarios. The a la carte Contact Center SKU makes sense when your cases live in a non-Microsoft CRM and you only need the channel layer (the standalone path above), or when you already hold Customer Service Enterprise under an attach-eligible arrangement and the attach discount brings the channel layer below the Premium premium. In every other case, default to Premium for a cases-plus-channels team - it exists to collapse this exact stack.

One more attach nuance: if agents already carry Sales Enterprise or Field Service as their base Dynamics 365 license, model Customer Service as an attach before you compare Premium. Attach can pull the cases-plus-channels stack below the Premium line for dual-role teams even when pure list math favors Premium. Pure contact-center agents without another Dynamics base still default to Premium when they need both cases and channels.

Digital Messaging Capacity Now Lives in Microsoft Copilot Studio

A significant licensing change arrived in the 2025-2026 wave and is easy to miss because it hides in a footnote. Microsoft's pricing pages state it plainly in footnotes 2 and 7: 'Purchase capacity for digital messaging with Microsoft Copilot Studio.' Under the older add-on model, digital messaging carried its own per-session capacity entitlement tied to the Digital Messaging add-on. Under the current model, that capacity has migrated into the Copilot Studio metering framework - the same framework that meters Copilot agents and bot sessions across the Power Platform.

What this means in practice: the $95/user Contact Center Digital seat is the entitlement to use the channels (the right for an agent to handle a chat or social conversation). The actual digital messaging and chatbot session volume meters through Microsoft Copilot Studio, which itself runs on Copilot Credits backed by a linked Azure subscription. So a digital-heavy deployment now carries three cost layers rather than two: the per-user seat, the Copilot Studio capacity for messaging and bots, and the underlying Copilot Credit consumption that powers it. A team that leans heavily on self-service chatbots will feel this migration most acutely.

The budgeting implication is concrete. Model your monthly conversation and bot-session volume, not just your agent count, before committing to a digital-only stack. An organization that buys the Digital SKU thinking chat is 'included' can be surprised by a Copilot Studio capacity bill driven by bot deflection volume - the very volume that makes chat attractive in the first place. Forecast the messaging workload as a first-class line item.

Cross-check chatbot design against Copilot Studio message blocks early. Partner worked examples show that a bot 'message' is any bot action—welcome, automation step, or response—so a chatty multi-turn deflection path multiplies billable messages far beyond the raw customer conversation count. That is why usage-based agent and bot metering is the 2025–2026 contact-center story practitioners keep repeating: autonomous deflection that looks free in the seat quote shows up as Copilot Studio and Copilot Credit consumption on the Azure-linked bill.

Default Capacity Pools: Routing, IVR, Call Intelligence, Credits

Microsoft does not put every entitlement number on the marketing pricing page. The Dynamics 365 Licensing Guide (March 2026 edition and later updates) is where default capacity pools live—unified routing record routes, Copilot Studio IVR minutes, Call Intelligence minutes, Dataverse storage accruals, and the base Copilot Credit envelope on Premium. Partner explainers that walk those guide numbers show a consistent pattern: Contact Center Voice-class seats carry large monthly pools of Call Intelligence and voice-bot minutes per user, Digital seats contribute unified routing record routes, and Customer Service Premium adds a per-user base Copilot Credit pool (commonly summarized as 1,000 credits per user per month in March 2026 guide summaries) so AI agents do not start from zero on day one.

Treat those pools as planning inputs, not free infinite capacity. A high-deflection IVR that keeps callers in automation for five minutes still burns voice-bot minutes. Call recording and transcription drive Dataverse file storage as well as ACS recording charges. Unified routing overages matter when you route email and cases through the same engine as chats. Model monthly conversation volume against the pooled entitlement before you celebrate a 'cheap' Premium seat.

Legacy Omnichannel for Customer Service add-on contracts still appear in renewals. Microsoft’s Contact Center licensing guidance has been clear that customers on older Omnichannel add-ons can remain through the current enrollment and may renew for one additional term in some transition language, but at the next renewal they move to Contact Center add-ons or Customer Service Premium. Do not price a five-year TCO on discontinued SKU names—convert every quote to the three current Contact Center SKUs or Premium before you compare.

Voice Telephony Is Never in the License - It Runs on Azure

Voice is the line item most likely to surprise a finance team, because the Contact Center Voice seat is not the telephony bill. The Contact Center Voice SKU ($95/user/month) or the combined Contact Center SKU ($110/user/month) grants the software entitlement to route, queue, transcribe, and handle voice conversations inside Dynamics 365. The actual PSTN calls—the dial tone, the per-minute carriage, the phone numbers—run on Azure Communication Services, which Microsoft’s pricing pages state explicitly is 'priced separately' (footnotes 3 and 8 on Contact Center; footnote 8 on Customer Service).

Azure Communication Services meters independently. Public ACS list rates useful for rough models (always re-check the Azure pricing calculator for your region): SIP Direct Routing is listed at $0.004 per minute inbound and $0.004 per minute outbound; voice/video over IP at $0.004 per user minute; mixed audio call recording at $0.002 per minute. Microsoft Learn voice-channel pricing scenarios still walk Omnichannel/Contact Center calls as per-participant ACS legs—so a 10-minute Direct Routing handoff can bill multiple $0.004 legs depending on path. Phone-number rental and PSTN connectivity charges stack on top.

The important flexibility is that you are not forced to buy Microsoft’s calling plan. Microsoft confirms that 'existing carriers and calling plans are supported by Azure Direct Routing,' so an organization with an existing SIP trunk or carrier contract can bring that connectivity into Dynamics 365 rather than repurchasing it. For teams that prefer an all-Microsoft calling path, Microsoft Teams Phone Standard ($10/user/month, paid yearly) adds the PBX feature pack native to Teams—but that is a telephony license, not a substitute for the Contact Center seat, and Teams Phone extensibility has its own stacked requirements (see the Teams Phone section above).

The budgeting reality: a 25-seat voice team can run a four- or five-figure monthly Azure Communication Services line that never appears on the Dynamics 365 invoice. The two-invoice problem is structural—the Dynamics invoice carries the licenses, a separate Azure invoice carries the telephony consumption. Forecast telephony volume (inbound minutes, outbound minutes, numbers) separately from the seat count, and decide between Direct Routing (bring your own carrier), Operator Connect, a Microsoft calling plan, or Teams Phone extensibility early, because it changes both the cost profile and the integration effort.

Teams Phone Extensibility: Extra Licenses Beyond the Contact Center Seat

Azure Communication Services is not the only voice path. Teams Phone extensibility for Dynamics 365 Contact Center reached general availability in 2025 and is called out in the 2026 licensing materials: organizations can apply existing Teams Phone licenses so Contact Center agents place and receive calls on the Teams telephony backbone instead of building a pure ACS-only estate. That path is attractive when the company already standardized on Teams Phone, Operator Connect, or Direct Routing for corporate voice.

It is not free with the Contact Center seat. The March 2026 Dynamics 365 Licensing Guide pattern requires two sets of licenses. On the service line (inbound number / call queue): a Teams Phone Resource Account license (assigned to a resource account, not a person) plus PSTN connectivity via Microsoft Calling Plans, Operator Connect, or Direct Routing. For each Contact Center service representative: a Contact Center Voice or combined user license, a qualifying Microsoft Teams license, and a Microsoft Teams Phone license (included in Microsoft 365 E5 for many tenants, otherwise Teams Phone Standard at $10/user/month paid yearly as a standalone add-on).

Miss any of those three agent-side pieces and Teams Phone extensibility does not work for that person—there is no soft workaround. ACS-native Contact Center voice remains the simpler path when you do not want to dual-license Teams Phone, or when the contact center should stay decoupled from corporate Teams telephony. Budget both paths before design freeze: ACS consumption-only versus Teams Phone seat plus ACS/PSTN connectivity. Practitioner write-ups of the March 2026 guide also note that Teams Phone extensibility does not currently hand each agent a unique direct-inward-dial number inside the Contact Center app without additional user-level PSTN setup.

Copilot Credits: The AI Bill That Sits on Top of the Seats

Layered on top of every Contact Center seat is the Copilot Credit consumption model that powers the AI features. Microsoft's pricing page is explicit that the four contact-center agents - Customer Intent Agent, Customer Knowledge Management Agent, Case Management Agent, and Quality Evaluation Agent - each 'Requires Copilot Credits (sold separately)' on the Contact Center, Contact Center Digital, and Contact Center Voice SKUs. The same credits drive the inline AI assist: email drafting, case summarization, Q&A over knowledge, and real-time conversation intelligence during calls. On the a la carte Contact Center SKUs, you budget for credit consumption from day one.

Customer Service Premium inverts this. Microsoft's footnote 6 confirms that 'Base Copilot Credit capacity [is] included in Dynamics 365 Customer Service Premium,' so a Premium bundle ships with a pooled credit entitlement rather than forcing a separate credit purchase. This is the second reason - after the seat-stack arithmetic - that Premium tends to win the cases-plus-channels comparison: it folds the credit layer into the per-seat price where the a la carte stack bills it on top.

Copilot Credits themselves run on a linked Azure subscription and come in two payment cadences. Pay-as-you-go bills monthly in arrears for the credits you actually consumed, with no upfront commitment. Prepaid Copilot Credit Commit Units let you choose a credit amount up front and save up to roughly 20% versus pay-as-you-go, with automatic pay-as-you-go coverage when the prepaid pool runs out. There is no feature difference between the two - only how you pay. The discipline that matters: on a la carte Contact Center SKUs, monitor pooled credit consumption before it tips into overage; on Premium, monitor the included envelope the same way.

Quality Evaluation Agent closed and real-time conversation evaluation remains marked as preview on the Contact Center pricing page (footnote 5 as of August 2026), so treat multi-conversation QA automation as a roadmap item in commercial commitments rather than a fully GA entitlement. Release-wave coverage for 2026 also pushes custom voice for voice agents and broader agentic orchestration—cost landings still run through Copilot Credits and ACS voice paths, not through a new flat 'AI seat.' When Microsoft ships cheaper, faster voice models into Contact Center (for example MAI-Voice public previews discussed publicly in mid-2026), your software seat may stay constant while consumption per minute falls—model credit and ACS unit costs as variable, not fixed.

Six Licensing Mistakes That Inflate an Omnichannel Bill

Across the Dynamics 365 omnichannel scopes Flectic runs, the same mistakes repeat. The first is stacking the Digital and Voice add-ons ($95 + $95 = $190) instead of buying the combined Contact Center SKU ($110) when both channel families are needed. The second is the inverse of the stack-math rule: buying Customer Service Enterprise plus Contact Center a la carte ($215/user/month) when Customer Service Premium ($195) bundles both and includes credits. These two alone can move a 25-seat bill by tens of thousands of dollars per year.

The third mistake is over-seating or treating seats as concurrent. Licensing supervisors, quality analysts, and back-office case workers on Contact Center seats they never use inflates the per-user line for no capability gain—and floating one named seat across two simultaneous shift workers is not allowed. The fourth is forgetting the bills that never appear on the Dynamics invoice: Azure Communication Services telephony for any voice channel, Copilot Studio capacity for digital messaging volume, and Copilot Credit overage for AI agents. A scope that looks affordable on the license quote can double once consumption lands.

The fifth is ignoring attach eligibility—if you already hold a qualifying Dynamics 365 base, Contact Center attach discounts (footnote 1) and Customer Service attach pricing should be modeled before you commit to list. The sixth is under-licensing the Teams Phone extensibility path: buying Contact Center Voice while forgetting Teams Phone Standard, a resource account, or PSTN connectivity, then discovering mid-project that agents cannot place calls on the Teams backbone. Every one of these is a composition error, not a feature error. The channel capability is the same; the cost is not.

A 25-Agent Omnichannel Invoice: Seats Plus Consumption Layers

Pricing abstractions resolve fastest with a worked invoice. Take a 25-agent team that needs chat, SMS, and voice—a true omnichannel contact center—and compare license stacks at list price, then layer illustrative consumption so finance sees the second invoice. Stack A, Customer Service Premium: 25 × $195 × 12 = $58,500 per year, which includes Customer Service Enterprise, the full Contact Center capability, and base Copilot Credit capacity. Stack B, Customer Service Enterprise plus Contact Center a la carte: (105 + 110) × 25 × 12 = $64,500 per year—$6,000 more than Premium, and without the included credit capacity. Stack C, Contact Center standalone with cases in Salesforce: 25 × $110 × 12 = $33,000 per year, with no Dynamics 365 case management.

Now add consumption that list-price seat tables omit. Suppose the same 25-agent team handles roughly 12,000 agent voice minutes and 8,000 outbound minutes per month on SIP Direct Routing at the published ACS $0.004/min legs, plus mixed audio recording on a subset of calls, plus Copilot Studio bot traffic for chat deflection. Even a conservative ACS Direct Routing model at ~20,000 billable minute-legs × $0.004 is only ~$80/month on pure minute math—until you multiply participant legs, add number rental, recording, transcription storage, and peak concurrency. Partner Azure-consumption write-ups for Contact Center routinely show that VOIP and recording lines dwarf naive minute estimates once IVR, dual legs, and recording are included. Put a dedicated Azure line in the TCO even if your first-month estimate is a placeholder.

If those 25 agents also take the Teams Phone extensibility path and do not already have Teams Phone via Microsoft 365 E5, add Teams Phone Standard at $10/user/month: 25 × $10 × 12 = $3,000/year on top of Premium or a la carte seats. That is still usually smaller than getting the Dynamics seat composition wrong, but it is a real third invoice (Microsoft 365 commerce) beside Dynamics and Azure.

The decision still reads off the arithmetic. For a cases-plus-channels team on Dynamics 365, Stack A (Premium) beats Stack B by $6,000/year on license alone and further on credits—so Premium is the default unless an attach discount changes Stack B’s math. Stack C is cheapest only because it omits case management entirely. None of the three seat figures alone is a complete omnichannel TCO: add ACS telephony, Copilot Studio digital capacity, Copilot Credit overage, Dataverse storage, Teams Phone if used, and implementation before you sign.

When Dynamics 365 Omnichannel Is Not the Right Answer

Dynamics 365 Contact Center is the right answer when you need enterprise-grade unified routing, deep Microsoft-stack integration, bring-your-own-carrier voice via Azure Direct Routing, and you can absorb the Copilot Credit and Azure Communication Services consumption that the architecture implies. For a smaller service team whose requirement is more modest - live chat on a support site, email-to-case, a knowledge base, and basic SLAs - the per-seat-plus-consumption economics of a full contact-center stack can dwarf the actual workload.

Odoo's live chat, helpdesk, and email modules are part of the Odoo Enterprise subscription rather than metered per conversing seat, per Copilot Credit, and per voice minute. For an SME that does not need Contact Center IVR, unified routing across a dozen channels, or Premium-tier AI agents, Odoo can deliver a functional support inbox at a fraction of the all-in cost - and the chat and email sending is handled through Odoo's own or configured providers without a separate Azure telephony invoice. The decision should follow the requirement, not the vendor.

This is exactly where being platform-neutral matters. Flectic implements both Dynamics 365 and Odoo for SMEs across Canada, the UK, and the US, so the recommendation follows the scenario. When the honest answer is a simpler chat-and-email workload on Odoo, we say so; when it is a true multichannel contact center on Dynamics 365, we scope the license stack properly and ship it. The broader CRM context - including how an omnichannel service desk fits alongside sales and marketing - is worth reviewing alongside this licensing page.

How Flectic Helps You Stack the Right Licenses

Flectic is an AI-driven ERP and CRM partner for SMEs across Canada, the UK, and the US, implementing both Dynamics 365 and Odoo. We do not sell licenses. We map your service scenario to the right platform and license stack, then ship it using an AI-accelerated delivery model designed to deliver up to 3x faster than a conventional partner engagement for well-scoped SME work.

On omnichannel licensing specifically, we run a platform-neutral license-stack exercise: we check whether Customer Service Premium or an Enterprise-plus-Contact-Center attach is cheaper for your cases-plus-channels team, verify attach eligibility against your existing Dynamics 365 estate, right-size the Contact Center seat count by stripping out non-conversing users, forecast Azure Communication Services telephony from your real call volume, and model Copilot Studio digital capacity and Copilot Credit consumption from your actual conversation and bot-deflection numbers. The output is a grounded multi-year TCO with no lowballing - even when the honest answer is Odoo rather than a Dynamics 365 contact-center stack.

If the result is Dynamics 365, we implement it - Customer Service, Contact Center, voice on Azure Communication Services, and the Copilot layer. If the result is Odoo, we implement that. Either way, you walk into the first conversation with a defensible license-stack model rather than a vendor list price. Book an ERP Readiness Call and we will bring the worked stack arithmetic to the table.

Frequently asked questions