> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/~/revisions/5vNgx1SBLaM9wSz456q7/agent-quality-assurance/agent.md).

# Agent

## Overview

The Agent view provides a comprehensive workspace to monitor and analyze the performance of individual support agents within specific organizational areas, such as Credit Card. It allows supervisors and managers to evaluate agent quality, track ticket volume, and understand the specific issues being handled.

<figure><img src="/files/jsbRCOEycXBRU7WHNF68" alt=""><figcaption></figcaption></figure>

## Viewing & Searching

The interface displays the agent's identifier (email or name) at the top, accompanied by an "Agent" tag to confirm the view level.

A dedicated toolbar allows users to refine the data displayed across the entire page:

### Filtering Data

<figure><img src="/files/WULVVGOxLbWUmEJipvaL" alt=""><figcaption></figcaption></figure>

Use the dropdown menus and fields at the top to filter the view:

* "Filters": Click to segment data by specific criteria relevant to the agent's performance or ticket categories.
* "Date Picker": Select a predefined period (e.g., "Last 30 days") or define a custom range to explore agent activity over time.
* "Search": Use the search bar to quickly look up specific tickets or topics by entering keywords related to the agent's work.

## Panels

### Metrics

Immediately following the toolbar, a series of metric cards provides high-level insights into the agent's performance. These cards display counts and scores for various categories like Overall tickets, Ticket NPS, Backoffice tasks, and Complaints. Each card includes a trend indicator showing a percentage or point comparison against the previous period.

<figure><img src="/files/WRJ7YN4lTmFwGxY9a2pB" alt=""><figcaption></figcaption></figure>

### What's happening?

This panel provides an AI-generated summary of the types of tickets the agent has been addressing, highlighting persistent difficulties or friction points in the customer journey. It includes a "What are people saying?" anchor button that navigates directly to the detailed ticket cards at the bottom of the page.

<figure><img src="/files/WjkgRvFiWgFteqiiE7cu" alt=""><figcaption></figcaption></figure>

### Charts

A flexible visual representation panel that allows users to explore agent data through various metrics. Users can use the "Edit chart" or "+" buttons to modify visualizations, such as line graphs showing performance trends over time (e.g., Ticket NPS Score).

<figure><img src="/files/XyamszXI6q1YWO3DJITp" alt=""><figcaption></figcaption></figure>

### Metrics Table

This section contains a "Reason" tab, which focuses on contact reasons. It features a configurable table that breaks down performance metrics for every specific reason an agent has handled, allowing for granular quality assessment.

<figure><img src="/files/Nt58k4e3exQ3PMxgL1Sa" alt=""><figcaption></figcaption></figure>

### What are people saying?

Located at the bottom of the page, this panel displays individual cards representing each support ticket the agent acted upon. These cards offer a qualitative look at the actual interactions and feedback associated with the agent's work.

<figure><img src="/files/LgP8cLDrjubftUw5KZEc" alt=""><figcaption></figcaption></figure>

## Troubleshooting & FAQs

### Common Issues

* "The metrics don't seem to match the current week."\
  Solution: Check the date filter in the toolbar. Ensure the period is set to the specific timeframe you wish to analyze.
* "I can't see the specific reasons in the table."\
  Solution: Ensure the "Reason" tab is selected within the Metrics panel. If the table is empty, the agent may not have handled tickets within the selected filters.

## See Also

* [Agent Feedback](/~/revisions/5vNgx1SBLaM9wSz456q7/agent-quality-assurance/agent/agent-feedback.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ask.birdie.ai/~/revisions/5vNgx1SBLaM9wSz456q7/agent-quality-assurance/agent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.