FAQs: Workflow Rules | Zoho Desk

FAQs: Workflow Rules

1. What is a Workflow Rule?
A Workflow Rule is an automation mechanism that executes a predefined set of actions — alerts, tasks, field updates, and custom functions — when specific conditions are met on a record. Instead of requiring agents to manually send notifications, assign tasks, or update fields, workflow rules handle these actions automatically and instantly upon trigger.

For example, when a high-priority ticket is created in the "Billing" department, a workflow rule can simultaneously send an email alert to the billing team lead, assign a follow-up task to the ticket owner, and update a custom field called "Escalation Flag" to "Yes" — all without any manual intervention.
2. When to use workflow rule?

Here are some common examples of workflow rules:

  1. Ticket assignment: Workflow rules can automatically assign incoming tickets to specific agents or teams based on various criteria, such as ticket type, customer priority, or expertise. This helps ensure that tickets are promptly routed to the most appropriate resource for timely resolution.
  2. Priority and escalation: Based on predefined rules, workflows can automatically assign different levels of priority to tickets, escalate them based on response or resolution time thresholds, or trigger alerts to supervisors or higher-level support tiers. This helps prioritize critical issues and ensures timely resolution.
  3. SLA Management: Service level agreements (SLAs) define response and resolution time commitments. Workflow rules can enforce SLAs by tracking ticket status, sending reminders for approaching or breached SLAs, and generating reports to monitor performance against SLA targets.
  4. Email Notifications: Workflow s can trigger email notifications to customers, support agents, or supervisors at various stages of the ticket lifecycle. For example, notifications can be sent when a ticket is created, assigned, updated, or resolved, keeping stakeholders informed about the progress of their requests.
  5. Knowledge Base Suggestions: When a support agent is working on a ticket, workflow rules can analyze the content of the ticket and suggest relevant knowledge base articles or solutions that may assist in resolving the issue. This helps agents provide accurate and efficient support by leveraging existing knowledge resources.
  6. Ticket Categorization and Routing: Workflow rules can automatically categorize and tag incoming tickets based on keywords, customer details, or other criteria. This categorization enables effective ticket routing, grouping similar issues together, and improving reporting and analytics.
  7. Automated Responses: Workflow rules can trigger automated responses to customers to acknowledge their support requests, provide status updates, or share relevant information. These responses can be customized based on ticket type, priority, or other attributes.
  8. Ticket Closure and Follow-up: Workflow rules can initiate actions upon ticket closure, such as sending satisfaction surveys to gather feedback from customers or generating reports for performance analysis and improvement.
3. What kind of automation can be done using workflow?
Various manual actions can be automated using workflows.
Automations available for the ticket module
Workflow Action
Example
Alerts
Send an alert to a manager when a high-priority ticket is created.
Field Updates
Change status to “In Progress” when assigned to an agent.
Assign Ticket
Assign billing-related tickets directly to the Billing team.
Add Comment
Add a note saying “Escalated to Level 2” when SLA is breached.
Add Tags
Tag tickets with the word “refund” with “Payment-Issue”.
Send Email Reply
Automatically thank the customer after receiving a ticket.
Reply via Instant Messaging
Inform a customer via WhatsApp when their issue is resolved.
Notify via Instant Messaging
Notify the assigned agent about a VIP ticket via Slack.
Remove Tags
Remove outdated tags when ticket status is closed.
Add Followers
Add the supervisor as a follower for all tickets with escalated status.
Mark Ticket as Spam
Automatically mark tickets containing "free gift" as spam.
Share Ticket
Share product-related tickets with the Engineering department.
Add Skills
Add “Technical” skill tag for all software-related tickets.
Remove Skills
Remove “Urgent” skill once the ticket is resolved.
Recalculate Skills
When the ticket category changes, skills are recalculated.
Reassign Ticket Based on 
Auto-assign hardware tickets to agents with “Hardware Repair” skill.
Change Layout
Switch to a custom layout when the ticket is related to legal issues.
Tasks
Create a follow-up task to call the customer in two days.
Custom Functions
Update Zoho CRM when a ticket is marked “Resolved.”
External Actions - Send Cliq
Send a Cliq message to the support channel for all new enterprise customer

Automations for the other modules
Module
Automations
Example
Calls
  1. Alerts
  2. Custom Functions
  1. Alert: Notify agent when a call is missed
  2. Custom Function: Auto-create follow-up task for missed calls
Products
  1. Alerts
  2. Custom Functions
  1. Alert: Notify support team when a product is marked defective
  2. Custom Function: Sync product update with inventory system
Accounts
  1. Alerts
  2. Custom Functions
  1. Alert: Send an internal alert when a VIP account raises a ticket
  2. Custom Function: Auto-tag accounts as "High Value" based on criteria
Contacts
  1. Alerts
  2. Custom Functions
  1. Alert: Send welcome email when a new contact is added
  2. Custom Function: Sync contact data with CRM
Events
  1. Alerts
  2. Custom Functions
  1. Alert: Remind agent one hour before scheduled event
  2. Custom Function: Update event status post completion
Tasks
  1. Alerts
  2. Custom Functions
  1. Alert: Send an email reminder to the assigned agent 30 minutes before the scheduled call.
  2. Custom Function: Update the call status to “Completed” after the call ends.
Time Entry
Custom Functions
Custom Function: Log work hours in external billing software like Zoho Books
Custom Modules
  1. Alerts
  2. Field Updates
  3. Custom Functions
  1. Alert: Notify the manager when a record is added
  2. Field Update: Auto-update status when condition is met
  3. Custom Function: Trigger external API when custom condition


4. What are the components of a workflow rule?
A workflow rule consists of four elements:
  1. Basic Information — The module type the rule applies to, rule name, description, and an option to activate/deactivate the rule.
  2. Execute On — The trigger event that causes the rule to fire (e.g., record creation, edit, field update, customer reply, etc.).
  3. Rule Criteria — The conditions a record must meet for the rule to execute. Only records matching these criteria will trigger the actions.
  4. Actions — The alerts, tasks, field updates, and custom functions that run immediately when the rule is triggered.
5. What types of actions can a workflow rule perform?
A workflow rule can execute four types of actions:
  1. Workflow Alerts — Automated email notifications sent to specified recipients (groups, roles, agents, record owners, record creators, contacts, or additional email addresses).
  2. Workflow Tasks — Tasks automatically assigned to users with details like subject, status, priority, assignee, and due date.
  3. Workflow Field Updates — Automatic updates to specified field values on the record when the rule fires.
  4. Custom Functions — Custom scripts (Deluge) that can perform advanced logic, call external APIs, or manipulate data beyond what standard actions allow.
6. How many actions can be configured within a single workflow rule?
Each workflow rule can include up to:
  1. 10 alerts
  2. 10 tasks
  3. 10 field updates
There is no stated limit on custom functions, but practical performance considerations should guide how many actions you stack into a single rule.
7. How to create a Workflow Rule?
The creation process is divided into four parts:
Part 1: Basic Information
  1. Go to Setup > Automation > Workflows.
  2. On the Workflows List page, click Create Rule in the upper-right area.
  3. On the New Workflow page:
    1. Select the Module the rule applies to.
    2. Enter the Rule Name.
    3. Select the Active checkbox if you want the rule to be active immediately.
    4. Enter a Description.
  4. Click Next.
Part 2: Execute On 5. Select the trigger event (see the next FAQ for available options). 6. Configure any trigger-specific options (e.g., field names for Field Update, rating type for Happiness Ratings). 7. Click Next.
Part 3: Rule Criteria 8. Specify the criteria to filter records. Use AND/OR operators to combine multiple conditions. 9. Click Next.
Part 4: Actions 10. Add alerts, tasks, field updates, and/or custom functions. 11. Save the workflow rule.
8. Can workflow rules be created for the Tickets module across all departments?
Workflow rules are created per module per department. When you create a rule, you select the module it applies to, and the rule operates within the context of the department you're configuring it in. If you need the same rule in multiple departments, you must create separate rules in each department. The rule limits (5/15/30 per module per department) apply independently to each department.

9. Are workflow tasks and field updates available for all modules?
No, Workflow tasks and workflow field updates are available only for the Tickets module. For all other modules (Contacts, Accounts, Tasks, etc.), you can only associate workflow alerts and workflow custom functions. This is a critical distinction when designing automation for non-ticket modules.

10. Can records in custom modules be updated using workflow rules?
Yes. Workflow rules can update fields in custom modules (e.g., Patients, Employees, Claims) and their related modules. The update record action supports both static values (fixed text or numbers) and dynamic values (values derived from other fields or records).
For example, if an employee's name is updated in the Employee module, a workflow rule can automatically propagate that name change to the related Payroll module. Similarly, if a customer updates their date of birth on an insurance form, the workflow can recalculate and update the customer's age in the policy and claims modules.
11. What trigger events are available for the "Execute On" step?
A workflow rule can execute four types of actions:
  1. Workflow Alerts — Automated email notifications sent to specified recipients (groups, roles, agents, record owners, record creators, contacts, or additional email addresses).
  2. Workflow Tasks — Tasks automatically assigned to users with details like subject, status, priority, assignee, and due date.
  3. Workflow Field Updates — Automatic updates to specified field values on the record when the rule fires.
  4. Custom Functions — Custom scripts (Deluge) that can perform advanced logic, call external APIs, or manipulate data beyond what standard actions allow.
12. How does the "Field Update" trigger differ from the "Edit" trigger?
The Edit trigger fires whenever any change is made to a record — any field, any modification. The Field Update trigger is more granular: it fires only when specific fields you designate are modified. You can choose multiple fields and specify whether the rule should fire when all or any of the selected fields are updated.

For example, if you only want a notification when a ticket's "Priority" or "Status" field changes (but not when other fields like "Subject" or "Description" are edited), you would use the Field Update trigger and select those two specific fields. Note that this trigger is available only in the Enterprise edition.
13. Can the Private Thread trigger be configured for only incoming or only outgoing emails?
Yes. When you select the Private Thread trigger, you can choose to execute the rule for:
  1. Incoming private email threads only
  2. Outgoing private email threads only
  3. Both incoming and outgoing
This allows you to, for instance, send an internal notification only when a private thread is received from an external source, without triggering on outgoing internal communications.
14. How does the Happiness Ratings trigger work?
When you select Happiness Ratings, you can specify which rating(s) should trigger the rule. You can choose:
  1. All Ratings — The rule fires regardless of the rating value.
  2. A specific rating — The rule fires only when that particular rating (e.g., "Bad" or "Good") is received.
For example, you could create a workflow rule that triggers only on a "Bad" rating, automatically assigning a follow-up task to a senior agent and sending an alert to the department manager to review the ticket.
15. Are rule criteria mandatory?
No, Rule criteria are not mandatory. If you skip the criteria, the workflow rule will trigger for all records that match the selected "Execute On" event. This is useful when you want an action to fire universally — for example, sending an acknowledgment email to every customer who submits a ticket, regardless of any field values.

16. How many criteria can I specify in a single workflow rule?
You can specify a maximum of 25 criteria per workflow rule. You can combine these using AND/OR operators to build complex filtering logic.

For example, a rule could be configured as: (Department = "Billing" AND Priority = "High") OR (Department = "Technical" AND Category = "Bug"). This would trigger the rule for high-priority billing tickets or technical bug tickets.
17. Can AND and OR operators be used together in rule criteria?
Yes. You can combine AND and OR operators to create compound criteria. This allows for sophisticated filtering — for instance, triggering a rule only when the ticket category is "Refund" AND (the customer's region is "EU" OR the ticket amount is greater than $500).

18. Can a workflow rule trigger itself recursively?
Workflow rules triggered on Edit or Field Update could potentially create a loop if a field update action modifies a field that re-triggers the same rule. For example, if Rule A updates "Status" to "In Progress" and the rule's trigger is "Field Update on Status," the field update could re-trigger the rule. Exercise caution when designing rules with field update actions on the same fields that trigger the rule. Test thoroughly in a sandbox environment before activating such rules in production.

19. How do workflow rules interact with other automation features like Blueprints and Assignment Rules?
Zoho Desk processes automation in a specific hierarchy: Assignment Rules → Workflow Rules → SLAs → Round Robin → Blueprint. This means:
  1. Assignment rules may reassign the ticket owner before a workflow rule's "Record Owner" alert is evaluated.
  2. Workflow rules execute before SLAs are applied, so a field update in a workflow rule could affect SLA calculations.
  3. Blueprint transitions are evaluated last, so workflow rule actions (like field updates) will have already been applied by the time the blueprint evaluates the ticket.
20. How to create a Workflow Task?
  1. In the New Workflow page, under Actions, click the Add icon next to Tasks and select New.
  2. In the New Task window, specify: Subject, Status, Priority, Assignee, Due Date, and other task-related details.
  3. Click Save.
There is an option called "Assign ticket owner as task owner" — when enabled, the task will be assigned to the ticket owner. However, this assignment only takes effect if the corresponding ticket is unassigned at the time the rule fires. If the ticket already has an owner, the task will be assigned to the explicitly specified assignee instead.
21. How to create a Workflow Field Update?
  1. In the New Workflow page, under Actions, click the Add icon next to Field Updates and select New.
  2. In the Create Assignment Value window:
    1. Enter a Name for the assignment value.
    2. Optionally enter a Description.
    3. Select the field to be updated from the drop-down list.
    4. Specify the new value for the field.
  3. Click Save.
When the workflow rule triggers, the specified field will be automatically updated with the designated value. For example, you could automatically set a custom field "SLA Breach" to "Yes" when a ticket's status changes to "Escalated."
22. Can I auto update the ticket status?
Yes, you can update the ticket status automatically by using a Field Update action in a workflow rule, so that the ticket status is updated without any manual intervention. Let’s say your refund team wants tickets to be automatically marked as "Refund In Progress" once they are assigned to an agent within the refund team. By default, the ticket might remain in the "Open" status even after assignment, leading to confusion where customers may think no action has been taken, and agents may forget to update it manually.

To set up a workflow rule that auto updates the ticket status
  1. Navigate to Setup > Automation > Workflow Rules
  2. Click Create rule under the Tickets module
  3. Enter the Rule Name and Description
  4. Check the Active box to enable the rule
  5. Click Edit under the Execute On
  6. Set the Criteria as Team is refund
  7. Under Actions, click ➕ and select Field Update
  8. Choose the Status field and set the new value to "Refund on Progress"
  9. Click Save
  10. Click Save again to complete and save the workflow rule


23. Once deactivated, what will happen to the existing and new tickets?
Once a workflow rule is deactivated, it will no longer run or apply to any tickets (existing or new). However, any actions already performed by the rule on existing tickets will remain unchanged.

For example, if a workflow rule triggered an automatic email when the ticket subject contained the word “return,” and a ticket was created with the subject “Return request for order #1234” while the rule was still active, the email would be sent. Deactivating the rule later will not undo this action or affect that ticket in any way.

Additionally, after deactivation, the rule will not be triggered for new tickets or for any updates made to existing tickets—even if they meet the same criteria.
24. Is it possible to notify the team when a record is deleted?
Yes, it is possible to trigger a workflow by sending a notification when a record is deleted. 
To set up a workflow rule that notifies the team when a record is deleted:
  1. Navigate to Setup > Automation > Workflow Rules
  2. Click Create Rule and select the appropriate module (e.g., Tickets)
  3. Enter a Rule Name "Ticket deletion alert" and the Description
  4. Check the Active box
  5. In the Execute On field, select Delete, which makes the rule run when a record is deleted
  6. Click Next
  7. Set conditions, Team is "Support"

  8. Under Actions, click ➕ and choose Alert > New
    1. Name: Deleted Ticket Alert
    2. Click on Create an email template
    3. Subject: A ticket was deleted
    4. Body: A ticket has been deleted
    5. Select a specific agent under the Send Email Alert To option
    6. Click Save to finalize the alert
  9. Click Save to save the entire workflow rule


25. Can I send a automatic notification to the manager when the happiness rating is bad?
When a customer submits a bad rating through the Customer Happiness Rating survey, a workflow can be triggered to send an alert to the manager or lead.

To set up a workflow rule to send automatic notification 
  1. Navigate to Setup > Automation > Workflow Rules
  2. Click Create Rule and choose the Tickets module
  3. Enter Rule Name "Notify Manager on Bad Rating" and a description
  4. Check the Active box
  5. Execute On Edit as the rating is updated after ticket creation
  6. Click Next
  7. Set Criteria Customer Happiness Rating is Bad

  8. Under Actions, click ➕ and select Alert > New
    1. Create the Alert Name as "Notify Manager - Bad Rating"
    2. Click Create an email template
    3. Enter Subject: Customer submitted a bad rating, and the Body of the email: A ticket has received a bad customer rating
    4. Click Send To to choose the manager's email directly or select a role like Team Lead or Manager
    5. Click Save to save the alert
  9. Click Save to save the workflow rule



26. Can I move the ticket to another layout using workflow?
Yes, the user can move tickets to a different layout using a workflow by providing the correct criteria and adding the layout change as an action. In this example, we will change the layout of tickets with a subject containing 'Bug' to a different layout called 'Bug Tracking Layout'.

To create the Workflow Rule to change Layout
  1. Navigate to Setup > Automation > Workflow Rules
  2. Click on Create Rule and choose the Tickets module
  3. Enter Rule Name and Description:
    1. Rule Name: Move to Bug Tracking Layout
    2. Description: Changes the layout if the ticket subject contains the word "Bug"
  4. Check the Active box
  5. Choose Create under Set Execute On
  6. Click Next to define the condition
  7. Under Criteria, select Subject contains Bug
  8. Click Next.
  9. Under Actions, click the ➕ icon and choose Change Layout
  10. In the Change Layout popup: Select the target layout: Bug Tracking Layout
  11. Click Save
  12. Click Save again to complete the workflow rule


27. Can I create a workflow rule to automatically assign tickets to specific agents based on certain criteria?
Yes, you can create a workflow rule to automatically assign tickets to specific agents based on a predefined criteria. When setting up the rule, define the condition based on ticket attributes like category, type, priority, or custom fields, then select the desired agent or team to whom the tickets should be assigned.
Example: Automatic Ticket Assignment for high priority tickets

A company that offers IT services receives various support tickets from its clients through Zoho Desk. The company has a priority system for tickets, where urgent tickets require immediate attention and resolution. They want to automatically assign urgent tickets to a dedicated team of senior support agents who can quickly address critical issues.

The support admin create a workflow rule in Zoho Desk that automatically assigns tickets with high priority (urgent) to a specific team of senior support agents, ensuring prompt handling and resolution of critical customer issues.

The support admin sets up a workflow rule in Zoho Desk to automate the ticket assignment process for urgent tickets.

To create the Workflow Rule:
  1. Navigate to Setup > Automations > Workflows > New Rule.
  2. Name the rule "Automatic Assignment for Urgent Tickets."
  3. Add a brief description to explain the purpose of the rule.
To define the trigger conditions:
  1. Set the rule to trigger when a ticket is created or updated.
  2. Specify the trigger condition to check the ticket priority. For example, "Ticket Priority is high." 
Assign urgent tickets to the Senior support team:
  1. Add the action to assign the ticket to the specific team of senior support agents. For example, "Assign Ticket to Team: Senior Support Team."
 Notify the Senior support team:
  1. You can optionally add an action to notify the senior support team about the new ticket assignment. This can be done via an email notification or an in-app alert.
Save the Workflow Rule:
  1. Once the trigger condition and actions have been defined, save the workflow rule.
Whenever a new ticket is created or updated in Zoho Desk, the workflow rule automatically checks the ticket's priority. If the ticket priority is high the rule immediately assigns it to the dedicated team of senior support agents called the "Senior Support Team."
28. Can I set up a workflow rule to send an automated response to customers when they submit a new ticket?
Yes, users with administrative privileges can set up an automated response. A workflow rule can be created with the trigger condition based on ticket creation. An action can be added to send an email response (acknowledgement) to the customer every time a ticket is created.

You can also customize the email content using email templates and include dynamic placeholders to personalize the response.

To set up an automated response to customers:
  1. Log in to your Zoho Desk account with administrator privileges.
  2. Go to Setup () in the top-right corner and select Workflows under Automation.
  3. On the Workflow Rules page, choose a department from the drop-down for which you want to create a workflow rule.
  4. Click the Create Rule button.
  5. Choose the Tickets module from the list and give your rule a name and description for reference.
  6. Set the trigger conditions for the rule as Create. This will execute the rule whenever a ticket is created.
  7. Select your Criteria, If any, from the drop-down to trigger the rule when those specific criteria matches.
  8. Select Actions under Tasks and click Send Email Replies.
  9. Choose your email templates or create a new email templates to be send.
  10. Click Save.

See also>> Managing email templates


29. Can I perform field update on custom fields using a workflow rule?
Yes, you can update custom fields using a workflow rule in Zoho Desk. When setting up the rule, select the action to update the ticket field, and then choose the custom field you want to modify and the new value.

30. Can I close tickets automatically when certain criteria are met?
Yes, you can create a workflow rule to automatically close a ticket when specific criteria are met. Set up the rule's trigger conditions to check for the relevant attributes, such as ticket status or custom fields, and add the action to close the ticket.

31. How can I send a survey automatically to the customers after their ticket has been resolved?
To send a survey after ticket resolution, create a workflow rule with trigger conditions that check for ticket status being resolved. Add the action to send the survey email with a survey link to the customer. You can also use Zoho Survey or integrate other survey tools in Zoho Desk for this.

32. How do I test and validate my workflow rule to ensure it works as intended?
To test a workflow rule, create a test ticket that meet the rule's trigger conditions and verify if the actions are executed as expected. Make adjustments as needed and test again until the rule performs as desired.

InfoWe hope that this list of frequently asked questions about Workflow Rules is informative. If you still have questions that haven't been addressed, please let us know. We will be happy to discuss them with our subject matter experts and add them in the future. And please don't forget to share your rating below!
33. Can existing workflow actions be reused across multiple rules?
Yes. When adding actions to a workflow rule, you can choose to associate existing workflow actions (alerts, tasks, field updates) or create new ones. This means if you've already created an alert called "High Priority Notification" for one rule, you can reuse it in another rule without recreating it from scratch.

34. What happens if multiple workflow rules trigger on the same event?
If multiple workflow rules are configured for the same module, department, and trigger event, and a record matches the criteria of more than one rule, all matching rules will execute. Zoho Desk does not stop at the first matching rule — each rule is evaluated independently. This means a single ticket creation could trigger alerts from Rule A, tasks from Rule B, and field updates from Rule C simultaneously.

35. Does a workflow rule execute immediately or is there a delay?
Workflow actions execute immediately when the rule is triggered and the record matches the criteria. There is no configurable delay or scheduling mechanism within standard workflow rules. If you need delayed actions (e.g., "send an email 2 hours after ticket creation"), you would need to use custom functions with time-based logic or explore other automation features like SLA escalation rules.

36. Can a workflow rule be deactivated without deleting it?
Yes. When creating or editing a workflow rule, you can toggle the Active checkbox. Unchecking it deactivates the rule — it will no longer trigger, but its configuration is preserved and can be reactivated at any time. This is useful for seasonal rules or temporary process changes

37. Can a workflow rule be deleted or deactivated?
Yes, a workflow rule can either be deleted or deactivated by users who have the permission to manage automation.
To delete a workflow rule
  1. Navigate to Setup > Automations > Workflows > Rules
  2. Hover on the workflow rule and click the Delete () icon that appears next to the rule name
  3. Confirm by clicking the OK button


To deactivate a workflow rule
  1. Navigate to Setup > Automation > Workflow Rules
  2. Hover over the workflow rule and click the Deactivate () icon that appears next to the delete icon
  3. Click on the Inactive tab to confirm that the workflow has been deactivated and moved into the inactive tab



38. What happens if an email template referenced by a workflow alert is deleted?
If the email template associated with a workflow alert is deleted, the alert will fail to send when the rule triggers. No error notification is sent to the administrator by default — the alert simply silently fails. Always verify that referenced email templates exist and are active before relying on workflow alerts in production.