contact-centre, Customer-service

Bringing end-to-end visibility with screen recording in Dynamics 365 Contact Centre

Bringing end-to-end visibility with screen recording in Dynamics 365

(A unified capability for Dynamics 365 Customer Service and Dynamics 365 Contact Center that captures an agent’s on-screen workflow to provide context beyond just voice and text.)

Real-time User Journey

This journey illustrates how screen recording helps resolve a complex “process” dispute where a transcript alone wasn’t enough:

  1. Complex Interaction: An agent assists a customer with a high-value insurance claim. The interaction involves navigating three different internal legacy systems and a knowledge base.
  2. Triggered Recording: As soon as the agent accepts the call in the Contact Center, the screen recording starts automatically (or is manually toggled by the service rep).
  3. Visual Workflow: The agent hits a snag in the legacy system, leading to a delay. They search for a workaround in the knowledge base, which the recording captures.
  4. Secure Upload: Upon ending the session, the recording is automatically and securely uploaded to Microsoft Dataverse, linked directly to the specific conversation and case record.
  5. Quality Evaluation: A supervisor reviews the “Critical Failure” flagged by the Quality Evaluation Agent. While the transcript sounds professional, the Screen Recording shows the agent bypassed a mandatory compliance checkbox in the internal system.
  6. Targeted Coaching: The supervisor uses the video to show the agent exactly where they deviated from the process, using the recording as a visual training tool to prevent future errors.

Step-by-Step: How to Enable This Feature

Administrators can enable and govern this feature within the admin center settings:

  • Step 1: Admin Center Access

Sign in to the Customer Service admin center or Contact Center admin center.

  • Step 2: Navigate to Recording Settings

Go to Operations > Insights > Call and Screen Recording.

  • Step 3: Enable Screen Recording Controls

Toggle the “Enable screen recording” switch to On. You can choose to enable this for “Voice Conversations” (automatic) and “Other Workloads” (manual toggle for agents).

  • Step 4: Configure Storage & Governance

Ensure your Dataverse storage is configured to handle video files. Set the Retention Policy (e.g., “Delete screen recordings after 90 days”) to align with your regional compliance laws.

  • Step 5: Set Role-Based Access (RBAC)

In the Security Roles section, assign the “Screen Recording Viewer” or “Manager” roles only to authorized supervisors and compliance officers. This ensures that sensitive on-screen data is protected.

  • Step 6: Deploy to Workspace

Go to Agent Experience Profiles and ensure the “Screen Recording” component is visible in the agent’s live conversation widget or productivity pane.

Infographic: Closing the Visibility Gap

AspectTranscript / Audio OnlyWith Screen Recording
VisibilityCaptures “What was said.”Captures “What was done.”
ComplianceHard to verify if policies were clicked.Visual proof of process adherence.
System UsageBlind to technical glitches.Identifies UI/UX bottlenecks in apps.
CoachingBased on verbal cues.Based on actual navigation and speed.
SecurityRedaction limited to text/audio.Role-based secure access to video files.

References

contact-centre, Customer-service

2026 Release Wave 1: Transforming Business Processes with Agentic AI in Dynamics 365

2026 Release Wave 1: Transforming Business Processes with Agentic AI

(A comprehensive roadmap detailing hundreds of new capabilities across Dynamics 365, Power Platform, and Copilot Studio, focusing on autonomous agents and “human-in-the-loop” productivity.)

Real-time User Journey: The Autonomous Supply Chain

While the release covers many areas, the “Autonomous Procurement” journey is a primary highlight of this wave:

  1. Inventory Anomaly: An Autonomous Supply Chain Agent identifies a predicted shortage of a critical component due to a regional weather event.
  2. Market Research: The agent proactively researches alternative suppliers in the Microsoft Dataverse and via the web, comparing lead times and carbon footprints.
  3. Drafting the Plan: The agent drafts a procurement plan, including a pre-filled purchase order for a new supplier that meets all sustainability criteria.
  4. Human-in-the-loop Approval: The Procurement Manager receives a notification in Microsoft Teams. They open the Copilot sidecar, review the agent’s reasoning, and approve the order with one click.
  5. Execution & Tracking: The agent submits the order, updates the ERP, and begins tracking the shipment, providing the manager with real-time risk updates as the weather event progresses.
  6. Resolution: The factory avoids a production halt, and the manager spends their day on strategic supplier relationships rather than manual order tracking.

Step-by-Step: How to Enable Wave 1 Features

Release wave features are rolled out in stages. Here is how to manage and enable them:

  • Step 1: Access the Release Planner

Visit the Microsoft Release Planner to see the specific dates for each feature (General Availability vs. Public Preview).

  • Step 2: Enable Early Access

Sign in to the Power Platform Admin Center. Go to Environments > [Your Environment] > Settings > Updates. Click “Manage” and select “Update now” to enable the 2026 Wave 1 early access features in a sandbox environment.

  • Step 3: Configure New Autonomous Agents

Navigate to the Agent Hub within Dynamics 365 or Copilot Studio. Locate the new pre-built agents (e.g., Sales Research Agent or Case Management Agent) and toggle them to Enabled.

  • Step 4: Update App Profiles

Go to Agent Experience Profiles and ensure the new Copilot Pane and Multi-session companion features are added to your users’ workspaces.

  • Step 5: Define Knowledge Sources

In Copilot Studio, point your agents to the updated Microsoft Fabric or Dataverse connectors to ensure they are using your latest enterprise data for their “Agentic” reasoning.

  • Step 6: Monitor Performance

Use the newly released AI Evaluation Dashboards to measure the accuracy and ROI of the Wave 1 features as they are rolled out to production.

Infographic: 2026 Release Wave 1 Pillars

PillarKey FocusFeatured Capabilities
Agentic AIMoving from “assist” to “act.”Autonomous Sales, Service, and Supply Chain Agents.
Unified DataBreaking silos with Dataverse + Fabric.Real-time insights, zero-copy data sharing, and AI “Memory.”
Copilot StudioEmpowering makers to build agents.Visual agent designer, advanced orchestration, and safety guardrails.
Integrated WorkspaceEmbedding AI where you work.Native AI in Teams, Outlook, and the new Desktop Companion App.
GovernanceTrustworthy and secure AI.AI Evaluation frameworks, sensitive data redaction, and audit logs.

References

contact-centre, Customer-service

Fraud Protection in Contact Centers with Dynamics 365

Contact centres are the beating heart of customer engagement. They handle millions of interactions daily across voice, chat, email, and digital channels. But with this central role comes vulnerability: fraudsters increasingly exploit contact centres as entry points for account takeovers, payment fraud, and identity theft.

Microsoft’s Dynamics 365 Fraud Protection offers a cloud-native solution to mitigate these risks. This paper explores why fraud protection is essential, how Dynamics 365 addresses it, and what licensing and SKUs are required to deploy it effectively.

2. The Growing Need for Fraud Protection

2.1 Fraud Trends in Contact Centres

  • Social Engineering: Fraudsters impersonate legitimate customers to gain access to accounts.
  • Synthetic Identities: Fake accounts created to exploit promotions or loyalty programs.
  • Account Takeover (ATO): Stolen credentials used to hijack customer accounts.
  • Refund Abuse: Exploiting return policies to gain financial advantage.
  • Payment Fraud: Unauthorized transactions processed through agents.

2.2 Impact on Organizations

  • Financial Losses: Billions lost annually to fraud in customer service channels.
  • Reputation Damage: Customers lose trust after a single breach.
  • Operational Strain: Agents spend more time verifying identities manually.
  • Regulatory Risk: Non-compliance with PCI DSS, GDPR, HIPAA, etc.

2.3 Why Contact Centres Are Vulnerable

  • High volume of interactions.
  • Reliance on human agents who can be manipulated.
  • Legacy authentication methods (PINs, security questions).
  • Increasing omnichannel complexity.

3. Dynamics 365 Fraud Protection: An Overview

Microsoft’s Dynamics 365 Fraud Protection is a SaaS solution designed to safeguard organizations against fraud across digital and contact center channels.

3.1 Core Modules

  1. Account Protection (AP)
    • Detects fraudulent account creation and login attempts.
    • Uses AI models to flag suspicious activity.
  2. Purchase Protection (PP)
    • Evaluates online payment transactions for fraud risk.
    • Integrates with payment processors to reduce chargebacks.
  3. Loss Prevention (LP)
    • Identifies fraud in returns, discounts, and loyalty programs.
    • Helps retailers and service providers reduce abuse.

3.2 Integration with Contact Centres

  • Seamlessly integrates with Dynamics 365 Contact Center.
  • Provides real-time fraud scoring during customer interactions.
  • Enhances Nuance voice biometrics for secure authentication.
  • Reduces manual verification workload for agents.

4. Licensing & SKU Requirements

Fraud Protection is not included in Dynamics 365 Premium or Contact Center licenses. It requires separate licensing.

4.1 Base License

  • Dynamics 365 Fraud Protection Base License
    • Includes Account Protection, Purchase Protection, and Loss Prevention.
    • Cost: $1,000/month/tenant
    • Transaction allowances:
      • 100,000 Account Protection transactions/month
      • 2,000 Purchase Protection transactions/month
      • 4,000 Loss Prevention transactions/month

4.2 Add-ons

Add-onCoverageCost (approx.)
Account Protection Add-on20K transactions/month$150/month (<2M transactions) or $100/month (≥2M transactions)
Purchase Protection Add-on2K transactions/month$150/month (<500K transactions)
Loss Prevention Add-on4K transactions/monthIncluded in base; scalable via add-ons

4.3 Licensing Path

  1. Dynamics 365 Premium License
    • Covers CRM/ERP apps (Sales, Customer Service, Finance, etc.).
  2. Dynamics 365 Contact Center License
    • Provides omnichannel engagement, AI-powered service, and Nuance integration.
  3. Dynamics 365 Fraud Protection SKU
    • Adds fraud detection across account, purchase, and loss prevention.
  4. Transaction Add-ons
    • Scale based on interaction volume.

5. Cost Analysis

5.1 Example Scenario

  • A contact center handling 500,000 monthly interactions.
  • Fraud Protection base license ($1,000/month).
  • Additional transaction packs:
    • Account Protection: 20 add-ons ($150 × 20 = $3,000/month).
    • Purchase Protection: 250 add-ons ($150 × 250 = $37,500/month).
  • Total monthly cost: ~$41,500

5.2 ROI Considerations

  • Reduced chargebacks: Savings from fewer fraudulent transactions.
  • Lower operational costs: Agents spend less time on manual verification.
  • Customer retention: Trust preserved through secure interactions.
  • Compliance savings: Avoidance of fines and penalties.

6. Deployment Roadmap

6.1 Phase 1: Assessment

  • Identify fraud risks in current contact center operations.
  • Map customer journey touchpoints vulnerable to fraud.

6.2 Phase 2: Licensing & Procurement

  • Acquire Dynamics 365 Fraud Protection base license.
  • Add transaction packs based on forecasted volume.
  • Ensure Dynamics 365 Contact Center license is active.

6.3 Phase 3: Integration

  • Configure Fraud Protection with CRM workflows.
  • Integrate Nuance biometrics for voice authentication.
  • Train agents on fraud alert handling.

6.4 Phase 4: Optimization

  • Monitor fraud detection accuracy.
  • Adjust fraud scoring thresholds.
  • Scale transaction packs as needed.

7. Case Studies

7.1 Retail Contact Center

  • Reduced refund abuse by 40% using Loss Prevention.
  • Saved $2M annually in fraudulent returns.

7.2 Banking Contact Center

  • Integrated voice biometrics with Account Protection.
  • Prevented thousands of account takeover attempts.

7.3 Healthcare Contact Center

  • Protected patient data from fraudulent access attempts.
  • Achieved compliance with HIPAA security standards.

8. Risks & Considerations

  • Cost scaling: Fraud Protection costs rise with transaction volume.
  • Integration complexity: Requires configuration with existing CRM workflows.
  • Customer experience balance: Overly strict fraud rules may block legitimate customers.
  • Training needs: Agents must understand fraud alerts to act effectively.

9. Conclusion

Fraud protection in contact centres is essential for security, compliance, and customer trust. Microsoft’s Dynamics 365 Fraud Protection provides a modular solution, but it requires separate licensing beyond the Premium license.

The base SKU costs $1,000/month per tenant, with add-ons available for scaling transaction volumes. Organizations must carefully plan licensing to balance cost and coverage.

By integrating Fraud Protection with Dynamics 365 Contact Center and Nuance AI, businesses can reduce fraud, improve efficiency, and protect customer trust.

contact-centre, Customer-service

AI Evaluation: The New Standard for Measuring Contact Center Excellence in Dynamics 365

AI Evaluation: The New Standard for Measuring Contact Center Excellence

(A comprehensive framework focused on measuring the performance of AI agents and human-AI collaboration using advanced metrics like reasoning accuracy and response latency.)

Real-time User Journey: The AI Audit Loop

This journey illustrates how a supervisor uses the AI Evaluation framework to ensure an autonomous agent is performing safely and effectively:

  1. Autonomous Interaction: An AI agent handles a complex request regarding a “Warranty Exception” for a high-value customer.
  2. Telemetry Capture: In real-time, the system captures not just what was said, but the Reasoning Path the AI used to decide to grant the exception.
  3. Performance Evaluation: The Evaluation engine automatically scores the interaction based on the Three Pillars: Understand (Did it get the intent?), Reason (Was the logic sound?), and Respond (Was it fast and empathetic?).
  4. Anomaly Detection: The framework flags the interaction because the Response Latency spiked to 1.2 seconds (above the 800ms threshold) during a specific logic branch.
  5. Supervisor Review: The supervisor opens the Evaluation Dashboard. They see the “Reasoning Trace” and identify that the AI was stuck in a loop checking two conflicting internal policies.
  6. Optimization: The supervisor adjusts the policy priority in Copilot Studio. The Evaluation framework then runs a “Synthetic Test” (a simulated call) to verify the fix before the agent goes live again.

Step-by-Step: How to Enable This Feature

The AI Evaluation tools are found within the Analytics and Insights section of the Dynamics 365 Contact Center.

  • Step 1: Access the Contact Center Admin Center

Sign in and navigate to Insights > Evaluation Framework.

  • Step 2: Define Evaluation Sets

Create a “Dataset” of representative customer interactions (both voice and text) that you want the AI to use as a benchmark for “Good” performance.

  • Step 3: Set “Three Pillar” Thresholds
    • Understand: Define the required Intent Recognition Accuracy (e.g., >90%).
    • Reason: Enable “Reasoning Tracing” to capture the AI’s step-by-step logic.
    • Respond: Set the Target Latency (e.g., <800ms) and Tone Consistency parameters.
  • Step 4: Enable Automated Quality Scoring

Toggle on Auto-Evaluation. This allows the AI to score 100% of interactions using the Quality Evaluation Agent (QEA) framework.

  • Step 5: Configure Synthetic Testing

In the evaluation settings, enable Simulated Conversations. This allows you to “test” your AI agents against a battery of predefined scenarios to measure performance before they interact with real customers.

  • Step 6: Deploy the Evaluation Dashboard

Add the AI Performance Insights report to your Power BI workspace to view real-time scores across your entire digital workforce.

Infographic: The AI Evaluation Framework

ComponentMetric / FocusTarget Benchmark
UnderstandIntent Recognition, Word Error Rate (Voice).90% + Accuracy
ReasonLogical Consistency, Policy Adherence.Zero Hallucination
RespondResponse Latency, Sentiment Alignment.< 800ms Latency
SafetyRedaction Accuracy, Bias Detection.100% Compliance
CollaborationHuman-AI Handoff Efficiency.< 10s Transfer Time

References

contact-centre, Customer-service

Proactive voice engagements in Dynamics 365 Contact Center

Proactive voice engagements in Dynamics 365 Contact Center

(A shift from reactive support to proactive service, where AI agents initiate outbound voice calls to notify customers of critical updates, service disruptions, or personalized offers.)

Real-time User Journey: Anticipatory Service

This journey illustrates how the system prevents a customer from needing to call support by reaching out first:

  1. Event Detection: An airline’s internal system flags that Flight 102 is delayed by four hours due to a technical issue.
  2. Audience Segmentation: The Proactive Engagement Agent identifies all passengers on that flight who have not yet checked in or are currently in transit.
  3. Autonomous Outreach: The AI agent initiates an outbound call to a passenger.
  4. Natural Interaction: The passenger answers. Using HD Voices, the agent says: “Hi Alex, I’m calling from the airline. Your flight to Seattle has been delayed. I’ve already found a seat for you on the 6:00 PM departure. Would you like me to confirm that now?”
  5. Interactive Resolution: The passenger agrees via voice. The agent updates the booking in the CRM and sends a new boarding pass via SMS.
  6. Deflection Success: Because the airline reached out proactively, the passenger does not call the busy airport desk, reducing the “spike” in inbound volume for human agents.

Step-by-Step: How to Enable This Feature

Proactive voice requires configuration in both the Dynamics 365 Contact Center and Azure Communication Services.

  • Step 1: Configure Outbound Settings

In the Contact Center admin center, navigate to Channels > Voice. Ensure you have a validated outbound phone number and the appropriate telephony carrier settings.

  • Step 2: Define Proactive Triggers

Use Power Automate or Dataverse to set up a trigger. For example, “When a Flight Status changes to ‘Delayed’, trigger the Proactive Voice Flow.”

  • Step 3: Create the Voice Agent in Copilot Studio

Design the “Outbound Conversation” topic in Microsoft Copilot Studio. Specifically, select an HD Voice and draft the script using variables (like {CustomerName} and {FlightNumber}) for personalization.

  • Step 4: Enable “Proactive Outreach” in Settings

In the Bot settings, navigate to Proactive Engagements and toggle the feature to On. Map your Copilot bot to the outbound voice channel.

  • Step 5: Set Governance & Quiet Hours

Configure “Quiet Hours” (e.g., no proactive calls between 9:00 PM and 8:00 AM) and “Frequency Caps” to ensure customers aren’t overwhelmed by automated calls.

  • Step 6: Launch and Monitor

Publish the bot. Use the Agent Activity Feed to monitor the success rate and customer responses to these proactive calls in real-time.

Infographic: Reactive vs. Proactive Voice

FeatureReactive Voice SupportProactive Voice Engagement
OriginCustomer initiates (High effort).Company initiates (Zero effort for customer).
Inbound VolumeLeads to massive “spikes” during crises.Smooths the curve by resolving issues early.
ToneOften defensive/apologetic.Anticipatory and helpful.
CostHigh (Human agents handling complaints).Low (AI agents handling resolutions).
Customer ImpactFrustration and wait times.Surprise, delight, and loyalty.

References