For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

How to Test Copilot Studio Agents With TestMu AI

Copilot Studio agents run over digital messaging channels and, once the telephony channel is enabled, over phone through Dynamics 365 Contact Center. Two voice flavours exist: basic IVR agents on classic orchestration, and real-time voice agents. TestMu AI connects to the agent on whichever channel it runs on, drives full multi-turn conversations across personas and edge cases, and scores every run.

Before You Begin​

Before you connect a Copilot Studio agent, make sure you have:

  • A published Copilot Studio agent
  • The telephony channel enabled and connected to Dynamics 365 Contact Center, for phone agents only
  • TestMu AI workspace with agent-testing permissions
  • Source docs for scenario generation: topic export, PRD, or knowledge base

Test a Copilot Studio Phone Agent​

Phone testing covers callers who reach the agent over PSTN or SIP on the telephony channel. Upload the topic export and knowledge sources to generate scenarios, then add the telephony number and pick from 100+ voices, background noise conditions, and personas. It covers what telephony introduces across every topic the agent can trigger: DTMF entry, barge-in, silence detection, transfers, and carrier latency.

Full setup: Phone agent testing

Test a Copilot Studio Chat Agent​

Chat testing covers text conversations on the agent's published web or messaging channel. Upload the topic export and knowledge sources to generate scenarios, then create the endpoint profile against the published channel endpoint. It catches topic triggering, knowledge grounding, and tool failures before they reach the voice channel.

Full setup: Chat agent testing

What You Get With Agent Testing​

Every Copilot Studio run, on any surface it supports, is scored across:

  • 30+ metrics across 8 categories, with configurable thresholds
  • Context-aware scenario generation
  • Adversarial testing and automated issue detection
  • 100+ voices and personas
  • Multilingual conversations
  • Quality scoring and real-time call monitoring

Copilot Studio-Specific Considerations​

A few Copilot Studio behaviours are worth building dedicated scenarios around:

  • The telephony channel must be enabled before connecting Dynamics, and the order matters for reconnection
  • Basic voice agents and real-time voice agents behave differently enough to need separate scenarios
  • Transfers carrying SIP UUI context require direct routing, since PSTN numbers do not support UUI header transfer
  • Topics trigger on either phrases or descriptions, and accuracy settings only affect the phrase path
  • There is no direct audio surface outside telephony, so there is no voice section on this page

Troubleshooting​

Common failure modes to watch for:

  • Topic not triggered
  • Telephony channel not connected
  • UUI transfer rejected
  • Agent published to the wrong environment
Last updated on

Test across 3000+ combinations of browsers, real devices & OS.

Book Demo

Help and Support

Related Articles

On this page