The help desk has its own category in Workflows: ticket events trigger your own flows (notices, actions, approvals), and an approval flow can have some requests approved by the requester’s manager before they are handled. This article explains the triggers, the conditions, the preset provided and the journey of a ticket to approve.
Before you start #
- Workflows are set in Settings › Manage Employees › Workflows, Workflows tab, Help desk category. You need the workflow management rights.
- The category only appears if the Help desk module is active.
Triggers #
| Trigger | When |
|---|---|
| Ticket created | A ticket enters the queue: when it is filed, whatever the channel (employee space, portal, e-mail, agent, website widget, Microsoft Teams, API), follow-ups included, or, if it was waiting for approval, when its flow decides; a task of a service catalogue request, when it is created in its service’s queue. Once per ticket. |
| Ticket status changed | A ticket changes status, including when it is taken, returned to the queue, merged into another one (the absorbed ticket moves to “Closed”) or resolved with a major incident (each attached ticket). |
| Ticket changed | Its priority, type or category, agent or service changes, or the requester replies. |
| Deadline approaching | A first-response or resolution deadline reminder goes out. |
| Service commitment missed | A ticket’s first response or resolution deadline is missed (at the time of the escalation). |
| Ticket without activity | An open ticket has had no message and no change for the chosen number of business hours. |
| Macro (applied by an agent) | An agent applies the macro from the ticket’s page. |
| Ticket to approve | An employee files a ticket and an active approval flow exists (see below). |
Except for “Ticket to approve”, these triggers are those of the help desk rules: all the active workflows of the same trigger apply, one after the other, in the order set in Settings › Help center › Automations, and each one is recorded in the ticket’s timeline. See Help desk automations: rules and macros. For “Ticket to approve”, only one flow applies.
The flow runs in the name of the requesting employee: their manager is the “manager” of the steps. For an external person, it runs in the name of the agent holding the ticket, otherwise of a service manager. A flow never receives the ticket’s subject, description or form answers: only its number, service, type, priority, channel, organisation and customer contract, audience, status, agent and a link to the ticket. The “The ticket subject contains” condition reads the subject on the ticket without passing it to the flow.
Conditions #
- Ticket service among: one or more services.
- Request type among: one or more types, named “Service — Type”.
- Ticket priority among: Low, Normal, High, Critical.
- Employee or external requester: Employee, External person.
- Organisation contract among: one or more service levels of customer organisations (see The help desk and the CRM).
- Ticket channel among, Ticket organisation among, Ticket status among, Ticket change among (for “Ticket changed”), Deadline concerned among (first response or resolution) and The ticket subject contains (words separated by commas).
Seven help desk actions are added to the usual ones: Assign the ticket, Set the ticket priority, Categorise the ticket, Reply with a canned response, Change the ticket status, Notify the ticket team and Transfer the ticket. The lists of services, types, contracts and organisations, like the settings of these actions, are only shown to those who administer the help desk; otherwise the editor says so.
The “Line manager approval before handling” preset #
The category comes with an inactive preset: Line manager approval before handling. Trigger “Ticket to approve”, one approval step by the requester’s line manager (48 hours, reminder after one day), then “Ticket to handle”. As long as it is inactive, tickets go straight to the queue.

- Open the preset by clicking its row (or Duplicate to start from a copy).
- To approve only some requests, add a Request type among (or Ticket service among) condition before the approval step: this is how you set an approval flow per request type.
- Activate the workflow.
The journey of a ticket to approve #
When the flow applies, the ticket stays visible but cannot be handled:
- in the queue, it reads “Waiting for approval” and cannot be taken;
- on its page, a banner explains it: the agent can read it, add an internal note, link it to another ticket and add observers, nothing else (no taking, no reply, no status change, no transfer, no merge, no copy);
- its service commitments do not run: no reminder, no escalation.

The requester sees in their request that it is waiting for approval before being handled, and the timeline says “Approval requested”.

The approver decides from Workflows › Approvals, as for any request: Accept or Reject (a reason is required to reject), or Delegate.

- Approved: the ticket can be handled and its commitment delays run from the decision. The timeline says “Approval granted”.
- Rejected: the ticket is closed, and the requester receives the reason in the closure notice. The timeline says “Approval refused”, with the reason.
Good to know #
- The approval flow only applies to employees’ requests: an external person has no line manager, their ticket goes straight to the queue. A follow-up request (a reply on a closed ticket) is not submitted for approval.
- For a service catalogue item, the flow applies to the request: its tasks are only created after approval, never after a refusal, and a task never goes through a flow (see The service catalogue).
- A ticket outside the flow’s “Applies to” scope follows the fallback flow: the line manager decides.
- If the step designates nobody, the flow is cancelled and the ticket can be handled.
- A ticket erased for GDPR during its approval cancels its flow.
