Deflection overview

Important

Power Virtual Agents capabilities and features are now part of Microsoft Copilot Studio following significant investments in generative AI and enhanced integrations across Microsoft Copilot.

Some articles and screenshots may refer to Power Virtual Agents while we update documentation and training content.

Return on investment (ROI) and improved customer satisfaction (CSAT) are top priorities for the organizations that implement Microsoft Copilot Studio copilots.

Optimizing the copilot deflection rate is one of the top focus areas for organizations to achieve their business goals around ROI and CSAT, and to improve the copilot's overall performance. There are major indicators in Microsoft Copilot Studio that help improve copilot performance, such as resolution rate, escalation rate, and CSAT.

While the metrics continue to evolve, there are several things you can do as a copilot builder to improve the deflection rate of your copilot. In these articles, we cover the importance of deflection in conversational AI and general techniques/considerations that are universal for optimizing deflection for copilots.

Tip

In the context of conversational AI, deflection is an indicator representing the percentage of requests that are completed in a self-service fashion that would otherwise be handled by live agents. In other words, it refers to the number of items a team avoids having to deal with as a result of automation.

Why deflection optimization?

  • Better customer experience: more customers or employees can get their issues resolved by the copilot instead of waiting for a human agent in chat or phone. This leads to a better customer experience and higher CSAT scores. While this helps reduce wait time, live agents can also focus on more complex, higher-value tasks.
  • Cost savings: one of the key ways the ROI of the copilot is determined is by using deflection rates. Human agent call support typically costs around $5 to $10 in the contact center industry. However, a copilot session that resolves a customer request costs around 50 cents. This means that higher deflection rates lead to higher cost savings.

Understanding the key components of Microsoft Copilot Studio analytics to improve deflection

A basic understanding of available analytics is required to be able to determine what deflection means for your organization. The following table describes the key metrics from Microsoft Copilot Studio:

Description Details
Total Sessions The total number of analytics sessions within the specified time period.
A conversation with a copilot can generate one or multiple analytics sessions, each with their own engagement status and outcome. An analytics session begins when a user has new questions after an initial conversation completed (for example, reached the End Of Conversation topic).
Engagement Rate The percentage of total sessions that are engaged sessions.
An engaged session is an analytics session in which a custom topic is triggered, or the session ends in escalation. Engaged sessions can have one of three outcomes—they're either resolved, escalated, or abandoned.
Resolution Rate The percentage of engaged sessions that are resolved.
A resolved session is an engaged session in which the user receives an End Of Conversation question that asks "Did that answer your question?" and the user either doesn't respond or responds "Yes."
Escalation Rate The percentage of engaged sessions that are escalated.
An escalated session is an engaged session that is escalated to a human agent.
Abandon Rate The percentage of engaged sessions that are abandoned.
An abandoned session is an engaged session that isn't resolved or escalated after one hour from the beginning of the session.
CSAT The graphical view of the average of CSAT scores for sessions in which customers respond to an End of Conversation request to take the survey.

These metrics need to be continuously improved to optimize the copilot ROI. However, each organization might have their own definition of what deflection rate means to them. For example, an organization might consider the Abandon rate along with the Escalation rate as part of their deflection calculation, while another organization might look purely at the Escalation rate.

Despite having different definitions for a deflection rate, these metrics still provide the foundation to calculate deflection. Based on our experience with various customers, in the context of deflection, Resolution rate and Escalation rate play a major role. Increasing the Resolution rate and reducing the Escalation rate typically has a direct result on overall copilot deflection metrics.

Key techniques

Diagram illustrating the key techniques of topic and agent analysis.