---
title: "AWP Support Desk Agent Inbox: Manage Tickets"
description: "Work the agent inbox in AWP Support Desk: filter tickets by status, priority, category or assignee, reply, add internal notes and assign agents."
url: "https://awp-software.com/docs/agent-inbox/"
updated: "2026-11-14"
category: AWP Support Desk
---

# AWP Support Desk Agent Inbox: Manage Tickets

The agent inbox is the wp-admin screen where your team reads, answers and organizes tickets. It is the first thing you see under the **Support Desk** menu, and it is designed so an agent can go from the filtered list to a sent reply in a few clicks. Everything here also exists through the REST API and WP-CLI, but the inbox is where the daily work happens.

## What you need

- An account with the Support agent role or higher. The [roles and capabilities guide](/docs/roles-capabilities/) explains the differences.
- Tickets arriving through the [customer portal](/docs/customer-portal/), WP-CLI or the REST API.

## Find tickets with filters

1. Open **Support Desk** in the admin menu. The inbox is the plugin's landing screen.
2. Filter the list by status, priority, category and assignee.
3. Ticket counts sit next to the filters, so you can size each queue before opening anything.
4. Use the search box to find a specific ticket.
5. Combine filters to build a working queue, for example "open tickets assigned to me".

## Work a ticket

1. Open a ticket from the list. The detail screen shows the public conversation between the customer and your team.
2. Write a reply in the composer when you have an answer for the customer.
3. Switch to an internal note when you need staff-only context: a diagnosis, a next step, a reminder. Customers never see it.
4. Load a canned reply from the staff library when the answer repeats itself.
5. Update the status, priority or category from the controls beside the conversation.
6. Assign the ticket to an agent — yourself or a teammate — so ownership is clear.
7. When the problem is solved, set the status to resolved or closed. The customer receives a closure notice by email.

The whole screen is keyboard accessible and checked against WCAG 2.2 AA in automated tests, so agents can also work with assistive technology or without a mouse.

## Reply or internal note

The two message types exist so your team can think out loud in private:

|  | Reply | Internal note |
| --- | --- | --- |
| Who sees it | The customer, in the portal thread | Staff only, on the ticket detail screen |
| Email | Sent to the customer | Never emailed |
| Use it for | Answers the customer needs | Context for the team: diagnoses, next steps, warnings |

## Canned replies

Canned replies are a staff library of reusable templates. They are created under **Support Desk → Canned replies** and loaded into the ticket composer:

1. Open **Support Desk → Canned replies**.
2. Save the templates your team reuses: a greeting, a first-response checklist, a closing message.
3. In a ticket, load the canned reply into the composer.
4. Review and edit the text before sending. Nothing is sent by loading a template — the composer always gets the final word.

The library belongs to the whole desk: anything saved there is available to every agent, which keeps answers consistent when several people rotate on the same tickets.

## Statuses, priorities and categories

The values agents pick are editable catalogues, not a fixed list. Under **Support Desk → Settings** you can add, rename, reorder and deactivate statuses and priorities, and you can manage the ticket categories the same way. An entry that tickets already use cannot be deleted: deactivate it instead, and existing tickets keep their value while the option disappears from new ones. That keeps the history intact when you reorganize the desk.

## Reports for managers

Managers and administrators get basic reports under **Support Desk → Reports**: tickets created, open load, resolved tickets, and the average time to first response and to resolution, over 7, 30 and 90-day periods. The figures are a snapshot of the selected period, calculated from your own data. They answer "how busy are we and how fast do we answer", not deeper analytics. Use them in a weekly review: comparing the 7-day and 30-day views shows whether the queue is shrinking. If you need advanced reporting, CSAT surveys or SLA policies, that is the territory of the paid Pro add-on.

## Next steps

Emails make the inbox work across the team: the [email notifications guide](/docs/email-notifications/) explains who is told about what and in which language. To tune who can reply, assign or manage, see the [roles and capabilities guide](/docs/roles-capabilities/). The [product page](/products/support-desk/) puts the inbox in the context of the full plugin.
