Automations do the repetitive work for your agents: rules sort, assign, reply or notify as soon as a ticket arrives or changes, and macros chain several actions in one click from a ticket’s page. This article is for the help desk administrator, who writes the rules and macros, and for agents, who apply the macros.
Before you start #
- To write rules and macros, you need the Administer the help center right (Execute level; Access to read the page). The Workflows rights are not needed.
- To apply a macro, you need the Help center agent right (Execute level).
- Prepare the canned responses (Settings › Help center › Canned responses) and the service categories your actions will use.
Open Settings › Help center › Automations. The Rules are grouped by moment and numbered in the order in which they apply; the Macros follow.

How rules apply #
A rule reads “when… if… then…”: at a given moment, if all its conditions are met, it carries out its actions. Six moments are available:
| When | What triggers the rule |
|---|---|
| When a ticket arrives | The ticket enters the queue: when it is filed, whatever the channel, or when its approval flow decides, if it has one. Once per ticket. |
| When a ticket changes | Its priority, type or category, agent or service changes, or the requester replies. |
| When the status changes | The ticket changes status, including when it is taken. |
| When a deadline approaches | A deadline reminder goes out (see Help desk service commitments). |
| When a deadline is missed | The escalation of a missed deadline goes out. |
| After N hours without activity | An open ticket has had no message and no change for N business hours of its service. |
- All the active rules for the same moment apply, one after the other, in the order of the list. Each one reads the ticket again: the second sees what the first changed.
- A rule marked Stops the next ones prevents, when it applies, the rules after it for that moment.
- The arrows change the order; the switch activates or deactivates the rule.
Creating a rule #
- Click New rule.
- Enter the Name: it appears in the list and in the tickets’ timeline.
- Under When, choose the moment. For After N hours without activity, enter the number of business hours (from 1 to 720).
- Under If, add the conditions with Add a condition. Without a condition, the rule applies to every ticket (“Always”). The Service condition keeps the rule to one or more teams.
- Under Then, add the actions with Add an action, then set each one. They run in the order shown, and a status change always comes last.
- If needed, turn on Stop the following rules when this one applies.
- A new rule is Active by default: turn it off to prepare it without it running. Click Save.

The new rule goes last among those of its moment. The pencil edits it; the bin deletes it, and what it has already done stays done.
Conditions #
- Service, Request type, Priority, Channel, Requester (employee or external person), Organisation, Customer contract and Status: choose one or more values; the ticket only has to match one of them.
- What changed, for “When a ticket changes”: the priority, the type or category, the agent, the service (transfer), a reply from the requester.
- Deadline, for approaching or missed deadlines: first response or resolution.
- The subject contains: words or groups of words separated by commas. One is enough, regardless of capitals and accents.
All the conditions of a rule must be met.
Actions #
| Action | Setting |
|---|---|
| Assign | round robin (each ticket to the service’s next agent), to the least busy (to the agent with the fewest open tickets) or to an agent you choose. Agents absent that day (an approved absence in the Absences module; working from home is not one) are skipped, as is the requester if they are an agent of the service. With round robin and least busy, a ticket that is already assigned stays so. |
| Set the priority | The priority to give. |
| Categorise | A category of the ticket’s service. |
| Reply with a canned response | A shared canned response or one of the service, sent in the requester’s language. |
| Change the status | The new status, always applied last. |
| Notify | the ticket’s agent (without an agent: the service agents), the service managers or the service agents, in the notification bell and by e-mail. The message is optional; it accepts the markers {numero}, {service}, {type}, {priorite}, {statut} and {lien}. |
| Transfer | The service that receives the ticket. |
What rules leave on the ticket #
Each rule that applies is recorded in the ticket’s Timeline, as an internal entry: its name, the moment, then each action, done or left with “no effect” and the reason (for example “no agent available”). When it stops the next rules, the timeline says so too.

A reply sent by a rule goes out in the help desk’s name: in the Conversation, it is signed “Help center” and marked Automatic reply. The requester receives it in their request and by e-mail. It does not stop the first-response clock: only an agent’s reply does.
An action that cannot be carried out (ticket already assigned, no agent available, canned response of another service…) blocks nothing: the other actions run, and the timeline says why this one had no effect. The rule still counts as applied, and stops the next ones if it is set to.
Macros #
A macro is a sequence of actions an agent applies in one click from a ticket’s page, for example “Badge handed over”: reply, categorise, resolve.
Creating a macro #
- In Automations, click New macro.
- Enter the Name: it is the label of the button agents will see.
- Under For the tickets of, add the Service condition to keep the macro to one or more services. Without it, the macro is offered on the tickets of every service.
- Under Then, add the actions, as for a rule. The status change comes last.
- Leave Offered to agents on, then click Save.
Applying a macro #
On a ticket’s page, the Macros bar, under the actions panel, shows one button per macro of its service. Hovering over a button lists its steps; one click applies it.

- The macro acts in the agent’s name: its reply is the agent’s own and counts as the first response, and the timeline names the agent.
- It is all or nothing: if one action is refused (a category of another service, for example), none is carried out and a message gives the reason.
- The bar only appears on an open ticket that is not waiting for approval and that the agent can move forward: unassigned, theirs, or in a service they manage.

Rules and the Workflows editor #
Every rule and every macro is a workflow of the Help desk category: it also appears in Settings › Manage Employees › Workflows, where workflow administrators open it in the full editor (see Workflows and ticket approval). A rule reshaped there (a branch, an approval step…) is marked Reshaped in Workflows: you can still activate, deactivate, move or delete it here, but it can only be edited in the Workflows editor.
Good to know #
- Deactivating a rule or a macro undoes nothing it has done: it simply stops applying.
- A ticket waiting for approval is not touched by any rule. Once approved, it enters the queue and its “When a ticket arrives” rules run at that point; if rejected, it is closed without them.
- A transferred ticket does not go through “When a ticket arrives” again. To act when it enters a service, use “When a ticket changes” with What changed: the service (transfer).
- Inactivity is counted in business hours of the ticket’s service (its hours, time zone and public holidays), like its commitments. A message (a reply or an internal note, from the agent or the requester) or a change to the ticket counts as activity. The rule runs once per period of inactivity, on tickets that are neither resolved nor closed.
- A rule is not restarted by its own effects, and beyond three levels of rules triggered by one another, no more rules run: two rules cannot loop.
- A ticket whose data has been erased (GDPR) is no longer touched by rules.
- A task of a service catalogue request triggers its service’s rules like any ticket; a canned response has no effect there, as the requester follows the request (see The service catalogue). On a ticket attached to a major incident, Change the status and Transfer have no effect, and a macro that contains them is refused (see Major incidents and problems).
- A rule or a macro has ten actions at most. The “Notify” message is saved in the language of your screen; without a message, each recipient receives a default text in their language.
