The Customer Service Workspace in Dynamics 365

The Customer Service Workspace is Dynamics 365's modern agent desktop — a multi-session, productivity-paneled, omnichannel-ready environment that replaces the older single-session Customer Service Hub for serious contact-centre work. Understanding what it adds and where it differs from the Hub matters for any new Customer Service deployment.

The Hub baseline. Customer Service Hub is the model-driven app most agents historically used. Single browser tab = single case. Navigation is between cases by opening a new tab. Adequate for low-volume, knowledge-driven service work.

What Workspace adds.

• Multi-session tabs within a single browser window — agents handle several conversations or cases simultaneously.
• Productivity pane — collapsible side panel with smart assist, knowledge, similar cases, suggested actions.
• Agent scripts — guided steps tied to case type or conversation context.
• Omnichannel integration — voice, chat, SMS, social, email surfaces unified.
• Macros — pre-canned actions agents trigger (send template, close case, escalate).
• Customisations specific to Workspace — layouts and components designed for the multi-session model.

Sessions. A session is a working context — a case, a conversation, a customer record. Multiple sessions are stacked as tabs at the top of the workspace. Switching between sessions preserves state per session: forms half-edited, conversations mid-thread.

For agents handling chat or voice (where multiple conversations may be active simultaneously), multi-session is essential. For email/case agents working one at a time, single-session may suffice.

Productivity pane. A vertical side panel that contextually surfaces:

• Smart assist — AI suggestions based on conversation content.
• Knowledge search — search KB and articles inline.
• Similar cases — related cases for context.
• Agent script — step-by-step guidance.
• Customer summary — quick view of who the customer is and their history.

The pane is configurable per session type; what an inbound voice call shows differs from a returning case.

Agent scripts. Procedural guidance:

• Linear scripts — checklist of steps.
• Decision-tree scripts — branching based on customer responses.
• Automated step actions — some steps trigger flows or macros.

Scripts standardise call handling; quality and speed both improve once agents follow them. Building scripts is meaningful work — they must reflect real-world variability, not idealised playbooks.

Macros. Pre-defined sequences of actions:

• Send a template email.
• Create a follow-up task.
• Update case status and route.
• Open a specific URL with customer ID.

Macros eliminate repetitive clicks. Defined in the productivity pane configuration; agents trigger by button.

Omnichannel surfaces. When Omnichannel for Customer Service is installed alongside Workspace:

• Inbound chat, SMS, voice route to agent's queue.
• Conversation surface in the workspace handles the medium.
• Customer profile, history, sentiment displayed in the productivity pane.

The unified surface means agents don't context-switch between systems for different channels.

Workspace vs Hub — when to use each.

• Hub — small teams, case-only workload, simple service.
• Workspace — multi-channel teams, chat/voice agents, productivity-pane-heavy workflows.

Migration from Hub to Workspace is straightforward for the data side (same Dataverse), heavier for the UX side (forms, dashboards, customisations may need rework).

Customisations. Workspace is a model-driven app like Hub. Customisations:

• Site maps — what entities and views are accessible.
• Forms — record forms; can be Workspace-specific.
• Dashboards — at the workspace level.
• Productivity pane components — custom side-panel widgets.

Some legacy Hub customisations don't transfer cleanly; budget rework time.

Performance. Multi-session is heavier than single-session:

• Each session loads forms and data.
• High session counts can degrade performance.
• Modern browsers handle 5–10 sessions comfortably; beyond that, agents stack their own tabs.

Common pitfalls.

• Workspace deployed without scripts or macros. Agents get the multi-tab feature but no productivity uplift; experience worse than Hub.
• Productivity pane configured incorrectly. Wrong components for the channel; cluttered.
• Switching costs underestimated. Migrating from Hub means retraining, rewriting customisations, retesting; budget weeks not days.
• Session limit hit. Heavy use opens many sessions; performance drops. Set agent training: close sessions promptly.
• Custom code on forms broken. JavaScript form scripts running differently across Workspace sessions; test carefully.

Strategic positioning. Workspace is Microsoft's strategic direction for Customer Service agent UX. New investments should land on Workspace; existing Hub deployments should plan migration on a reasonable timeline. Maintaining both adds complexity; commit to one as your primary surface and design customisations for that target.

Operational rule. Choose Workspace by default for new Customer Service deployments. Ensure agent scripts, macros, and productivity pane components are designed before go-live — the multi-tab capability alone isn't worth the migration effort, but the productivity layer on top of it transforms agent efficiency.