GM Dynamics & Agentic AI Consulting

Shift planning and scheduling in Dynamics 365 Contact Center (Integrated Workforce Management to align agent availability with operational demand).

Real-time User Journey

This journey illustrates how a Workforce Scheduler moves from a theoretical capacity plan to an active, assigned shift schedule:

Template Creation: The Scheduler creates a Shift Template that defines the “ideal” workday, including specific slots for work periods, lunch, and training sessions.
Capacity Alignment: They link the template to a Capacity Plan (see previous feature) to ensure the number of shifts created matches the predicted customer demand.
Automated Scheduling: The Scheduler uses the Automated Scheduling tool to bulk-assign hundreds of agents to shifts based on their skills, contracts, and preferred time zones.
Intraday Adjustment: During the live shift, a sudden surge occurs. The Scheduler uses Manual Scheduling to quickly drag and drop an available agent into a “high-priority” shift slot to maintain coverage.
Break Distribution: The system automatically staggers break times across the team so that there is never a moment where all agents are offline simultaneously, ensuring continuous customer service.

Step-by-Step: How to Enable This Feature

To set up shift planning and scheduling within your environment:

Step 1: Admin Center Access Sign in to the Customer Service admin center or Contact Center admin center.
Step 2: Access Workforce Management Navigate to Operations > Workforce Management > Shift plans.
Step 3: Define Shift Templates Select New to create a template. Define the start/end times and add “Shift Activities” like:
- Work: For active customer handling.
- Break/Lunch: To ensure compliance and well-being.
- Training/Meeting: For non-operational tasks.
Step 4: Configure Shift Plans Create a Shift Plan record. Select the date range, the target Organization Units (teams), and the Shift Templates to be used.
Step 5: Run Automated Scheduling Within the Shift Plan, select Generate Schedule. The system will match agents to the required slots based on their profile data (skills and availability).
Step 6: Publish the Schedule Review the generated calendar. Once satisfied, click Publish. This makes the schedule visible to agents in their personal dashboards and ensures Unified Routing only sends work to agents currently on an active “Work” shift.

Infographic: Shift Planning & Scheduling Pillars

Pillar	Focus	Key Benefit
Shift Templates	Structured Workdays	Consistent inclusion of breaks and training.
Automated Scheduling	Speed and Scale	Reduced administrative work for large teams.
Skill Matching	Quality Control	Ensures specialized queues (e.g., Technical Support) are staffed by experts.
Break Staggering	Continuity	Eliminates “dead zones” in service coverage.
Unified Integration	Routing Accuracy	Automatically prevents calls from being routed to agents on lunch.

References

Shift planning and scheduling in Dynamics 365 Contact Center

Uncategorized

Predict workforce capacity needs in Dynamics 365 Contact Center

May 10, 2025May 3, 2026 Goloknath

Predict workforce capacity needs in Dynamics 365 Contact Center (Staffing forecasting to align workforce availability with customer service demand).

Real-time User Journey

This journey illustrates how a Workforce Manager uses the tool to maintain service levels:

Demand Assessment: The Manager opens the Capacity Planning dashboard to view the predicted number of agents needed for the upcoming month.
Granular Analysis (Short-term): They drill down into “Short-term planning” to see agent requirements in 15-minute intervals for the following day, identifying a specific gap between 10:00 AM and 11:30 AM.
Channel Slicing: The Manager applies “Data Slicing” to see if the shortage is specifically in the Voice queue or the Chat queue.
Strategic Shift Adjustment: Seeing a long-term upward trend in support requests, the Manager uses the “Long-term planning” view to justify a new hiring batch to the leadership team.
Optimization: The Manager adjusts existing agent shifts to cover the identified 15-minute gaps, ensuring that the contact center remains optimally staffed without overspending on unnecessary overtime.

Step-by-Step: How to Enable This Feature

To activate and configure capacity planning, follow these steps:

Step 1: Admin Center Access

Step 2: Navigate to Forecasting/Insights

Go to Operations > Insights > Capacity planning (Preview).

Step 3: Create a Planning Scenario

Select New to create a capacity plan. You must link it to an existing Volume Forecast (as the capacity plan uses volume data to calculate agent headcount).

Step 4: Define Service Level Goals

Input your target Service Level (e.g., 80% of calls answered in 20 seconds) and Average Handling Time (AHT). The AI uses these metrics to convert volume into “Required Headcount.”

Step 5: Configure Slicing Attributes

Select the dimensions you want to plan for, such as specific Channels, Queues, or Skills.

Step 6: Publish and Review

Save the configuration. The system will process the historical volume and your service goals to generate a staffing forecast. Review the interactive charts to finalize your workforce strategy.

Infographic: Capacity Planning Levels

Planning Level	Granularity	Primary Goal
Short-term	15-minute intervals	Real-time agility; handling daily volume spikes.
Long-term	Daily/Monthly	Strategic hiring and budget allocation.
Data Slicing	Channel/Queue/Skill	Targeted resource distribution across touchpoints.
Efficiency Metrics	SLA & AHT based	Balancing operational cost with customer satisfaction.

References

Predict workforce capacity needs in Dynamics 365 Contact Center

Uncategorized

Forecasting case and conversation volumes in Dynamics 365 Contact Center

May 4, 2025May 3, 2026 Goloknath

Forecasting case and conversation volumes in Dynamics 365 Contact Center (Advanced AI-driven demand prediction for strategic and operational planning).

Real-time User Journey

This journey describes how a Contact Center Supervisor uses forecasting to ensure operational readiness:

Trend Analysis: The Supervisor opens the Forecasting dashboard and reviews AI-generated predictions for the next quarter (Long-term) based on historical data.
Slicing the Data: They filter the forecast by Channel (e.g., Voice vs. Chat) and Queue to see where the heaviest volume is expected.
External Data Integration: To get a complete picture, the Supervisor Imports workload data from an external legacy system to include channels not yet migrated to Dynamics 365.
Operational Adjustment: Seeing a predicted surge in chat volume for the upcoming week (Short-term), the Supervisor adjusts agent shift schedules to ensure SLA compliance.
Export for Stakeholders: The Supervisor Exports the interactive charts into a spreadsheet for the monthly budget meeting to justify hiring additional seasonal staff.

Step-by-Step: How to Enable This Feature

To enable and configure forecasting, follow these steps in the Dynamics 365 admin interface:

Step 1: Access Configuration

Step 2: Navigate to Insights

Go to Operations > Insights > Forecasting.

Step 3: Create a Forecast Scenario

Select Create to set up a new forecasting scenario. You will need to:

Choose the Channel type (Case or Conversation).
Select the Historical period (Microsoft recommends at least 6–12 months of data for accuracy).
Step 4: Configure Data Slicing

Define the attributes for slicing (e.g., by Queue or Organization Unit). This allows the AI to generate more granular predictions.

Step 5: Run and Schedule

Save the scenario and run the initial forecast. You can set the forecast to Auto-refresh (daily or weekly) so the predictions stay current with the latest interaction data.

Step 6: (Optional) External Import

If using external data, navigate to the Import section within the forecasting tool and upload your .csv file following the provided schema.

Infographic: Forecasting Capabilities

Feature	Scope	Key Benefit
Long-term Forecasting	Daily volumes for months/years.	Strategic hiring and budget planning.
Short-term Forecasting	Intraday (15/30 min) intervals.	Precise agent scheduling and shift management.
Data Slicing	By Channel, Queue, or Skill.	Identifying specific bottlenecks before they happen.
External Integration	Supports 3rd party workload data.	Holistic view of the entire contact center.
Interactive Charts	Visual trend comparison.	Quick interpretation of complex demand patterns.

References

Forecasting case and conversation volumes in Dynamics 365 Contact Center

Uncategorized

Dynamics 365 Contact Center WhatsApp channel powered by Azure Communication Services (ACS)

May 3, 2025May 3, 2026 Goloknath

This feature marks the general availability of a native integration that allows businesses to engage with over two billion WhatsApp users directly within the Microsoft ecosystem, eliminating the need for third-party connectors.

Real-time User Journey

This journey illustrates how a customer interaction flows from a mobile device to a resolved business case:

Customer Initiation: A customer sends a WhatsApp message to the business’s verified number regarding a service inquiry.
Azure Communication Services (ACS) Gateway: The message is securely received by ACS, which acts as the intelligent bridge between Meta’s infrastructure and Microsoft’s cloud.
Intelligent Routing: Dynamics 365 Unified Routing analyzes the message intent and customer sentiment, then assigns the conversation to the most qualified available agent.
Agent Workspace Engagement: The agent receives a notification in the Omnichannel Agent Workspace. They see the customer’s identity and previous interaction history across all channels (Voice, Email, Chat).
AI-Powered Assistance: Copilot assists the agent in real-time by drafting suggested responses, translating messages if necessary, and summarizing long conversation threads to speed up resolution.
Asynchronous Resolution: If the agent needs to research an issue, the customer can close their app; the agent sends a reply later, and the customer receives a push notification on WhatsApp to continue the thread.

Step-by-Step: How to Enable This Feature

To enable the WhatsApp channel, you must coordinate settings across the Azure Portal, Meta Business Suite, and Dynamics 365.

Step 1: Azure Resource Setup

Create an Azure Communication Services (ACS) resource in the Azure Portal. Ensure the resource is in the same tenant as your Dynamics 365 environment.

Step 2: Connect Meta Business Account

Within the ACS resource, navigate to Advanced Messaging > Channels. Select WhatsApp and follow the prompts to sign in with your Meta Business account and link your WhatsApp Business Profile.

Step 3: Register an App in Entra ID

Create a new App Registration in Microsoft Entra ID (formerly Azure AD) to allow secure data exchange between ACS and Dynamics 365. Record the Application (Client) ID and Tenant ID.

Step 4: Configure the Channel in Dynamics 365

Go to the Copilot Service Admin Center (or Omnichannel Admin Center). Under Channels, select Messaging accounts > Add account. Choose WhatsApp, enter your ACS resource name, and provide the App Registration details from Step 3.

Step 5: Set up Webhooks (Event Grid)

Copy the Callback URL provided in the Dynamics 365 channel settings. In the Azure Portal, create an Event Grid Subscription for your ACS resource that sends “Advanced Message Received” events to this URL.

Step 6: Create Workstreams and Rules

Define a Workstream for WhatsApp and set up Routing Rules to determine which queues or agents should receive these specific messages.

Infographic: The Integrated Ecosystem

Layer	Component	Function
User Layer	WhatsApp App	Customer interacts on their preferred social messaging platform.
Gateway Layer	Azure Communication Services	Native Microsoft bridge providing enterprise-grade security and scalability.
Logic Layer	Unified Routing & AI	Determines intent, scores sentiment, and identifies the best agent.
Action Layer	Dynamics 365 Contact Center	Unified agent interface with Copilot assistance and 360-degree customer views.

References

Announcing Dynamics 365 Contact Center WhatsApp channel powered by Azure Communication Services

Uncategorized

What’s New in Copilot Studio: April 2025 – Advancing Multi-Agent Orchestration and Connected Experiences

May 3, 2025May 3, 2026 Goloknath

The April 2025 update focused on the release of the Multi-Agent Orchestration engine and the introduction of Agent-to-Agent (A2A) connectivity, allowing agents to work together as a unified system.

Real-time User Journey: Collaborative Multi-Agent Resolution

The core journey introduced this month involves “handoffs” between specialized agents to solve a complex user request:

Request: A user asks a general “HR Agent” in Teams, “I’m traveling to London for a client meeting next week; can you handle my travel booking and ensure it complies with our latest policy?”
Orchestration: The HR Agent realizes it doesn’t have booking permissions. Using the new Orchestration Engine, it identifies a specialized “Travel Booking Agent” and a “Policy Compliance Agent.”
Collaborative Execution: * The Policy Agent retrieves the travel policy from SharePoint and provides the budget limits to the Travel Agent.
- The Travel Agent searches for flights and hotels that fit those limits.
Verification: The agents pass data back and forth to confirm the hotel choice is within the allowed budget.
Completion: The primary HR Agent returns to the user with a single message: “I’ve found a flight and hotel that comply with our policy. Would you like me to book them?”

Step-by-Step: How to Enable Multi-Agent Connectivity

To allow your agents to communicate with one another using the new protocol:

Step 1: Open Copilot Studio: Navigate to your primary agent.
Step 2: Enable Orchestration: Go to Settings > Generative AI and toggle the orchestration mode to “Generative (Preview)” or “Multi-agent.”
Step 3: Register Sub-Agents: Go to the Actions or Tools tab and select “Add an Agent.” You can now select other agents published within your environment.
Step 4: Define Descriptions: Ensure each sub-agent has a highly detailed Instructional Description. The orchestrator uses these to “know” which agent is the expert in travel, finance, or technical support.
Step 5: Configure Permissions: Set up Delegated Authentication so the sub-agents can act on behalf of the user who started the original chat.
Step 6: Test & Publish: Use the “Test” pane to watch the “Conversation Map” and see how the orchestrator routes the logic between agents.

Infographic: The April 2025 Feature Set

The April update brought several tools to manage complex AI ecosystems:

Feature	What it Does	Impact on Business
Multi-Agent Orchestration	Allows a “Master Agent” to manage “Sub-Agents.”	Reduces the need for users to know which specific bot to talk to.
A2A Protocol Support	Open standard for agent-to-agent communication.	Enables agents to talk across different platforms (e.g., Copilot to custom Azure bots).
Conversation Maps	Visual debugging tool for orchestration.	Helps developers see exactly where a handoff happened or failed.
Knowledge Handoff	Context is passed between agents during a handoff.	The user doesn’t have to repeat their information to the second agent.

References

What’s new in Copilot Studio: April 2025