Service — Dynamics 365 Contact Center
Contact centres designed for the volumes, integrations and teams that have to live with them.
End-to-end design and delivery of Microsoft Dynamics 365 Contact Center, from discovery through to live operations. I have architected contact centres at national and worldwide scale, where the design has to survive real call volumes and a working operations team on day one.
What the work involves
A contact centre is more than its software
Dynamics 365 Contact Center brings voice, digital channels and AI agents into one platform. The hard part is rarely the licensing — it is the routing logic, the telephony integration, the knowledge the AI agents draw on, the reporting the operations team actually needs, and the cut-over that gets you live without dropping calls.
A typical engagement covers:
- Discovery of current channels, telephony, queues and the operational pain that prompted the change.
- Channel and routing design — voice, chat, email and social, with the rules that decide who gets what.
- AI agent design — what the virtual agents handle, what they escalate, and the knowledge they are grounded on.
- Telephony and CRM integration — SBC, carrier, and the customer record the agent sees on answer.
- Reporting and the operational playbooks supervisors run the floor with.
- The cut-over plan, sequenced so you reach go-live cleanly.
The architecture
How the pieces fit together
Where it tends to go wrong
The three places it slips
Contact centre programmes usually slip in three places: the telephony integration is treated as an afterthought and surfaces late; the AI agents are launched without the knowledge or guardrails to be trusted with real customers; and the reporting is built for a demo rather than for the supervisor running the floor at 4pm on a Friday.
I bring those three to the front of the design, name the trade-offs early, and stay close enough to delivery that they do not quietly drift. The aim is a contact centre your operations team can run and grow, not one they work around.
Example projects
Two contact centre programmes, at scale
Two examples of the kind of multi-country contact centre work this service covers, where the architecture has to hold up across borders, operating models and regulators.
Example 1 — Energy · 7 countries
A global energy company — contact centres and BPOs across seven countries
A global energy company running customer contact across seven countries in the United States, South America and Europe, through a mix of in-house contact centres and outsourced BPO partners. The work was to bring those sites onto one coherent Dynamics 365 Contact Center architecture — consistent routing, reporting and agent experience — while respecting the real differences at each location: telephony carriers, languages, time zones, and the line between what the in-house teams and the BPOs each handle. The design had to give the group a single operational picture without forcing every site into an identical mould.
Example 2 — Manufacturing · Europe & China
A manufacturing company — a contact centre spanning six European countries and China
A manufacturing company running contact centre operations with staff in six European countries and in China. Here the central challenge was architectural and regulatory at once: a single platform that worked for distributed teams, while resolving the data residency, cross-border transfer and compliance constraints that come with operating across the EU and China together. The design had to be defensible to each jurisdiction, not just functional — deciding what data could sit where, how it moved, and where the boundaries had to be drawn so the platform stayed both compliant and usable.
Engagement shapes
Three ways to bring a CCaaS programme together
Most engagements are fractional — I sit inside your team for the months it takes to ship. A short discovery is the usual entry point.
2–3 weeks · fixed scope
CCaaS Programme Read
Diagnose where the CCaaS programme is, in language your sponsors and your delivery team can both stand behind.
Walk out with
- a current-state landscape across voice, digital and AI
- a target architecture with named trade-offs
- the next-quarter action list
2 days a week · 3-month minimum
Fractional CCaaS Architect
Hold the design across voice, digital channels, AI agents, telephony and reporting while your team delivers.
Walk out with
- integrated channel design
- an AI-agent / human-agent operating model
- a programme that holds together at go-live
6–8 weeks · project-shaped
CCaaS Go-Live Recovery
A focused intervention to get a slipping CCaaS go-live back on track.
Walk out with
- a re-baselined cutover plan
- the design fixes that unblock it
- renewed sponsor confidence
Planning or rescuing a contact centre?
Whether it is a new build or a programme that has stalled, the first conversation is a straightforward read of where things are and what a credible next step looks like.