ARN Smart Support
Language: English

Automation rules

Updated 9 Nov 2026 4 min read
Browse Ticketix articles

Automation rules make routine ticket changes without an agent: assign a ticket, set its priority or SLA policy, add a tag, email the customer or notify the assignee. Ticketix has two kinds of rules. Both are managed by administrators.

KindWhereBest for
Routing rulesSetup → Automation → Routing rulesOne condition and one action on every new ticket
WorkflowsSetup → Automation → WorkflowsSeveral triggers, condition groups, up to 20 actions, delays and a run history

In the menu, Setup → Automation opens the workflows.

Routing rules for new tickets

Routing rules run on every new ticket, lowest order first: when the condition matches, the action is applied.

  1. Open Setup → Automation → Routing rules.
  2. Under New rule, choose the Condition (Subject, Customer Email, Category, Product or Priority), the Operator (contains, equals, does not contain or does not equal) and the Condition value.
  3. Choose the Action (Assign agent, Set priority, Set category or Add tag) and the Action value.
  4. Set the Order (1–999) and keep Active selected.
  5. Click Create rule. The rule appears in the list with its status, where you can Delete it.

Workflow rules

Open Setup → Automation → Workflows and click New rule.

  1. Enter a Name and choose the Trigger:
TriggerRuns when
Ticket createdA ticket is created
Reply receivedA reply arrives on a ticket
Status changedThe status of a ticket changes
Assignment changedThe assigned agent changes
No activityA ticket had no activity for a set time; checked each time the scheduled task runs
  1. Set the Order (lower runs first) and, if the rule should wait, a Delay (seconds).
  2. Under Conditions, add rows in Group 1 and optionally Group 2 (optional). Each group matches when All must match or Any may match; choose how the two groups combine under Between the groups. A row has a Field, a Comparison (is, is not, contains, does not contain, greater than, less than or is one of (comma list)) and a Condition value. Fields are subject, customer email, category, product, priority, status, department, customer number, assigned agent number, minutes without activity and source. Empty rows are ignored.
  3. Under Actions, add up to 20 actions with their Action value or Text:
ActionWhat it does
Assign to agentAssigns an agent
Assign to teamAssigns the ticket through a team; see Departments, teams and assignment
Set status, Set priority, Set categorySets the status, priority or category
Apply SLA policyApplies an SLA policy, or lets the policy rules choose
Add tagAdds a tag
Email the customerSends an email to the customer
Add internal noteAdds an internal note
Notify the assigneeSends an in-app notification to the assignee
  1. Keep Active selected. Select Stop later rules when this one matches if later rules should not run once this rule matched.
  2. Click Save rule.

The Workflow rules list shows each rule with its trigger and order, with Pause or Enable and Duplicate to start a new rule from an existing one. Rules run in order on the current ticket; delayed actions run through the queue. If one action of a run fails, the run is recorded as failed with the reason and its other actions are rolled back. The routing rules keep working next to the workflows.

Test before you rely on a rule

Under Dry run, choose a Sample ticket and a Trigger and click Run without changes. Ticketix shows which rules would match, with their actions and delay. When two rules set the same field to different values, the list warns about a possible conflict.

Run history

Run history lists each run with the time, rule, ticket, Outcome (applied, skipped or failed) and an Explanation. Search by rule name and filter by outcome. Delayed rules wait in the job queue until their time, and no-activity rules are checked on each run of the scheduled task. See Set up the scheduled task (cron).

A practical start

  1. Create a workflow rule with the trigger Ticket created, a condition on the product and the action Assign to team.
  2. Run a dry run on a test ticket.
  3. After a week, read Run history and adjust conditions that skip or fail.
On this page

Submit a ticket

Create a new support request without needing a portal account.

Priority
Attachments
Only you and our staff see a ticket. Never send passwords or licence codes.

Track a ticket

Use the ticket number and password from your confirmation email.

The number and the password are in your confirmation email.

Sign in

Access your support portal account.

New here?

Create account

Create your support portal account.

Already have an account?

Forgot password?

We email you a link to choose a new password.

Conversation

Was this helpful?
Open full article
↑ ↓ to moveEnter to openEsc to close