Automation
Triggers
Triggers run right after a ticket is created or updated (including new messages), in position order. Each trigger fires at most once per change; a trigger can react to another trigger’s change, up to five passes, never in a loop. Conditions have all (every one must hold) and any (at least one) lists.
Automations
Automations run every ten minutes on open tickets and need at least one "hours since" condition. Each automation fires once per ticket, so "close solved tickets after 4 days" runs exactly once.
Macros
A macro is a set of actions plus an optional reply and note, applied with one click or in bulk. The reply goes into the composer for review; in bulk it is sent.
Canned responses
Saved reply text with a shortcut. Type / in the composer to insert one.
Placeholders
Replies, notes, notices, macros and canned responses can use placeholders, with an optional default:
Hi {{requester.first_name | default: "there"}}, thanks for writing about {{ticket.subject}}.| Placeholder | Value |
|---|---|
{{ticket.ref}} | #123 |
{{ticket.number}} | 123 |
{{ticket.subject}} | Subject |
{{ticket.status}} | Status |
{{ticket.priority}} | Priority |
{{ticket.url}} | Link for agents |
{{ticket.portal_url}} | Link for the customer |
{{requester.name}} | Customer name |
{{requester.first_name}} | First name |
{{requester.email}} | |
{{agent.name}} | Agent name |
{{agent.first_name}} | Agent first name |
{{brand.name}} | Brand |
{{workspace.name}} | Help desk name |
Condition fields
| Field | Meaning |
|---|---|
status | Status |
priority | Priority |
type | Type |
channel | Channel |
subject | Subject |
tags | Tags |
group_id | Group |
assignee_id | Assignee |
brand_id | Brand |
language | Language |
sentiment | Sentiment (AI) |
intent | Intent (AI) |
category | Category (AI) |
requester_email | Requester email |
requester_domain | Requester email domain |
org_id | Organisation |
message_text | Message text |
message_author | Message from (customer or agent) |
event | Event: created, updated, customer_reply, agent_reply, note, sla_breached, time |
hours_since_created | Hours since created |
hours_since_updated | Hours since updated |
hours_since_requester_update | Hours since customer update |
hours_since_agent_update | Hours since agent update |
hours_since_status_change | Hours since status change |
sla_breached | SLA breached |
within_business_hours | Within business hours |
custom.<key> | Any custom field |
Operators: is, is_not, in, not_in, contains, not_contains, starts_with, gt, gte, lt, lte, present, absent, includes, excludes, changed, changed_to, changed_from.
Actions
| Action | Does |
|---|---|
set_status | Set the status |
set_priority | Set the priority |
set_type | Set the type |
set_group | Set the group |
set_assignee | Assign to a person, the current agent, nobody, or "auto" (the group’s routing) |
add_tags | Add tags |
remove_tags | Remove tags |
set_tags | Replace tags |
set_field | Set a custom field |
add_follower | Add a follower |
reply | Send a public reply |
note | Add an internal note |
notify | Email the assignee, the group or an address |
webhook | Send the ticket to a webhook |
snooze | Snooze for some hours |
send_csat | Send the satisfaction survey |
ai_triage | Run AI triage |
Assignment
Each group picks how new tickets are assigned: manual, round robin, load balanced (fewest open tickets under each person’s cap) or skill based (people with every skill the ticket needs, from skill:<name> tags). Only people whose status is online get tickets.
Approvals
In Settings, Approvals choose roles whose replies need approval, or words (like refund) that make a reply wait for a supervisor.