> This page is for version Generative (default).
> For other versions, use one of these documentation indexes:
> - Generative (default): https://developers.ada.cx/generative/llms.txt
> - Scripted: https://developers.ada.cx/scripted/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.ada.cx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.ada.cx/_mcp/server.

# Performance reports

Measure your AI Agent's performance with a variety of detailed reports. This article outlines the individual reports, what they
measure, and how the various filters work. Unless otherwise noted, you
can view these reports by going to **Performance** > **Reports** in your
Ada dashboard.

By default, these reports don't include data from test users. That means
that when you're testing your AI Agent, you don't have to worry about skewing
your report results.

## Learn about each report\[#report-details]

Click a report name below to expand it and learn about the metrics it
includes. Note that the reports that are available in your AI Agent may vary
based on your Ada subscription. If you have any questions, don't
hesitate to contact your Ada team.

For more information on the filters you can use to refine your report
data, see the [Filter the data that appears in a report](#filter-report-data) section of this page.

#### Actions usage

Provides visibility into how often Ada is performing each action, and highlights errors with full log download functionality - allowing your team to troubleshoot effectively. You can access this report through the Reports tab (under Performance) in the left navigation menu or directly through the report icon at the top of the Actions Hub.

<table>
  <thead>
    <tr>
      <th>
        Metric
      </th>

      <th>
        Definition
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Conversations**
      </td>

      <td>
        The number or percentage of conversations where a specific Action was used. Click on this number to see these conversations filtered in the Conversations View.
      </td>
    </tr>

    <tr>
      <td>
        **API calls**
      </td>

      <td>
        The total number of API calls made by an Action.
      </td>
    </tr>

    <tr>
      <td>
        **Error Rate**
      </td>

      <td>
        The percentage of failed API calls made.
      </td>
    </tr>

    <tr>
      <td>
        **AR rate**
      </td>

      <td>
        The percentage of conversations that your AI Agent determined were automatically resolved. Your AI Agent calculates this with the formula `Resolved conversations / (Resolved conversations + Not Resolved conversations)`.
      </td>
    </tr>

    <tr>
      <td>
        **Containment rate**
      </td>

      <td>
        The percent of conversations that did not result in a handoff to human support.
      </td>
    </tr>

    <tr>
      <td>
        **CSAT**
      </td>

      <td>
        The percent of conversations customers reviewed positively, out of all conversations they reviewed.
      </td>
    </tr>
  </tbody>
</table>

![](/_fern-files/_img/9fc7b912b97866176bd9204adc61dff01c702e6d5155e37eb2103091099ee873.webp)

#### Agent satisfaction score

View customer satisfaction (CSAT) surveys where the scores are
attributed to human support, available if the "Automatically survey
after chat" option is turned on.

> **Note**
>
> When you filter this report by date, it uses the date that the user
> submitted their satisfaction survey, rather than the date the
> conversation started. As a result, the number of conversations that
> appear in this report may vary from other reports.

There are four ways you can set up customer satisfaction reviews, each with different scales for recording feedback:

| Rating type                  | Negative review     | Positive review |
| ---------------------------- | ------------------- | --------------- |
| **Numeric (5-point scale)**  | 1, 2, or 3          | 4 or 5          |
| **Numeric (10-point scale)** | 1, 2, 3, 4, 5, or 6 | 7, 8, 9, or 10  |
| **Emoji (5-point scale)**    | 😠, 🙁, or 😐       | 🙂 or 😍        |
| **Thumbs up/down (binary)**  | 👎                  | 👍              |

<table>
  <thead>
    <tr>
      <th>
        Metric
      </th>

      <th>
        Definition
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Live chat score**
      </td>

      <td>
        The percent of agent reviews that were positive. Your AI Agent
        calculates this with the formula `SUM (positive agent reviews) / SUM (all agent reviews) * 100`.
      </td>
    </tr>

    <tr>
      <td>
        **Agent name**
      </td>

      <td>
        The name of the agent who spoke with the customer immediately
        before the customer provided the review. If multiple agents interacted
        with the customer in the same conversation, even if only one agent's name
        appears in this list, all of the agents in that conversation are
        assigned the customer's CSAT score.

        Agent names appear in this list if they have at least one review in
        the time periods selected for either data display or for
        comparison.
      </td>
    </tr>

    <tr>
      <td>
        **Avg score**
      </td>

      <td>
        The percent of agent reviews that were positive.
      </td>
    </tr>

    <tr>
      <td>
        **# of positive**
      </td>

      <td>
        The number of agent reviews that were positive.
      </td>
    </tr>

    <tr>
      <td>
        **# of negative**
      </td>

      <td>
        The number of agent reviews that were negative.
      </td>
    </tr>

    <tr>
      <td>
        **Total # of surveys**
      </td>

      <td>
        The total number of agent reviews.
      </td>
    </tr>
  </tbody>
</table>

#### Automated resolution rate

The [automated resolution rate](/generative/docs/monitoring/conversations/resolution-rate-optimization)
is an analysis of how many conversations your AI Agent was able to resolve
automatically.

To calculate the automated resolution rate, your AI Agent analyzes each completed
conversation to understand both the customer's intent and the AI Agent's
response. Based on that analysis, it then assigns a classification of
either Resolved or Not Resolved to each conversation.

For a conversation to be considered automatically resolved, the
conversation must be:

* **Relevant** - Ada effectively understood the customer's inquiry, and
  provided directly related information or assistance.

* **Accurate** - Ada provided correct, up-to-date information.

* **Safe** - Ada interacted with the customer in a respectful manner and
  avoided engaging in topics that caused danger or harm.

* **Contained** - Ada addressed the customer's inquiry without having to
  hand them off to a human agent.

  While Containment Rate can be a useful metric to get a quick glance of
  the proportion of AI Agent conversations that didn't escalate to a human
  agent, automated resolution rate takes it a step further. By measuring
  the success of those conversations and the content they contain, you
  can get a much better idea of how helpful your AI Agent really is.

> **Info**
>
> Your AI Agent will only assess for automated resolution when a conversation has ended. When viewing the automated resolution rate graph, a dotted line may appear to indicate that recent conversations may not have ended and therefore may cause the automated resolution rate to fluctuate once they're analyzed. For more information on how the conversation lifecycle impacts automated resolution, see [automated resolution rate](/generative/docs/monitoring/conversations/resolution-rate-optimization#conversation-lifecycle).

In this list, you can view a summary of what each customer was looking for, how your AI Agent
classified the conversation, and its reasoning. If you need more
information, you can click a row to view the entire conversation
transcript.

<table>
  <thead>
    <tr>
      <th>
        Metric
      </th>

      <th>
        Definition
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Automated Resolution Rate**
      </td>

      <td>
        The percentage of conversations that your AI Agent
        determined were automatically resolved. Your AI Agent calculates this with
        the formula `Resolved conversations / (Resolved conversations + Not Resolved conversations)`.
      </td>
    </tr>

    <tr>
      <td>
        **Containment Rate**
      </td>

      <td>
        The percent of conversations that did not result in a handoff to a
        human agent.
      </td>
    </tr>
  </tbody>
</table>

#### Average handle time

View the average amount of time customers spent talking with your AI Agent,
for conversations that didn’t end in handoffs to human support.

This report uses
[winsorization](https://en.wikipedia.org/wiki/Winsorizing) on all of its
metrics. To handle outliers, your AI Agent calculates the 90th percentile of
all handle times. If a handle time is higher than the 90th percentile
limit, your AI Agent replaces it with the 90th percentile limit instead.

| Metric                                | Definition                                                                                                                                        |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Avg handle time when contained**    | The average amount of time customers spent talking with your AI Agent, for conversations that didn’t end in handoffs to human support.            |
| **Avg handle time before escalation** | The average amount of time customers spent talking to your AI Agent before handoff, for conversations where customers escalated to human support. |
| **Avg handle time with agents**       | The average amount of time customers spent talking to live support agents.                                                                        |

![](/_fern-files/_img/576a2e8f841fe284029aeb4d9cde88ae63b0c2def79c6c14fd003a40c3de3e73.webp)

#### Containment rate

View how often customers were able to self-serve instead of escalating to
human support.

| Metric               | Definition                                                                      |
| -------------------- | ------------------------------------------------------------------------------- |
| **Containment rate** | The percent of conversations that did not result in a handoff to human support. |

![](/_fern-files/_img/877dd8733e74a92bd4f121298aa3e337cea4d22e194dd6f2da3aed4e053bb787.webp)

#### Conversational messages volume

View the number of AI Agent, customer, and human agent messages per conversation.

Example conversation:

```
AI Agent
- Hello! (1)
- Hello! How can I be of assistance today? (2)

                    Customer
                    [1] Hello -
                    [2] What is the status of my order? -

AI Agent
- I can check on that for you. (3)
- What is your order number? (4)

                    Customer
                    [3] abc123 -

AI Agent
- Let me fetch that information for you... (5)
- Your order is currently being packaged for shipping. (6)
- Your estimated delivery date is Dec 25. (7)

                    Customer
                    [4] that is too long. let me speak to an agent -

AI Agent
- Understood. Connecting you to the next available agent (8)

Human agent
- Hello my name is Sonia. How can I further help you? {1}

                    Customer
                    [5] I need my order sooner. please cancel it -

Human agent
- Sorry about the delay. I will cancel your order {2}
- Your order has been cancelled {3}

                    Customer
                    [6] Thank you -
```

<table>
  <thead>
    <tr>
      <th>
        Metric
      </th>

      <th>
        Definition
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Number of conversations**
      </td>

      <td>
        The number of conversations where a customer sent at least one
        message to your AI Agent.
      </td>
    </tr>

    <tr>
      <td>
        **Messages sent**
      </td>

      <td>
        The number of conversations (y-axis) that contained a given
        number of messages your AI Agent sent (x-axis).

        In the example above, where AI Agent messages are counted in parentheses `()`, this conversation would fall under **8 AI Agent
        messages**. Each response bubble counts as a single message,
        excluding messages that indicate a live agent has joined or left the
        chat.
      </td>
    </tr>

    <tr>
      <td>
        **Customer messages received**
      </td>

      <td>
        The number of conversations (y-axis) that contained a given
        number of messages customers sent (x-axis).

        In the example above, where customer messages are counted in square
        brackets `[]`, this conversation would fall under 6 customer
        messages.
      </td>
    </tr>

    <tr>
      <td>
        **Agent messages**
      </td>

      <td>
        The number of conversations (y-axis) that contained a given
        number of messages agents sent (x-axis).

        In the example above, where agent messages are counted in curly
        brackets `{}`, this conversation would fall under **3
        agent messages**. Emojis, links, and pictures all count as agent
        messages for this report.
      </td>
    </tr>

    <tr>
      <td>
        **Number of messages (x-axis)**
      </td>

      <td>
        The number of each type of message per conversation.

        Roughly 95% of conversations have fewer than 45 messages of any one
        type, which is why the upper end of the scale groups all conversations
        with 45 or more of any one type of message.
      </td>
    </tr>

    <tr>
      <td>
        **Number of conversations (y-axis)**
      </td>

      <td>
        The number of conversations that fall in each quantity of
        messages.
      </td>
    </tr>
  </tbody>
</table>

#### Conversations breakdown

View the number of conversations initiated, engaged, and escalated in
your AI Agent.

<table>
  <thead>
    <tr>
      <th>
        Metric
      </th>

      <th>
        Definition
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Opens**
      </td>

      <td>
        The number of conversations where a customer opened your AI Agent and
        was presented with a greeting. Every conversation contains one greeting.
        The entire series of messages that may be sent counts as one greeting,
        but only one needs to be sent for it to count as an open.
      </td>
    </tr>

    <tr>
      <td>
        **Engaged**
      </td>

      <td>
        The number of conversations where a customer sent at least one
        message to your AI Agent.

        A conversation counts as engaged once a customer sends a message,
        regardless of whether your AI Agent understands the message.
      </td>
    </tr>

    <tr>
      <td>
        **Escalated**
      </td>

      <td>
        The number of conversations where a customer requested an
        escalation to human support.
      </td>
    </tr>

    <tr>
      <td>
        **Automatically Resolved**
      </td>

      <td>
        The number of conversations that your AI Agent automatically resolved.

        > **Note**
        >
        > Before July 31, 2024, this number was approximated based on the automated resolution rate (`AR%`) of a sample of your conversations, and was calculated with the formula `# of engaged conversations x AR%`.
        >
        > The calculated number of automatically resolved conversations was subject to the error margin of the calculated `AR%`.

        For more information, see [Understand and improve your AI Agent's automated resolution rate](/generative/docs/monitoring/conversations/resolution-rate-optimization).
      </td>
    </tr>
  </tbody>
</table>

![](/_fern-files/_img/7ed180ee0e71cbefbbce076ac1f0bf2a1bbf8fae8590ed7553af015e0e14eaf3.webp)

#### Customer satisfaction score

View the percent of your AI Agent's conversations that customers reviewed
positively. For more information, see [Collect and analyze customer satisfaction data with Satisfaction Surveys](/generative/docs/monitoring/performance/csat/csat-configuration).

There are four ways you can set up customer satisfaction reviews, each with different scales for recording feedback:

| Rating type                  | Negative review     | Positive review |
| ---------------------------- | ------------------- | --------------- |
| **Numeric (5-point scale)**  | 1, 2, or 3          | 4 or 5          |
| **Numeric (10-point scale)** | 1, 2, 3, 4, 5, or 6 | 7, 8, 9, or 10  |
| **Emoji (5-point scale)**    | 😠, 🙁, or 😐       | 🙂 or 😍        |
| **Thumbs up/down (binary)**  | 👎                  | 👍              |

| Metric            | Definition                                                                                          |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| **Overall score** | The percent of conversations customers reviewed positively, out of all conversations they reviewed. |

#### Knowledge usage

View to help you understand which articles are most frequently used by Ada in customer responses, and which articles are correlated with high or low Automated Resolution Rates as well as other performance metrics. Includes conversation drill-throughs to support improvement workflows. You can access this report through the Reports tab (under Performance) in the left navigation menu or directly through the report icon at the top of the Knowledge Hub.

<table>
  <thead>
    <tr>
      <th>
        Metric
      </th>

      <th>
        Definition
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Conversations**
      </td>

      <td>
        The number or percentage of conversations where a specific article was used. Click on this number to see these conversations filtered in the Conversations View.
      </td>
    </tr>

    <tr>
      <td>
        **AR rate**
      </td>

      <td>
        The percentage of conversations that your AI Agent determined were automatically resolved. Your AI Agent calculates this with the formula `Resolved conversations / (Resolved conversations + Not Resolved conversations)`.
      </td>
    </tr>

    <tr>
      <td>
        **Containment rate**
      </td>

      <td>
        The percent of conversations that did not result in a handoff to human support.
      </td>
    </tr>

    <tr>
      <td>
        **CSAT**
      </td>

      <td>
        The percent of conversations customers reviewed positively, out of all conversations they reviewed.
      </td>
    </tr>
  </tbody>
</table>

![](/_fern-files/_img/cdc1a59dfd068b52d0598c27501fe2a22c769e5277899764b82745c995ffd6e2.webp)

#### Satisfaction survey results

View the results of your customer satisfaction (CSAT) survey. For more
information, see [Collect and analyze customer satisfaction data with Satisfaction Surveys](/generative/docs/monitoring/performance/csat/csat-configuration).

> **Note**
>
> When you filter this report by date, it uses the date that the user
> submitted their satisfaction survey, rather than the date the
> conversation started. As a result, the number of conversations that
> appear in this report may vary from other reports.

There are four ways you can set up customer satisfaction reviews, each with different scales for recording feedback:

| Rating type                  | Negative review     | Positive review |
| ---------------------------- | ------------------- | --------------- |
| **Numeric (5-point scale)**  | 1, 2, or 3          | 4 or 5          |
| **Numeric (10-point scale)** | 1, 2, 3, 4, 5, or 6 | 7, 8, 9, or 10  |
| **Emoji (5-point scale)**    | 😠, 🙁, or 😐       | 🙂 or 😍        |
| **Thumbs up/down (binary)**  | 👎                  | 👍              |

<table>
  <thead>
    <tr>
      <th>
        Metric
      </th>

      <th>
        Definition
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Last submitted**
      </td>

      <td>
        The most recent time a customer submitted a satisfaction
        survey.
      </td>
    </tr>

    <tr>
      <td>
        **Agent**
      </td>

      <td>
        The agent, if any, who participated in the conversation. If
        multiple agents participated in the conversation, this is the agent who
        participated closest to the end of the chat.
      </td>
    </tr>

    <tr>
      <td>
        **Survey type**
      </td>

      <td>
        The type of survey the customer responded to.

        * **End chat**: The survey presented to the customer
          when they click “End chat” outside of a handoff.
        * **Live agent**: The survey customers receive when
          they close the chat after speaking with an agent, or when an agent
          leaves the conversation.
      </td>
    </tr>

    <tr>
      <td>
        **Rated**
      </td>

      <td>
        The satisfaction rating the customer selected.
      </td>
    </tr>

    <tr>
      <td>
        **Reason for rating**
      </td>

      <td>
        The reason(s) that the customer selected in the survey follow-up
        question, if any.

        Possible positive reasons:

        * Efficient chat
        * Helpful resolution
        * Knowledgeable support
        * Friendly tone
        * Easy to use
        * AI Agent was intelligent
        * Other

        Possible negative reasons:

        * Took too long
        * Unhelpful resolution
        * Lack of expertise
        * Unfriendly tone
        * Technical issues
        * AI Agent didn't understand
        * Other
      </td>
    </tr>

    <tr>
      <td>
        **Resolution**
      </td>

      <td>
        The customer's response, if any, to whether your AI Agent was able to
        resolve their issue. This can either be yes or no.
      </td>
    </tr>

    <tr>
      <td>
        **Comments**
      </td>

      <td>
        Additional comments, if any, that the customer wanted to include
        in the survey about their experience.
      </td>
    </tr>
  </tbody>
</table>

![](/_fern-files/_img/a23ad16203ff6772b690781385301fc9c0399f3377f4ee0a0e718abd9b730cbb.webp)

## Filter the data that appears in a report\[#filter-report-data]

### Filter data by date

To filter a report by date:

1. Click the date filter drop-down.

2. Define your date range by one of the following:

   * Select a predefined range from the list on the left.

   * Type the filter start date in the Starting field. Type the filter
     end date in the Ending field.

   * Click the starting date on the calendar on the left, and the
     ending date on the calendar on the right.

3. Click **Apply**.

The date filter dropdown provides you with the ability to specify the
date range you want to filter the report's data by. You can select from
a list of preset date ranges or select **Custom…** to specify your own
by way of a calendar selector.

### Filter data by additional criteria

The list of available filters differs for each report, depending on the
data the report includes. Clicking the **Add Filter** drop-down menu
gives you access to the filters relevant to the report you're viewing.

* **Include test user**: Include conversations originating from the Ada dashboard test AI Agent. Test conversations are excluded by default.

* **Action**: View conversations relevant only to specific Action(s).

* **Status code**: View reporting analytics relevant to API calls with a specific error code type (e.g. 1xx, 2xx, 3xx).

* **Article source**: View conversations that referenced articles from a specific source.

* **AR classification**: The [**automatic resolution**](https://docs.ada.cx/docs/generative/measure-success/understand-and-improve-your-ai-agent-s-automated-resolution-rate) classification for the conversation.

* **CSAT**: The customer satisfaction rating the customer gave the conversation.

* **Conversation topic**: The [**topic**](https://docs.ada.cx/docs/generative/measure-success/review-and-analyze-conversation-topics) your AI Agent automatically assigned to the conversation.

* **Conversation category**: The [**category**](https://docs.ada.cx/docs/generative/measure-success/review-and-analyze-conversation-topics#topic-category) that the assigned conversation topic has been manually grouped under.

* **Engaged**: Conversations where a customer sent at least one message to your AI Agent.

* **Handoff**: Conversations where your customer was handed off to a human agent.

* **Language** (if Multilingual feature enabled): Include/exclude volume of different languages if your AI Agent has content in other languages.

* **Channel**: Isolate different platforms that your AI Agent is visible in or interacts with (for example, Ada Web Chat, SMS, WhatsApp, etc.).

* **Browser**: Isolate users from specific internet browsers (for example, Chrome, Firefox, Safari, etc.).

* **Device**: Isolate users from specific devices and operating systems (for example, Windows, iPhone, Android, etc.).

* **Filter by variable**: View only the conversations which include one or more variables. For each variable, you can define specific content the variable must contain, or simply whether the variable *Is Set* or *Is Not Set* with any data.

### Additional information

* Report data is updated approximately every hour (but may take up to three hours).

* Reports are in the time zone set in [your profile](/generative/docs/other-features/team-access/profile).

## Printing\[#printing]

We recommend viewing your AI Agent's data in the dashboard for the best
experience. However, if you need to save the report as a PDF or print it
physically, use the following recommendations to limit rendering issues:

1. Click **Print**.

2. In the Print window that appears, beside **Destination**, select
   either **Save as PDF** or a printer.

3. Click **More settings** to display additional print settings.

4. Set **Margins** to **Minimum**.

5. Set **Scale** to **Custom**, then change the value to **70**.

   * Alternatively, you can set the **Paper size** to **A3** (11-3/4 x
     16-1/2 in) or **Legal** (8.5 x 14 in).

6. Under **Options**, select the **Background graphics** checkbox.

7. Right before saving or printing, scroll through your print preview,
   and beside **Pages**, change the number of pages you want to include
   in your PDF or printout. The settings you changed above may affect
   how these pages render.

8. If your destination is Save as PDF, click **Save**. If your
   destination is a printer, click **Print**.

---

Have any questions? Contact your Ada team, or email us at [](<mailto:help@ada.support%20%E2%80%9CHelp Docs inquiry%E2%80%9D>).