Monitor conversational agents - Microsoft Copilot Studio

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-improve-agent-effectiveness

Published

2026-06-01

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

Microsoft Learn terms of use; no-redistribution; short excerpts and locators only

Source notes citing this source

• The sources in this packet define abandonment and self-service outcomes in incompatible ways (Amazon Connect abandonment is in-queue disconnection; Copilot Studio abandonment is a 30-minute engaged-session timeout), so no single cross-vendor containment or abandonment rate definition can be assumed. inferred in context
• Copilot Studio counts an engaged session as Abandoned when it times out after 30 minutes without reaching a resolved or escalated state. in context
• Copilot Studio counts a session as Escalated when the Escalate topic triggers or a Transfer to agent node runs, whether or not the conversation actually reaches a live agent, and splits escalations into System intended, System unintended and User requested. in context
• Copilot Studio classifies each engaged session as Resolved, Escalated or Abandoned, and sessions that never become engaged are Unengaged. in context

Cite this source record

APA

WarmTransfer. (2026, June 1). Monitor conversational agents - Microsoft Copilot Studio. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-copilot-studio-analytics-effectiveness

BibTeX

@misc{warmtransfer-ms-learn-copilot-studio-analytics-effectiveness,
  title  = {Monitor conversational agents - Microsoft Copilot Studio},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-copilot-studio-analytics-effectiveness},
  note   = {Microsoft, accessed 2026-09-25}
}