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.
| Kind | Where | Best for |
|---|---|---|
| Routing rules | Setup → Automation → Routing rules | One condition and one action on every new ticket |
| Workflows | Setup → Automation → Workflows | Several 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.
- Open Setup → Automation → Routing rules.
- 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.
- Choose the Action (Assign agent, Set priority, Set category or Add tag) and the Action value.
- Set the Order (1–999) and keep Active selected.
- 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.
- Enter a Name and choose the Trigger:
| Trigger | Runs when |
|---|---|
| Ticket created | A ticket is created |
| Reply received | A reply arrives on a ticket |
| Status changed | The status of a ticket changes |
| Assignment changed | The assigned agent changes |
| No activity | A ticket had no activity for a set time; checked each time the scheduled task runs |
- Set the Order (lower runs first) and, if the rule should wait, a Delay (seconds).
- 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.
- Under Actions, add up to 20 actions with their Action value or Text:
| Action | What it does |
|---|---|
| Assign to agent | Assigns an agent |
| Assign to team | Assigns the ticket through a team; see Departments, teams and assignment |
| Set status, Set priority, Set category | Sets the status, priority or category |
| Apply SLA policy | Applies an SLA policy, or lets the policy rules choose |
| Add tag | Adds a tag |
| Email the customer | Sends an email to the customer |
| Add internal note | Adds an internal note |
| Notify the assignee | Sends an in-app notification to the assignee |
- Keep Active selected. Select Stop later rules when this one matches if later rules should not run once this rule matched.
- 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
- Create a workflow rule with the trigger Ticket created, a condition on the product and the action Assign to team.
- Run a dry run on a test ticket.
- After a week, read Run history and adjust conditions that skip or fail.