# Working on assist tickets

An assist ticket is how Ailo asks a teammate for help, for example to check whether a deposit has arrived. Working on a ticket never changes who serves the conversation: while you claim it, message Ailo and resolve it, whoever was serving keeps serving. The rules are in [Serving and assist tickets](serving.md).

## The ticket list

**Assist tickets** on the left rail has two groups:

- **Pool**: tickets nobody has claimed yet.
- **Mine**: tickets you have claimed, split into **In progress**, **On hold**, **Resolved** (including ones that couldn't be resolved) and **All**.

Ticket states:

| State | When |
| --- | --- |
| Open | In the pool, nobody has claimed it |
| Claimed | Someone claimed it but has not started |
| In progress | The assignee did their first piece of work |
| Resolved | The assignee resolved it |
| Couldn't resolve | The assignee closed it with a reason |
| Cancelled | It is no longer needed, for example an earlier ticket couldn't be resolved, so the system cancelled this one |

On hold is not a state of its own. It is a mark the assignee puts on a ticket, for example while waiting for another department.

## Claiming

On the ticket page select **Claim**, or press `C`. You then see "Claimed · {name} keeps serving".

When you **Message Ailo** on a ticket in the pool, sending it claims the ticket for you, and who serves does not change. Confirmation tickets from "Ailo asks you" work differently; see [My queue and all conversations](queue.md#ailo-asks-you).

## Working on it

Your first real piece of work after claiming moves the ticket to In progress: messaging Ailo, adding evidence, running a lookup, or resolving it outright. Just opening it does not count.

When you need to reply to the customer yourself, hold **Transfer to me** on the ticket page to start serving the conversation.

## Resolving, or not

- **Resolve**: the result goes back to Ailo, which tells the customer.
- **Couldn't resolve**: pick the **reason the customer sees** (Could not be completed, More customer information needed, or Service temporarily unavailable), then write the **internal reason** (required, team only).

## Handing it on

- **Transfer to a teammate**: give it to one teammate.
- **Return to pool**: put it back for someone else to claim.

When a member is deactivated, the tickets they hold go back to the pool, and the activity says why.

## What the customer sees

In the widget's **Service progress**, the customer sees which step the ticket is at:

| Step | When |
| --- | --- |
| Submitted | Ailo opened the ticket |
| Accepted | A teammate claimed it |
| In progress | The teammate started working on it |
| Done | The teammate resolved it |

When a ticket couldn't be resolved, the customer sees "This step couldn't be completed here — Ailo will tell you what happens next." Internal reasons, evidence and messages never appear on the customer's side.

## Related

- [Serving and assist tickets](serving.md)
- [Serving a conversation](conversation.md)
