FAQs: Supervisor Rules or Time-based Automations

FAQs: Supervisor Rules or Time-based Automations

What is a Supervisor rule?
Supervisor rules help teams manage tasks that don’t require an immediate response. Unlike workflow rules, which run as soon as a ticket is created or updated, Supervisor rules let actions occur after a set time period.

This means alerts, tasks, and field updates can be scheduled to run only when a ticket stays inactive, unassigned, or unresolved for longer than expected.

For example, administrators can use a Supervisor rule if a ticket remains unassigned for more than two hours, the rule can automatically notify the manager so they can quickly assign it to the right agent. This way, unassigned tickets don’t sit unnoticed in your help desk.
How is a Supervisor rule different from a Workflow rule?
Workflow rule
Supervisor rule
Workflow rules are event-based. 
Supervisor rules are time-based.
Automation triggers immediately when a ticket is created, updated, or a field value changes.
Automation triggers after a specified time interval has passed since a defined event.
Executes instantly when conditions are met. Triggered based on current field values or changes (e.g., Status is Open, Priority is High).
Executes once every hour, checking tickets that meet the defined time-based condition. Triggered based on elapsed time conditions (e.g., Hours since assigned > 2, Hours since last response > 4).
Can trigger multiple actions like alerts, field updates, and custom functions simultaneously.
Can trigger up to three time-based actions per rule: one alert, one task, and one field update.
Available across multiple modules (Tickets, Contacts, Accounts, etc.).
Applicable only to the Tickets module.
Why should I use Supervisor rules?
Supervisor rules help administrators automate time-based actions so that no ticket stays unattended or unresolved for too long.
Here are the key benefits:
  1. Automatically escalates tickets that stay unresolved for too long, keeping queues organized and manageable.
  2. Removes the need for teams to constantly check for inactive or overdue tickets by automating the follow-up process.
  3. Supports time-based automation needs where immediate action isn’t required, allowing for scheduled or delayed checks at the right time.
  4. Promotes timely ticket handling: Triggers follow-up actions on tickets that need attention, helping teams resolve issues faster and more consistently.
How to create a Supervisor rule?
Users can create Supervisor rules to automatically perform actions on tickets based on time-based conditions.
To set up a Supervisor rule:
  1. Navigate to Setup > Automation > Supervisor Rules > Rules.
  2. Select the department.
  3. Click Create Rule.
  4. Give the rule a name and a description.
  5. Mark the rule Active.
  6. Select the Business hours during which this rule will apply.
  7. Click Next.
  8. Under Criteria, click Select field to determine after which action the rule needs to be executed. This includes time-based criteria such as:
    1. Hours since status updated
    2. Hours since closed
    3. Hours since reopened
    4. Hours since assigned
    5. Hours since first assigned
    6. Hours since requestor responded
    7. Hours since agent responded
    8. Hours since due date
    9. Hours to due date
    10. Hours since modified
    11. Hours since created
    12. Hours since first response pending
    13. Hours since agent response pending
    14. Hours since requestor response pending
  9. Under Action, click + to add actions to be performed when the time-based action is executed.
    1. To create an alert:
      1. Provide a name and description.
      2. Select an email template or create an email template.
      3. Choose who to send the email alert to: team/role/role and subordinate/agents.
      4. Under Also Notify, the email can be sent to the record owner/record creator/notify contact/additional recipients as well.
      5. Click Save.
    2. To update the field value:
      1. Provide the assignment value name and description.
      2. Under Assignment Value, select the Fields that need to be updated.
      3. Provide the Value that needs to be changed.
    3. To set up a task:
      1. Give the task subject.
      2. Choose the task’s status.
      3. Set the task priority.
      4. Check the box if the ticket owner needs to be assigned as the task owner.
      5. Select an agent who needs to be assigned to this task. Even if the ticket owner will be the task owner, select the agent who should be assigned to this task if the ticket is unassigned.
      6. Set the due date for the task from the Supervisor Rules trigger time by clicking the timer and time selector (minutes, hours, days, or months).
      7. Provide a description.
      8. Click Save.
  10. Click Save again to save the overall Supervisor rule.
Is it possible to use supervisor rule in standard and custom modules ?
Supervisor rules are supported ONLY in  the Tickets module. It aims to help monitor ticket's activities such as passed hours since status update, assignment, or response and trigger respective actions like alerts, tasks, or field updates when a defined time condition is met.
What types of time-based conditions are available in Supervisor rules?
All time-based conditions are set and calculated hourly, rather than having an option to define them in minutes or half-hour intervals. Here are the time-based action available in supervisor rules:
  1. Hours since status updated
  2. Hours since closed
  3. Hours since re-opened
  4. Hours since assigned
  5. Hours since first assigned
  6. Hours since requestor responded
  7. Hours since agent responded
  8. Hours since due date
  9. Hours to due date
  10. Hours since modified
  11. Hours since created
  12. Hours since first response pending
  13. Hours since agent response pending
  14. Hours since requestor response pending
How does Zoho Desk calculate time for Supervisor rule conditions?
Zoho Desk calculates time for Supervisor rules based on the Business Hours chosen while setting up the rule. Time is counted only during the company’s working hours set under Setup > Organization > Business Hours.

The timer pauses after hours, weekends, and on holidays, then resumes when business hours start again. For example, if a ticket is assigned at 5 PM Friday and your hours end at 6 PM, the next hour is counted only when business hours resume on Monday.



What problem do supervisor rules solve that workflow rules cannot?
Workflow rules are designed to take action the moment a ticket is created or updated — they are event-driven and execute instantly. However, many support processes depend on the passage of time rather than an immediate event. For instance, you may want to escalate a ticket if it has been sitting unassigned for three hours, or remind an agent if a customer's response has gone unanswered for a full day. Workflow rules have no mechanism to "wait" and then act. Supervisor rules fill this gap by evaluating tickets on a recurring hourly schedule and triggering actions only when a specified amount of time has elapsed since a defined event on the ticket.
Which module do supervisor rules apply to, and can they be used for contacts, accounts, or other modules?
Supervisor rules are exclusively available for the Tickets module. They are purpose-built to monitor ticket lifecycle events — such as how long a ticket has been in a particular status, how long since it was assigned, or how long since a customer or agent last responded. They cannot be configured for Contacts, Accounts, or any other standard or custom module.
Who has the authority to set up and manage supervisor rules?
Only users with the Support Administrator permission profile — or any profile that includes the Help Desk Automation permission under Administrative Permissions — can create, edit, activate, deactivate, associate actions with, and delete supervisor rules. Standard agent profiles without this administrative permission cannot access or modify these rules.

How often does the system evaluate supervisor rules, and does timing affect which tickets get picked up?
Supervisor rules are evaluated automatically once every hour. During each hourly run, the system scans tickets to see if any meet the time-based conditions defined in the rule. It is important to understand that the evaluation is not continuous or minute-by-minute — it happens in discrete one-hour cycles. This means that a ticket may not trigger an action at the exact moment the time threshold is crossed; instead, it will be picked up during the next hourly evaluation. Additionally, the system only checks tickets that have received a customer response within the last 30 days. Tickets with no recent customer reply are skipped entirely, even if they technically meet the time condition.
What does the "is" comparison option mean, and how does it differ from "is less than" or "is greater than"?
When defining a time-based condition, you can compare the elapsed time using three operators: is, is less than, and is greater than. Because the system evaluates rules in one-hour intervals, these comparisons work at the granularity of whole hours, not minutes.
  1. "is greater than 2" matches tickets where more than two full hours have passed since the defined event. If the rule runs at 08:00 AM, it captures tickets where the event occurred before 06:00 AM.
  2. "is less than 2" matches tickets where fewer than two hours have passed. At an 08:00 AM evaluation, this captures tickets where the event happened between 06:00 AM and 08:00 AM.
  3. "is 2" targets tickets that fall within the specific two-hour window during the hourly check. At an 08:00 AM run, this would match tickets where the event occurred between 05:00 AM and 06:00 AM — meaning those tickets are now in their third hour but were in their second hour during the previous check.
The "is" operator is particularly useful when you want to act on tickets at a specific age rather than all tickets older or younger than a threshold.
Can I use decimal values like 1.5 or 0.5 hours in my time-based conditions?
No, The system only accepts whole numbers for time values in supervisor rule conditions. If you enter a decimal such as 1.5 or 0.5, the system will not read it correctly. This is because the evaluation cycle itself operates on one-hour intervals, so fractional hours have no meaning within the rule's logic. If you need finer granularity, consider whether a workflow rule or another automation approach might be more appropriate for your scenario.
How do business hours affect the time calculation in supervisor rules?
When creating a supervisor rule, you choose whether the rule should operate based on Business hours or Calendar hours. If you select Business hours, the timer only counts time during your organization's defined working hours, which are configured under Setup > Organization > Business Hours. The clock pauses outside of working hours, on weekends, and during holidays, then resumes when the next business period begins.

For example, if a ticket is assigned at 5:00 PM on a Friday and your business hours end at 6:00 PM, only one hour is counted for that day. The timer does not continue over the weekend. The next hour is only counted once business hours resume on Monday. This is important to understand because a condition like "hours since assigned is greater than 2" could span multiple calendar days if your business hours are limited.

If you select Calendar hours instead, the timer runs continuously regardless of weekends, holidays, or after-hours.
What types of actions can a supervisor rule perform, and is there a limit on how many actions each rule can trigger?
Users cannot associate two alerts with a single rule or add a custom function as an action. The one-alert, one-task, one-field-update structure is the maximum per rule. Each supervisor rule can be associated with up to three time-based actions: one alert, one task, and one field update. These are the only action types supported.
  1. Alerts send email notifications to selected recipients — such as a team, role, role and subordinates, or specific agents. You can also notify the ticket owner, ticket creator, the contact on the ticket, or additional recipients. Alerts require an email template to be selected or created.
  2. Field updates change the value of a specified field on the ticket when the condition is met. You choose which field to update and what the new value should be.
  3. Tasks create a new task associated with the ticket. You can define the task subject, status, priority, owner, due date (calculated from the rule's trigger time), and description. If the ticket is unassigned, you can designate a fallback agent to own the task.
What are some practical scenarios where supervisor rules add value?
Supervisor rules are ideal for any situation where the urgency of an action depends on how long something has been waiting. Common use cases include:
  1. Unassigned ticket alerts: Notify queue managers when a ticket has gone unassigned beyond a set number of hours, so it doesn't slip through the cracks.
  2. Resolution SLA monitoring: Alert agents or managers when a ticket has remained in an unresolved status for too long, helping maintain response and resolution commitments.
  3. Follow-up on customer responses: Notify an agent when a customer has responded to a ticket but the agent hasn't replied within a defined window, ensuring no customer message goes unanswered.
  4. Reopened ticket handling: Automatically assign or escalate tickets that have been reopened after a certain period, ensuring reopened issues get prompt attention.
  5. Reassignment visibility: Notify support managers when agents reassign tickets, providing oversight into ticket handoffs and potential bottlenecks.
  6. Response time reporting: Inform managers approximately how long it took an agent to respond after a ticket was assigned to them, supporting performance monitoring.
What happens to tickets that haven't received a customer response recently, are they still evaluated?
No, During each hourly evaluation, the system only examines tickets that have received a customer response within the preceding 30 days. Tickets without a recent customer reply are excluded from the check entirely. This means that if a ticket has been sitting idle with no customer interaction for over 30 days, supervisor rules will not evaluate or act on it, even if the time-based condition would technically be satisfied. This behavior helps focus automation on active, ongoing conversations rather than stale or abandoned tickets.
If a ticket is unassigned, who becomes the owner of a task created by a supervisor rule?
When configuring a task action within a supervisor rule, you can choose to assign the ticket owner as the task owner. However, if the ticket itself is unassigned at the time the rule triggers, the system needs a fallback. For this reason, the rule configuration requires user to select a specific agent who will be assigned the task in cases where the ticket has no owner. This ensures that the task always has a responsible person, regardless of the ticket's assignment status.