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}}.
PlaceholderValue
{{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}}Email
{{agent.name}}Agent name
{{agent.first_name}}Agent first name
{{brand.name}}Brand
{{workspace.name}}Help desk name

Condition fields

FieldMeaning
statusStatus
priorityPriority
typeType
channelChannel
subjectSubject
tagsTags
group_idGroup
assignee_idAssignee
brand_idBrand
languageLanguage
sentimentSentiment (AI)
intentIntent (AI)
categoryCategory (AI)
requester_emailRequester email
requester_domainRequester email domain
org_idOrganisation
message_textMessage text
message_authorMessage from (customer or agent)
eventEvent: created, updated, customer_reply, agent_reply, note, sla_breached, time
hours_since_createdHours since created
hours_since_updatedHours since updated
hours_since_requester_updateHours since customer update
hours_since_agent_updateHours since agent update
hours_since_status_changeHours since status change
sla_breachedSLA breached
within_business_hoursWithin 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

ActionDoes
set_statusSet the status
set_prioritySet the priority
set_typeSet the type
set_groupSet the group
set_assigneeAssign to a person, the current agent, nobody, or "auto" (the group’s routing)
add_tagsAdd tags
remove_tagsRemove tags
set_tagsReplace tags
set_fieldSet a custom field
add_followerAdd a follower
replySend a public reply
noteAdd an internal note
notifyEmail the assignee, the group or an address
webhookSend the ticket to a webhook
snoozeSnooze for some hours
send_csatSend the satisfaction survey
ai_triageRun 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.