Agents handle their services’ tickets from the ticket queue: they take them, reply to the requester, talk to each other through internal notes and move the status forward until resolution. This article describes the daily work of an agent and of a service manager.
Before you start #
- You must be a member of a service’s agent group (see Setting up the help desk) and hold the Help center agent right: Access to see tickets, Execute to handle them.
- Without a service, the queue says so: “You are not an agent of any service”.
The ticket queue #
Open Help desk › Ticket queue. The Views sort the tickets:
| View | Content |
|---|---|
| Unassigned | The free tickets of your services. |
| My tickets | Those assigned to you. |
| Overdue or due soon | Those whose deadline is missed or falls within two hours. |
| Waiting | Those waiting for the requester or a third party. |
| Whole service | All the service’s tickets, for its managers. |
Filter by service, status, priority, request type, category, agent, requester (employees or external people) and deadline, or search by number or subject. Open a ticket by its number leads straight to a ticket. The Deadline column flags delays; “Resolution paused” means the clock is stopped.

Take, assign, return #
- Take: the ticket is assigned to you and moves to “In progress”. If a colleague took it at the same moment, the screen tells you.
- Assign to: a service manager, or the agent holding the ticket, hands it to another agent of the service.
- Return to the queue: the ticket becomes free again.
An agent sees free tickets and their own. They can read a colleague’s ticket (by its number) and leave an internal note, but only that colleague or the service manager moves it forward.
The ticket page #
The page brings together the request (description, form answers, attachments of the request), the Conversation, the Timeline, the Requester and their other tickets, the Qualification, the Service commitments and the Milestones, as well as the Links and merge and Following cards (see Merging duplicates, linking tickets, observers and copies). A service catalogue request adds the Tasks cards of each step; a task, the Task of AST-… banner and the Original request and Request conversation cards (see The service catalogue). The Major incident card attaches the ticket to an ongoing incident of its service, or declares one (see Major incidents and problems).

Reply and write an internal note #
- In Conversation, choose Reply to the requester or Internal note.
- Write the text (bold, italic, lists) and attach files if needed.
- For a reply, Insert a canned response places a prepared text in the requester’s language, which you can edit; Insert an article adds a link to a knowledge base article this requester can read.
- Optionally choose Then move to a new status (for example “Waiting for the requester”).
- Click Send the reply or Add the note.

The requester receives the reply by e-mail and in their request, as do the requesters of grouped requests, the people in copy and the observers. An internal note is read by agents only.
Change the status #
In the actions panel, Move to offers the allowed statuses, then Apply. A Note for the requester can come with a resolution or a closure.
| From | To |
|---|---|
| New | In progress, Waiting for the requester, Waiting for a third party, Resolved, Closed |
| In progress | New (returned to the queue), Waiting for the requester, Waiting for a third party, Resolved, Closed |
| Waiting… | In progress, the other waiting status, Resolved, Closed |
| Resolved | In progress (reopening), Closed |
| Closed | None: a closed ticket no longer changes |
Transfer and requalify #
- Transfer sends the ticket to another service, with a Reason (internal). It keeps its number and timeline and arrives without an agent in the chosen service’s queue; its deadlines are recalculated.
- Qualification: change the Request type, the Category or the Priority, then Requalify. A priority change recalculates the deadlines.

File a ticket for someone #
After a call or a visit at the desk, New ticket files on behalf of an employee or an external person (e-mail address, name, organisation, language of their e-mails). The requester follows their ticket as if they had filed it and receives the acknowledgement. Tick I’ll handle it to assign it to yourself.
Good to know #
- A reply from a requester “Waiting for the requester” hands the ticket back to the agent: it moves back to “In progress”, unless it is attached to a major incident, where it keeps its status.
- The agent holding the ticket is notified when the requester replies, confirms the resolution or reopens the ticket.
- For an external person’s ticket, Block the sender discards their e-mails from then on, for all services.
- On a resolved or closed ticket, a knowledge base writer can Create an article from the reply: a draft to review before publishing.
- A ticket waiting for approval can be read, accepts an internal note and can be linked and followed, but allows no other action: see Workflows and ticket approval.
- A ticket attached to a major incident has its deadlines paused and changes neither status nor service, nor can it be merged, while it follows the incident: the incident’s resolution resolves it. A service catalogue request only moves to “Resolved” or “Closed” once all its tasks are finished.
- Your service’s macros appear under the actions panel: one click chains several actions (see Help desk automations: rules and macros).
