Route, update and follow up on tickets without manual work.
Zoho Desk automation takes care of the routine parts of support: acknowledging new tickets, routing them to the right person, updating fields as tickets move and flagging tickets that have gone quiet. You configure each rule once and Zoho Desk applies it to every matching ticket. This guide explains the automation tools, when to use each one and a starter set that suits most small and mid-sized support teams. It is part of our Zoho Desk guide.
Zoho Desk's automation tools live under Setup > Automation: assignment rules, workflows, supervisor rules, notifications, SLAs with escalations, and Blueprint. Use event-based workflows for actions that should happen the moment a ticket changes, and time-based supervisor rules for anything that depends on how long a ticket has waited.
| Tool | Triggered by | Best used for |
|---|---|---|
| Assignment rules | A new ticket matching criteria | Routing tickets to an agent or team, directly or by round robin |
| Workflows | A ticket being created or updated | Field updates, alerts and tasks the moment something changes |
| Supervisor rules | Time passing | Following up on tickets that have waited too long |
| Notifications | Ticket events | Emails to customers and agents, such as acknowledgements |
| SLAs and escalations | Due times | Response and resolution targets, with escalation before or after a breach |
| Blueprint | Ticket stage changes | Enforcing a fixed process with required steps at each stage |
To create or edit these rules you need the Support Administrator profile, or a profile that includes the Help Desk Automation permission.
Direct assignment sends tickets that meet a condition to a named agent or team. Typical conditions are the channel, the department, a product field, a keyword in the subject line or the customer's account. Round robin assignment spreads tickets evenly across a team so no single agent becomes the bottleneck. Most teams use both: direct rules for specialist topics and round robin for everything else.
Workflows are event-based. They run when a ticket is created, edited or reaches a particular field value. Useful examples include setting the category and moving a ticket to the billing team when it is tagged as a billing issue, alerting the account owner when a key account raises a ticket, and reopening a ticket when a customer replies after it was closed.
Supervisor rules are time-based. Instead of reacting to an event, they look for tickets that have stayed in a condition for too long, and Zoho Desk counts that time using the business hours you choose for the rule. Common uses are alerting a team lead when a ticket has been unassigned for two business hours, nudging the owner of a ticket that has been on hold all week, and closing tickets that have waited on the customer for several days. Zoho's supervisor rules FAQ explains how the timing works.
SLA policies set due times for first response and resolution and can escalate a ticket through several levels. They are the right tool whenever a commitment to a customer is involved. Our Zoho Desk SLA guide covers targets, business hours and escalation design.
For processes with fixed stages, such as refund approvals, returns or onboarding requests, Blueprint defines the stages a ticket must pass through and the fields an agent must complete before moving on. The concept is the same as Blueprint in Zoho CRM, applied to tickets.
Go to Setup > Automation > Workflows and create a new rule for the Tickets module.
Give the rule a name that says what it does, such as Route billing tickets to finance, so anyone can understand it later.
Choose when it runs: when a ticket is created, when it is edited, or when a specific field is updated.
Combine conditions with AND or OR so the rule only touches the tickets you intend.
Add the actions: a field update, an alert, a task or, for advanced cases, a custom function.
Test with a few sample tickets before you rely on it, and check that it does not overlap with an existing rule.
Menu labels occasionally change between Zoho Desk updates, but the structure stays the same. Custom functions use Zoho's Deluge scripting language; our Zoho Deluge guide is a good starting point if you need logic beyond the standard actions.
| # | Rule | Tool |
|---|---|---|
| 1 | Acknowledge every new ticket with its number and expected response time | Notification |
| 2 | Route tickets by department, product or subject keyword | Assignment rule |
| 3 | Alert the account owner when a key account raises a ticket | Workflow |
| 4 | Escalate tickets that are close to missing their first response target | SLA escalation |
| 5 | Remind, then close, tickets waiting on the customer after a set number of business days | Supervisor rule |
| 6 | Ask for a satisfaction rating when a ticket is closed | Notification |
Start with these six, run them for a month, then review which tickets still need manual handling. Those patterns tell you which rule to add next.
Workflows are event-based and run immediately when a ticket is created or updated. Supervisor rules are time-based and act on tickets that have stayed in a condition for a set period, measured in the business hours you choose.
Yes. Assignment rules can send tickets that match set conditions to a specific agent or team, or distribute them evenly across a team using round robin assignment.
Automation features expand as you move up the plans. Zoho states that time-based supervisor rules are available on all paid plans. Check Zoho's pricing page for the current feature split before you choose a plan.
No. Assignment rules, workflows, supervisor rules, notifications and SLAs are configured with menus and conditions. Coding is only needed for custom functions written in Deluge for advanced logic.
A clean rule set saves agents hours every week and stops tickets slipping through. ABR is a Zoho Premium Partner that sets up Zoho Desk as part of wider Zoho One implementations. We map your support process first, then configure departments, rules, SLAs and the help center to match it.