Dynamics 365 Contact Center - Architecture Map

📋 Architecture Overview

▼

Core Architecture Flow

CHANNELS → WORKSTREAMS → ROUTING RULES → QUEUES → AGENTS

Each layer adds intelligence, context, and control to ensure optimal customer service delivery through AI-powered routing and intelligent work distribution.

Key Layers

🌐 Channels

Entry points for customer engagement across multiple communication mediums

🔄 Workstreams

Containers that enrich, route, and configure work item behavior

📍 Routing Rules

Intelligent classification and route-to-queue decision logic

📥 Queues

Collections that organize work items for distribution

👥 Agents

Service representatives who handle customer interactions

🤖 AI Features

Copilot assistance, sentiment analysis, and intelligent routing

🗺️ Visual Architecture Flow

▼

📱 CHANNELS - Customer Engagement Layer

📞

Voice

PSTN Calls

💬

Chat

Live Chat

📱

SMS

Text Messages

📲

Social

FB/WhatsApp

👔

Teams

MS Teams

📋

Records

Cases/Emails

⬇

🔄 WORKSTREAMS - Routing & Configuration Layer

🔄

Messaging Workstream

Chat, SMS, Social, Teams

📞

Voice Workstream

Phone Calls (Push Only)

📝

Record Workstream

Cases, Emails, Records

⬇

🎯 ROUTING RULES - Intelligent Routing Layer

🏷️

Classification Rules

Categorize & Add Context

🎯

Route-to-Queue Rules

Condition-Based Routing

🛡️

Fallback Queue

Safety Net

⬇

📥 QUEUES - Work Distribution Layer

📥

Messaging Queue

Chat, SMS, Social

📞

Voice Queue

Phone Calls

📋

Record Queue

Cases & Emails

⬇

⚙️ ASSIGNMENT ALGORITHM - Evaluation Layer

🎯

Skills

Matching

🟢

Presence

Availability

⚡

Capacity

Workload

⬇

👥 AGENTS - Service Representative Layer

👤

Agents / Representatives

Handle Customer Interactions

📊 Assignment Methods

⚡ Highest Capacity

Routes to agent with most available capacity

🔄 Round Robin

Rotates assignments in order

😴 Least Active

Routes to least recently active agent

⚙️ Custom

Rule-based custom assignment

🔗 Key Relationships

▼

⬇️ Top-Down Relationships (Architecture Flow)

Channel

→

Workstream

Many-to-One

1. Channel → Workstream (Many-to-One)

Forward: Multiple channels of the SAME type can share one workstream

Example: 3 chat channels → 1 messaging workstream

Reverse: ✅ A workstream can have MULTIPLE channels attached (of the same type)

Phone Number

→

Voice Channel

→

Workstream

Many-to-One

2. Phone Number → Voice Channel → Workstream (Many-to-One)

Forward: Each phone number is associated with exactly ONE voice channel, which belongs to ONE workstream

Constraint: Phone numbers must have inbound calls enabled and cannot be shared across workstreams

Reverse: ✅ A workstream CAN have MULTIPLE voice channels, each with a different phone number

Use Case: Multilingual support - configure multiple voice channels with different phone numbers for different languages (e.g., Spanish number, German number, French number all in one workstream)

Workstream

→

Queues

One-to-Many

3. Workstream → Queues (One-to-Many)

Forward: One workstream can route to multiple queues via route-to-queue rules

Required: Must have one fallback queue as safety net

Reverse: ✅ A queue CAN receive work from MULTIPLE workstreams (of matching channel type)

Example: A "VIP Voice Queue" can receive calls from both "Premium Support Workstream" and "Executive Support Workstream"

Queue

→

Agents

Many-to-Many

4. Queue → Agents (Many-to-Many)

Forward: Queues can have multiple agents as members

Reverse: ✅ Agents CAN be members of MULTIPLE queues

Distribution: Based on assignment method and availability

Example: Agent John can be in "Voice Queue", "Chat Queue", and "VIP Queue" simultaneously

⬆️ Bottom-Up Relationships (Reverse Flow)

Agent Perspective:

✅ An agent can be a member of multiple queues
✅ An agent receives work from all queues they belong to
✅ Work assignment depends on capacity, skills, and presence across all queues
📊 Agents can view work items from all their queues in the Omnichannel Agent Dashboard
Example: Agent Sarah in "Voice Queue", "VIP Chat Queue", and "Email Queue"

Queue Perspective:

✅ A queue can receive work from multiple workstreams (matching channel type)
✅ A queue can have multiple agents as members
✅ A queue can be a fallback queue for multiple workstreams
❌ A queue CANNOT receive work from workstreams of different channel types
Example: "Premium Support Voice Queue" receives calls from both "Executive Support Workstream" and "VIP Customer Workstream"

Workstream Perspective:

✅ A workstream can have multiple channels of the same type attached
✅ A workstream can route to multiple queues
✅ A workstream can use the same queue as other workstreams
✅ A voice workstream can have MULTIPLE phone numbers through multiple voice channels
💡 Common use case: Multiple voice channels with different phone numbers for multilingual support

Channel Perspective:

📌 A channel belongs to ONE workstream (based on configuration flow)
✅ Multiple channels of the same type can share one workstream
Example: 3 different chat widget channels → all in 1 messaging workstream

🔒 Type Constraints

Workstream → Channel Type Constraint

Messaging workstream → Messaging queues only
Voice workstream → Voice queues only
Record workstream → Record queues only
❌ Cross-type routing NOT allowed
✅ Multiple workstreams of the same type CAN share the same queue

Workstream Type → Distribution Mode

Voice: Push mode ONLY
Messaging: Push or Pick mode
Record: Push or Pick mode
⚠️ Mode CANNOT be changed after creation

📊 Relationship Summary Table

From	To	Cardinality	Can Reverse?
Channel	Workstream	Many-to-One	✅ Yes (One workstream → Many channels)
Phone Number	Voice Channel	One-to-One	❌ No (Each phone number → One voice channel only)
Voice Channel	Workstream	Many-to-One	✅ Yes (One workstream ← Many voice channels with different phone numbers)
Workstream	Queue	One-to-Many	✅ Yes (One queue ← Many workstreams)
Queue	Agent	Many-to-Many	✅ Yes (fully bidirectional)

🌐 Channels 7 Types

▼

Available Channel Types

📞 Voice Channel

PSTN calling via Azure Communication Services
Real-time AI transcription
Sentiment analysis during calls
Phone numbers (1:1 with workstream)

💬 Chat Channel

Live chat support
Web widget integration
Persistent chat capability
Context variables support

📱 SMS Channel

Azure Communication Services
Twilio integration
Two-way messaging
Representative affinity

📲 Social Channels

Facebook Messenger
WhatsApp (via Twilio)
Apple Messages for Business
LINE messaging

👔 Microsoft Teams

Native Teams integration
Collaboration features
Expert swarming
Consultation capabilities

🔧 Custom Messaging

Custom channel development
Direct Line Bot Framework
Line-of-business channels
Telegram and others

📋 Entity Records

Cases routing
Email management
Standard business records
Custom entities

Implementation Pattern

Step 1: Establish account requirements with channel provider

Step 2: Configure the workstream in admin center

Step 3: Configure channel and attach to workstream

Step 4: Exchange authentication data (tokens/secrets)

🔄 Workstreams Core Component

▼

Workstream Types

Type	Routes	Distribution Modes
Messaging	Chat, SMS, Social channels, Microsoft Teams	Push or Pick
Voice	Phone calls (via phone number)	Push only
Record	Cases, Emails, Records	Push or Pick

Work Distribution Modes

🔔 Push Mode

System automatically routes work items
Agents receive message alerts
Required for voice workstreams
Supports bot integration

🎯 Pick Mode

Agents manually select work items
From "Open work items" list
Agent-controlled workload
Not available for voice

⚠️ Important: Work distribution mode CANNOT be changed after workstream creation!

Configuration Options

Capacity settings: Unit-based or profile-based
Allowed presences: Define which statuses can receive work
Skill matching: Exact Match, Closest Match, or None
Session templates: Customize agent workspace
Agent notifications: Configure alert behavior
Context variables: Pass custom data through routing
Representative affinity: Same agent handles returning items
Auto-close after inactivity: Timeout settings
Block capacity for wrap up: Post-work processing time

☎️ Phone Numbers

▼

Phone Number Configuration

Relationship: Phone Number → Voice Channel → Workstream
• Each phone number is associated with exactly ONE voice channel
• Each voice channel belongs to ONE workstream
• ✅ One workstream CAN have MULTIPLE voice channels (each with different phone numbers)

Configuration Steps

Provision: Acquire phone numbers via Azure Communication Services

Enable: Enable inbound calls on the phone numbers

Create Voice Channels: In the workstream, create multiple voice channels (one per phone number)

Associate: Link each phone number to its respective voice channel in the workstream

Configure: Set up language settings and voice profiles for each channel

Multiple Phone Numbers per Workstream

Use Case: Multilingual Support

Create multiple voice channels within one workstream
Each voice channel has a different phone number
Each voice channel configured with a different primary language
Example: +1-555-0100 (Spanish), +1-555-0200 (German), +1-555-0300 (French) all in one workstream

Single Phone Number - Multiple Languages

Alternatively, one phone number can support multiple languages with:

Primary language (first greeting)
Additional language options for customers
Hold and wait music configuration per language
Voice profile settings (voice, style, speed, pitch) per language

⚠️ Constraints:

Only numbers with inbound calls enabled are available
Each phone number can only be in ONE voice channel
Cannot associate number already linked to another workstream
Anonymous calls only supported via Azure Direct Routing
Cannot edit or upgrade phone number features after connecting to workstream

📍 Routing Rules

▼

Rule Types

🏷️ Classification Rules

Categorize incoming work items
Add context and metadata
Evaluate customer parameters
Enable intelligent routing decisions

🎯 Route-to-Queue Rules

Condition-based routing logic
Priority-based assignments
Skill-based matching
Multiple rules per workstream

Fallback Queue

Safety Net Mechanism: Every workstream must have a fallback queue that receives work items when:

No route-to-queue rules match
Classification errors occur
Route-to-queue rule errors occur

Default Routing Behavior

For simple routing scenarios, no custom rules are required:

Voice: All incoming calls → Default voice queue → Round robin assignment
Messaging: All conversations → Default messaging queue → Round robin assignment
Records: All records → Default entity queue → Round robin assignment

📥 Queues

▼

Queue Types

Queue Type	Workable Items	Purpose
Messaging Queue	Chat, SMS, Social messages	Route live conversations
Voice Queue	Inbound/outbound calls	Route phone calls
Record Queue	Cases, emails, records	Route entity records

⚠️ Type Constraint: Queue type must match workstream channel type. Cross-type routing is NOT allowed. For example, chat conversations can only be transferred to messaging queues.

Assignment Methods

⚡ Highest Capacity

Routes to agent with most available capacity, considering skills and presence

🔄 Round Robin

Rotates assignments based on queue membership order, updates based on assignment history

😴 Least Active

Routes to agent who has been least active recently

⚙️ Custom Assignment

Build custom rules using rulesets for priority, severity, and capacity

Queue Configuration

Queue Priority: Numeric priority (lower number = higher priority)
Operating Hours: Schedules and time zones
Overflow Management: Redirect work when thresholds exceeded
Agent Membership: Assign agents to queues
Default Queues: System-defined with all agents included

Default Queues (System-Defined)

Default Messaging Queue

All agents included by default for chat, SMS, and Teams

Default Voice Queue

All agents included by default for phone calls

Default Entity Queue

All agents included by default for cases and records

👥 Agents / Representatives

▼

Agent Configuration

📋 Queue Assignments

Agents can be members of multiple queues. Work is distributed based on queue membership and availability.

⚡ Capacity Profile

Defines workload capacity - unit-based or profile-based. Controls how many concurrent work items an agent can handle.

🎯 Skills

Skill-based routing matches work items to agents with required skills using exact or closest match algorithms.

🟢 Presence Status

Available, Busy, Away, Do Not Disturb, etc. Only allowed presences receive work assignments.

Agent Experience

Mode	Experience	Use Case
Push Mode	Receives auto-assigned work with notifications	Voice, urgent messaging, high-volume
Pick Mode	Manually selects from "Open work items"	Cases, emails, specialized work

Advanced Features

Representative Affinity: Same agent handles returning work items (enabled by default for persistent channels)
Wrap-up Time: Capacity blocked after completing work (configurable: always, never, or custom duration)
Channel-specific Capacity: Different capacity limits per channel type
Multi-channel Support: Handle voice, chat, and records simultaneously based on capacity

Assignment Algorithm Factors

Assignment Decision Considers:
    │
    ├─ Agent Presence (Available, Busy, DND)
    │
    ├─ Agent Capacity (current workload vs. max capacity)
    │
    ├─ Agent Skills (if skill matching enabled)
    │
    ├─ Queue Membership (agent must be in the queue)
    │
    ├─ Assignment Method (Highest Capacity, Round Robin, etc.)
    │
    └─ Priority & Routing Rules (from workstream configuration)

🔄 Routing Flow Example

▼

Complete Call Routing Journey

Customer Action: Customer calls +1-555-0100

Phone Number Lookup: Phone Number (+1-555-0100) associated with "Premium Support Voice Workstream"

Classification: Classification Rules evaluate call context (customer type, product, history)

Route-to-Queue Decision:
• Rule 1: If customer = "Premium" → "VIP Voice Queue"
• Rule 2: If product = "Product A" → "Product A Voice Queue"
• No match → "Fallback Voice Queue"

Queue Processing: Queue receives call and applies assignment method (e.g., Highest Capacity)

Agent Evaluation: Assignment algorithm evaluates:
• Agent presence (Available, Busy, DND)
• Agent capacity (current workload vs. max)
• Agent skills (if skill matching enabled)
• Queue membership

Assignment: Call assigned to Agent with highest capacity + matching skills + allowed presence

Agent Notification: Agent receives notification and call appears in workspace with full context

Post-Call: After call ends, agent enters wrap-up time (capacity blocked for configured duration)

🤖 AI & Intelligence Features

▼

Unified Intelligent Routing (AI-Infused)

😊 Sentiment Analysis

Real-time emotion detection to route frustrated customers to experienced agents

📊 Predicted Effort

AI estimates complexity to match work with agent expertise

🎯 Skills Matching

Intelligent matching of required skills to agent capabilities

🟢 Presence Awareness

Real-time availability tracking for optimal assignment

⚡ Capacity Optimization

Dynamic workload balancing across agent pool

👤 Customer Parameters

Historical data and customer context evaluation

Agent Copilot Features

Knowledge Chat/Search: Q&A format knowledge retrieval, not keyword-based
Agent Prompting: AI-powered suggestions and next-best-action recommendations
Email Draft Generation: Automated response drafting based on context
Case Summary Generation: AI-generated case summaries for quick context
Conversation Summaries: Automatic conversation recap and key points extraction
Live Call Transcription: Real-time transcription during voice calls
Call Sentiment Analysis: Continuous sentiment monitoring during conversations

🔧 Supporting Components

▼

🤖 Bots

Connected from Copilot Studio
Push-based workstreams only
Pre-conversation automation
Handoff to human agents

📄 Templates

Session templates
Notification templates
Consistent agent experience
Customizable layouts

🔢 Context Variables

Custom data passing
Through routing pipeline
Available to agents
Integration support

🕐 Operating Hours

Queue-based schedules
Time zone support
Business hours routing
After-hours handling

📊 Capacity Profiles

Define agent workload limits
Channel-specific capacity
Unit or profile-based
Dynamic adjustment

💡 Smart Assist

AI-powered suggestions
Knowledge article recommendations
Quick replies library
Real-time assistance

⚠️ Important Constraints

▼

✓ Unified routing must be enabled for Record workstreams

✓ Work distribution mode (Push/Pick) CANNOT be changed after workstream creation

✓ Voice workstreams support PUSH mode ONLY

✓ Phone numbers can only be associated with ONE workstream at a time

✓ Queues and workstreams must have matching channel types

✓ Cross-queue transfers only allowed within same channel type

✓ Bots receive conversations only in push-based workstreams

✓ Representative affinity only applies to push-type work distribution

✓ System Administrator role OR secure column permissions required for configuration

📐 Configuration Hierarchy

▼

Organization/Environment
    │
    ├─ Channels (provision & configure)
    │   ├─ Voice Channel
    │   │   └─ Phone Numbers (acquire via Azure Communication Services)
    │   ├─ Chat Channel
    │   ├─ SMS Channel (Azure Communication Services or Twilio)
    │   ├─ Social Channels (Facebook, WhatsApp, Apple Messages, LINE)
    │   ├─ Microsoft Teams
    │   └─ Custom Messaging Channels
    │
    ├─ Workstreams (create & configure)
    │   ├─ Type selection (Messaging, Voice, Record)
    │   ├─ Channel association (attach channels)
    │   ├─ Work distribution mode (Push or Pick)
    │   ├─ Capacity settings
    │   ├─ Allowed presences
    │   ├─ Skill matching algorithm
    │   ├─ Classification rules
    │   ├─ Route-to-queue rules
    │   └─ Fallback queue
    │
    ├─ Queues (create & configure)
    │   ├─ Queue type (Messaging, Voice, Record)
    │   ├─ Assignment method
    │   ├─ Priority
    │   ├─ Operating hours
    │   ├─ Overflow management
    │   └─ Agent membership
    │
    ├─ Agents/Representatives (configure)
    │   ├─ Queue assignments
    │   ├─ Capacity profile
    │   ├─ Skills
    │   └─ Presence management
    │
    └─ Supporting Components
        ├─ Capacity Profiles
        ├─ Session Templates
        ├─ Notification Templates
        ├─ Context Variables
        ├─ Operating Hours
        ├─ Bots/Agents (Copilot Studio)
        └─ Smart Assist configurations