# Zoho Desk Automation: Workflows, SLAs and Blueprint by Edition

> How Zoho Desk automation works by edition: workflow rules, macros, round robin, SLAs, supervisor rules, Blueprint, custom functions and Zia actions.

_Source: https://professionalstoolkit.com/articles/zoho-desk-automation — The Professional's Toolkit · updated November 2026_

---

Zoho Desk automates tickets in layers, and your edition decides how many layers you get. Free has no workflow rules at all, only 2 macros and default SLAs. Express adds one workflow rule on the ticket module and two direct assignment rules. Standard is the first edition with working room: 5 workflow rules per module, 5 supervisor rules and 4 SLAs. **Round robin and Blueprint start on Professional**, which costs $35 per agent per month billed monthly or $23 per agent per month billed annually. Custom functions, Zia actions and skill-based routing are Enterprise only. Pick the edition by the layer you need.


**$23** — Per agent per month billed annually for Professional ($35 billed monthly), the first edition with round robin and Blueprint.



- **1 rule** — Workflow rules on Express (ticket module only); none on Free
- **Hourly** — How often supervisor rules run (Standard and higher)
- **1,000 a day** — Zia action executions per organization (Enterprise only)


## Which edition unlocks which rule

| Edition | Workflow rules | Supervisor rules | SLAs | Assignment | Blueprint |
|---|---|---|---|---|---|
| Free | None | None | Default only | Manual | None |
| Express | 1 per module, tickets only | None | Default only | 2 direct rules | None |
| Standard | 5 per module | 5 | 4 | 5 direct rules | None |
| Professional | 15 per department per module | 15 per department | 10 per department | 15 direct rules plus round robin | 1 active per department |
| Enterprise | 30 per department per module | 30 per department | 20 per department | 30 direct rules, round robin, skill-based | 20 per department |

Macros climb the same ladder: 2 on Free and Express, 5 on Standard, 15 per department on Professional and 30 per department on Enterprise.[1] Express also stops at five users, so a sixth agent forces Standard whatever your rules look like. The expensive step is the jump to round robin and Blueprint. Moving from Standard to Professional adds $9 per agent per month on annual billing, or $15 per agent per month on monthly billing. For ten agents billed annually, that is $90 a month or $1,080 a year, by our arithmetic. Every agent sits on the same edition, so the step applies to the whole team; the full bill is in our [pricing guide](/articles/zoho-desk-pricing).

## Workflow rules: the event layer

Workflow rules react to events on a record and run actions straight away. Five triggers exist only on the Tickets module: customer reply, agent response, private thread, happiness rating and delete. The Field Update trigger is Enterprise only. Each rule holds up to 25 criteria and up to 10 alerts, 10 tasks and 10 field updates.[2] Tasks and field updates work only on tickets, so rules on contacts, accounts or other modules are limited to alerts and custom functions. That keeps most real automation inside the ticket module.

The Custom Actions Gallery widens what a rule can do without code. On the Tickets module a rule can carry up to five custom actions: assign the ticket, add a comment, send an email reply, add or remove tags, add followers, mark spam, share the ticket with another department, notify Zoho Cliq, or reply over instant messaging. Two details bite. Tags added by a workflow accept only the letters a to z and digits. And when a placeholder is empty, the assign action is skipped while email replies and comments still go out with blank values. **Test placeholders on real tickets** before you switch a rule on.


> 💡 **Check placeholders before going live:** If a workflow placeholder is empty, the assign action is skipped but email replies and comments still send with blank values. Test each rule on real tickets first.


Macros are the manual layer. An agent applies one with a click, from a single ticket or as a mass action on up to 50 tickets. A macro cannot hold conditions; it bundles up to 10 emails, 10 tasks and 10 field updates, plus one move-department action that always runs last. Macros are department specific, so a team with three departments rebuilds each macro three times. Use them for repeatable agent decisions, and leave anything that should happen without a human to workflow or supervisor rules.

## Getting tickets to the right agent

Without a rule, a new ticket stays unassigned. Direct assignment rules come first: each sends matching tickets to up to five targets and can also move them to another department. Express allows 2 of them, Standard 5, Professional 15 and Enterprise 30. They suit fixed routing, such as one product line to one specialist. Spreading load evenly needs round robin, which starts on Professional and comes in load-based and sequential forms. Skill-based routing, by language or domain expertise, is Enterprise only, with up to 30 active skills per department.

Round robin has defaults worth knowing before go-live. It assigns only to agents who are online on the email channel unless you include offline agents in preferences. Backlog tickets qualify only if the customer replied within the last 30 days. You can set a department-wide open-ticket threshold and agent-level thresholds; the agent value wins. In sequential mode, agents who are offline or at their threshold are marked skipped and sent to the end of the queue, and editing the agent list restarts the sequence. Round robin also leaves alone any ticket whose owner a workflow, direct rule or macro already set.

Zoho's customer story on CreditAccess Grameen, an Indian microfinance lender, says its audit officers receive tickets through a round robin rule. That is the simple case. On Professional and Enterprise, Zia field predictions can also fill picklist fields that then drive assignment. They read English text only. A prediction runs only when the whole email, every thread included, is in English. Multilingual queues still need direct rules. Plan for that.



> ⚠ **Follow-ups skip stale tickets:** Zoho Desk supervisor rules check only tickets with a customer response in the last 30 days, and round robin applies the same 30-day rule to backlog tickets.

## SLAs, business hours and time-based follow-ups

SLAs are department specific and apply to tickets. Free and Express run default SLAs only. Standard allows 4, Professional 10 per department and Enterprise 20 per department, each with up to 10 targets. Targets are set in minutes, hours or days, and each SLA carries up to two response and four resolution escalation levels.[3] An escalation can notify before, on or after the due time, reassign the ticket and change its priority. While a ticket is On hold the timer freezes. Customer-based SLAs need Professional; contract-based SLAs need Enterprise.

Business hours decide what the clock counts. Express through Professional get one business-hours schedule, Enterprise gets 100, and Free gets none. Each schedule links to at most two holiday lists, and holidays can be entered up to two years ahead. SLAs, Blueprint and time-based rules skip those holidays when they compute due dates. Days are tricky, though. A resolution target in days counts business days, Saturdays included. It ignores working hours.


> 💡 **Count SLA days carefully:** A Zoho Desk resolution target set in days counts business days, Saturdays included, and ignores working hours. Use hours when the target is tight.


Supervisor rules are the time-based layer, from Standard up: 5 on Standard, 15 per department on Professional, 30 per department on Enterprise. They run once an hour and check only tickets with a customer response in the last 30 days. Each rule takes at most three actions, one alert, one task and one field update, and time values must be whole numbers. Zoho's customer story on ET Money says its supervisor rules send a reminder after 24 hours without a customer reply, a second at 48 hours, then close the ticket, which the company credits with cutting manual tasks by over 40%.

## Blueprint: a process agents cannot skip

Workflow rules react; Blueprint enforces. A blueprint maps a department's tickets into states joined by transitions. Before a transition it checks who may act and whether criteria match. During it, Blueprint can demand a reply, comment, attachment, resolution or approval request, plus mandatory fields. After it, alerts, field updates and tasks run. Stages can carry their own time limits and escalate on delay. Professional gets 1 active blueprint per department with 20 transitions each; Enterprise gets 20 blueprints with 100 transitions.

Enterprise adds the controls stricter teams want. Strict mode forces agents to act only through transitions. Custom functions can run after a transition. A Blueprint dashboard shows time per state and SLA violations. Two limits hold on every edition: a blueprint cannot be deleted while tickets are active in it, and a ticket inside one cannot change layout. Zoho's customer story on CreditAccess Grameen describes a maker-checker setup: one blueprint stops field officers from closing their own tickets and routes them to managers, and a second blocks reopening without approval.


> ⚠ **Downgrades switch workflows off:** Zoho Desk disables workflow rules when an account is downgraded or the subscription expires, and you must re-enable them manually after renewal.


## Automation Studio, custom functions and Zia actions

Automation Studio is a no-code visual builder on Professional and Enterprise, opened on request through an early-access form. Rules are built from Action, If, Fork and Delay blocks, run asynchronously and chain actions, so an AI summary can feed an email. Classic workflows cannot branch. Custom functions are Enterprise only: Deluge scripts triggered by workflow rules, blueprint transitions or schedules. Limits are 50,000 executions a day, 200,000 statements per function and 2,500 emails a day, with one custom function per workflow rule.

Zia actions bring generative AI into workflow rules, and the conditions are tight. They are Enterprise only, run only in the US, CA, EU, IN and AU data centers, work on the Tickets module and on English text only, and share a cap of 1,000 executions per organization a day. Field extraction pulls up to five values per rule. Automatic email replies answer only the first response on email tickets and need a trained Answer Bot in the same department. Only one generative AI service can be active per organization, and Zia actions do not work with Azure OpenAI. Our [AI playbook](/articles/zoho-desk-ai-playbook) covers the rest of Zia.


## FAQ

**Can I test Zoho Desk automation before it reaches live tickets?**

On Enterprise, yes: Zoho Desk offers up to three sandboxes, each deployable to production. Lower editions have no sandbox, so test rules on a few real tickets first.

**Can workflow rules post alerts to Slack or Microsoft Teams?**

On Professional and Enterprise, workflow rules can notify Slack, Microsoft Teams, Google Chat or Zoho Cliq channels. The chat service must be integrated with Zoho Desk first, or the action does not appear.

**Does automation work on WhatsApp and other messaging channels?**

Instant messaging starts on Standard, but IM workflows, IM round robin and Blueprint in IM need Professional or Enterprise, and chatbots in IM are Enterprise only. Workflow-sent WhatsApp templates should be in English.

**Can automation follow up on a bad happiness rating?**

Yes, on Standard and higher. A workflow rule can email a follow-up when a customer leaves a Bad rating, and a supervisor rule can send the rating link 24 hours after a ticket closes.


## The bottom line

Zoho Desk's automation is deep, but it is sold in layers. Standard covers event rules, hourly follow-ups and a handful of SLAs. Professional is the real threshold, because even ticket distribution and enforced processes both start there. Enterprise is for teams that need code, AI inside rules or skill-based routing. Map your routing, follow-up and approval steps first. Count the rules each one needs. Then buy the lowest edition that holds them all.



## Sources

[1] Zoho Desk pricing plan comparison - Choose your perfect fit Plan Comparison Compare and — https://www.zoho.com/desk/pricing-comparison.html (2026-11)
[2] Zoho Desk help: Creating Workflow Rules — https://help.zoho.com/portal/en/kb/desk/automation/workflows/articles/workflow-automations (2026-11)
[3] Zoho Desk help: SLAs - Scope, Purpose, Understanding, and Setting up — https://help.zoho.com/portal/en/kb/desk/automation/escalate-sla/articles/understanding-and-working-with-slas (2026-11)
[4] Zoho Desk pricing page — https://www.zoho.com/desk/pricing.html
[5] Zoho Desk help center — https://help.zoho.com/portal/en/kb/desk
[6] Zoho Terms of Service — https://www.zoho.com/terms.html