FAQs: Assignment Rules

FAQs: Assignment Rules

Assignment basics

1. What is an assignment rule and why do I need it?
Assignment rule is an automation tool that lets the support administrator automate the process of assigning tickets to agents.
 
Customer support is a crucial job, and timely and effective resolution of tickets is essential to maintaining customer trust in your business.
Customer satisfaction is directly proportional to the efficiency with which customer issues are managed. If a ticket is received but not processed on time, such as if it is a pending assignment to an agent for a week, it will directly impact the overall customer experience. This can lead to customer distrust and lost revenue.

The automation rule helps to efficiently manage the ticket assignment process by routing tickets to agents based on their skills, departments, and specializations.

For example, if you receive thousands of tickets daily, it is not feasible to handle and assign them manually. The drawbacks of manual assignment include tickets being assigned to the wrong agent with the wrong skill set, or when they are unavailable, tickets being missed due to human error, tickets taking a long time to resolve, and agent productivity being hampered.
 
If an assignment rule is configured, tickets will be checked against the criteria that is set and assigned to the appropriate agents, ensuring immediate attention and quick resolution. This will result in fewer backlogs, faster resolution, higher efficiency, and a reduced risk of tickets going unattended or unresolved.

Users with Profile permission to manage Help Desk Automation can activate or deactivate the assignment rules. When you deactivate a rule, it will be labeled as Inactive. Assignment rules can be reactivated, when needed.

2. What are the different ways to automate ticket assignment?
There are three primary methods for automating ticket assignment:
  1. Workflow rules — Set criteria and select the agent or team that should receive tickets when the condition is satisfied. For example, when a ticket is created with "Problem Type" as "Billing related," assign it to the "Payments Team."
  2. Assignment rules — Assign tickets to agents or teams when a ticket is created or a field is updated. Assignment rules support direct assignment and round-robin methods (load-based, sequential, or skill-based), including load balancing with caps on the number of tickets per agent.
  3. AI-based assignment (Zia) — Zia can be trained to predict field values on tickets. Once the predicted values are entered, the assignment rule or workflow takes over to assign the ticket. For example, if Zia predicts and auto-fills "Problem Type" as "Billing related," the ticket is automatically assigned to the Payments Team.
3. What is the difference between workflows and assignment rules?
  1. Workflow:
    Workflows automate multiple actions, such as sending alerts, updating fields, and assigning tickets based on specific criteria.
    For example, a workflow can send an email alert to the manager when a high-priority ticket is created, assign the ticket to a senior agent, and set the status to "Urgent."
    Workflows can be triggered by multiple criteria but do not support round-robin distribution. So if you're looking to automate multiple actions beyond just assigning, and you don’t need even distribution among agents, workflows are the way to go.
  2. Assignment Rule:
    Assignment rules only handle ticket assignment by automatically assigning tickets to agents or teams based on specific conditions. Here are the different ways you can assign tickets to agents.
    1. Team-Based Assignment - All sales inquiries are assigned to the Sales team.
    2. Round-Robin Within agents - Distribute finance support tickets evenly among selected agents using a round-robin sequential assignment.
    3. Round-Robin Within a Team - Distribute technical support tickets evenly among agents using round-robin.
    4. Skill-Based Assignment - Tickets about “JavaScript” are routed to agents who have JavaScript listed as a skill.
    5. Load-Based Assignment - Assign tickets to agents with the lowest current ticket count to avoid overload.
Assignment rules are triggered only by assignment-related conditions. More importantly, Assignment Rules support round-robin distribution, which helps in balancing the workload across available agents.
4. Who will be assigned to the ticket if no assignment rule has been triggered?

If a ticket does not meet the criteria of any active Assignment Rule, it will remain unassigned and can be manually assigned to an agent or team by another agent or administrator.

Agents can find the unassigned tickets in the ticket module

The ones without a profile picture are considered to be unassigned.

Unassigned tickets can be filtered by selecting the Unassigned open tickets under the View.

5. What happens if multiple assignment rule meet the same criteria? Which one takes precedence?
When multiple assignment rules match, the system applies the first matching rule based on the criteria order. The rules are executed in the order they are listed, and once a matching rule is applied, no further rules are evaluated.
6. What are the different criteria I can use to assign tickets?
Criteria is the condition that can be defined in automation rules to determine when and how a rule should be triggered. These criteria help the system filter and identify specific tickets based on their defined properties.

Let's think of criteria as "if this, then that" logic. For example:

Let's think of criteria as "if this, then that" logic. For example:
  1. If Priority is "High" → Assign ticket to Justin Stewart
  2. If Description contains "refund" → Assign ticket to Thomas Lewis from the Finance department
These conditions can be based on system fields like ticket properties, contact info, key information, time, and date.
7. Can I use custom field values as criteria to assign tickets?

Yes, you can use custom field values to assign tickets. Once you have created a custom field, it will be displayed under the list of fields in the assignment rule. When creating a rule, you can select a custom field (e.g., "cost of the product") and define conditions, such as "=" or ">." When a ticket meets the specified custom field criteria, it will automatically be assigned to the designated agent, team, or department.

8. Can I assign tickets based on specific keywords?
Yes, to assign tickets based on specific keywords, such as, you must create a rule with the following criteria:
For any of the keywords:
  1. "Keyword contains payment, refund, invoice"

This will assign tickets that contain payment, refund, or invoice to a specific team or agent.
For all keywords together, use separate conditions:
  1. "Keyword contains payment" AND
  2. "Keyword contains refund" AND
  3. "Keyword contains invoice"
This will assign the tickets to a team or agent when all three keywords are present.

 Manual assignment

9. Who can assign unassigned tickets manually?
Two categories of users can assign unassigned tickets:
  1. Support Administrators - They can assign unassigned tickets to any agent or team.
  2. Agents with the "View Unassigned" permission - These agents can view unassigned tickets and pick them up themselves. Only the administrator has the privilege to define the profile permissions that enable or disable this capability for agents or support administrators.
10. How to enable or disable the "View Unassigned" permission for agents?
To configure "View Unassigned" permission:
  1. Go to Setup > User Management > Profiles.
  2. Select the desired profile.
  3. Under Ticket Permissions, enable or disable the View Unassigned option.

This controls whether agents with that profile can see and pick up unassigned tickets on their own. If disabled, those agents will not see unassigned tickets and will rely on managers or administrators to assign tickets to them.
11. How to assign a ticket from the List View?
To assign a ticket from the List View:
  1. Click the Tickets module.
  2. Open a List View from the left menu.
  3. Click the Avatar image corresponding to the unassigned ticket.
  4. Select an agent or a team from the drop-down menu. User can also use the search bar to locate an agent or a team quickly.

This is useful when you are reviewing a queue of unassigned tickets and want to assign them without opening each one individually.
12. How to assign a ticket from the Detail View?
To assign a ticket from its Detail View:
  1. Open the desired ticket from the Tickets module.
  2. Click the Avatar image in the left menu.
  3. Select an agent or a team from the drop-down menu.

From the Detail View, you can assign the ticket to a team or to a specific agent within a team by clicking the icon alongside the team name.
13. Can I assign multiple tickets at once instead of one by one?
Yes. User can assign bulk tickets from the Ticket List View. Open a view, select the tickets you want to assign (using the checkboxes), and then assign them all in a single click. This is particularly useful when a batch of tickets needs to go to the same team or agent - for example, assigning all billing-related tickets to the Payments Team at once.
To assign multiple ticket
  1. Click the Tickets module.
  2. Select desired tickets.
  3. Select Assign to.
  4. Select the agent from the picklist.
14. Can I assign a ticket to a team and an agent simultaneously?
No, User cannot assign a ticket to a team and an agent simultaneously. When you assign a ticket to a team, it is available to all agents in the team. However, it will remain unassigned to any specific agent until an agent picks it up or it is manually assigned. When a user assigns a ticket to a specific agent, it is directly allocated to that individual, bypassing the team-level assignment.
15. Why can't I see all the teams when assigning a ticket?
Support representative may not see all teams while assigning a ticket because teams are department-specific. This means that only the teams associated with the ticket's department will be visible during assignment.

For example, if a ticket is created under Department A, rep could only see and be able to assign it to teams that belong to Department A. Teams from other departments will not be displayed as assignment options.
16. Can the ticket owner be changed after it has been assigned?
Yes. The ticket owner can be changed at any time. Support representative can reassign a ticket from one agent or team to another using the same assignment method - clicking the Avatar image in either the List View or Detail View and selecting a new assignee. This is useful when a ticket needs to be escalated to a different team or when an agent goes on leave and their tickets need to be redistributed.

 Direct assignment

17. What is the difference between a direct assignment rule, a round robin assignment rule, and skill based assignment rule?
A direct assignment rule is organization-specific and is used to assign tickets to agents, groups, or teams directly, regardless of the departments to which they belong. This rule can be used to assign tickets to agents directly and move the tickets from one department to another when needed. 

For example, if a ticket is related to order and delivery, it should be assigned to the appropriate department where agents are specialized to handle these cases. 

If the support admin has configured a direct assignment rule, the rule criteria can be defined as "subject is orders or delivery," and the keywords can include terms like orders, delivery, shipment, consignments, and so on. Based on this, the tickets will be routed to the department responsible for order and delivery, and the agents or teams within that department will be displayed. The support admin can then select the groups, agents, teams, or both, to assign tickets.
 
Similarly, a direct assignment rule can be implemented at the organization level to categorize tickets based on the departments and teams responsible for handling them.
 
A round robin assignment rule is department-specific and is used to assign tickets to agents, groups, or teams within a department. Round robin ticket assignment works on the basis of load sharing by agents. The round-robin assignment rule will distribute and assign the incoming tickets equally amongst a group of agents. In order to not overload the agents, the support admin can set a threshold for tickets, which is the maximum number of tickets that can be assigned to each agent at a time. So, tickets are assigned to the least loaded agent first and are then distributed to other agents in the group until they reach the threshold you’ve set.
 
The skill-based assignment rule is a part of the round robin assignment rule, which assigns tickets to agents based on their skills. For example, if there is a ticket referring to a technical issue, the agents assigned to it should possess technical knowledge to understand the issue. In that case, the skill requirement for the agent will be technical. Similarly, if the ticket is from a specific country and there are agents who work in that specific time zone and are familiar with the language, the tickets will be assigned to agents with the corresponding language as a skill type. Here, language is the skill, such as English, German, or French.
18. How do I configure a direct assignment rule?
Users with Profile permission for managing Help Desk Automation can create assignment rules.
To configure a direct assignment rule:
  1. Navigate  to Setup > Automation > Assignment Rule
  2. On the Direct Assignment Rules List page, click New Direct Assignment
  3. On the New Direct Assignment Rule page, do the following:
  4. Enter the Rule Name.
  5. Specify the Execution Criteria for the rule.
  6. You can choose either Ticket Creation or Ticket Updation or both.
  7. Click Add Target.
  8. On the Add Target page, do the following:
  9. Ticket coming to department: Select the department where you would receive the tickets.
  10. Criteria: Enter criteria for the rule. You can associate up to 25 criteria using AND/OR operators.
  11. Move ticket to: Select the department were you want the tickets to be moved.
  12. Assign ticket to: Select the agent who should be assigned as the owner of the tickets.
  13. Click Save.

19. Can I assign tickets to multiple agents or teams using direct assignment rule?
No, the direct assignment rule allows assigning a ticket to only one agent or one specific team at a time. If there is a need to assign tickets to multiple agents, you must create separate direct assignment rules for each agent or create a round-robin assignment rule.
20. Is it possible to reassign tickets to a different department using assignment rules?

Yes, you can reassign tickets to a different department using assignment rules. When creating a direct assignment rule, you can specify the Move Ticket To option to transfer tickets to another department automatically.

21. Can I deactivate or delete an assignment rule?
Yes, you can deactivate or delete an assignment rule.
To deactivate assignment rules:
  1. Click the Setup icon (  ) in the top bar.
  1. In the Setup Landing page, click Assignment Rules under Automation.
  1. In the Direct Assignment Rules List page, click to open a rule.
  1. In the Rule Details page, uncheck the Active option.
  1. Click Save.


Note: If you don't want to use Direct Assignment Rules that have been configured, you can toggle it to deactivate all rules at once.


 Round-robin assignment

22. What are the different types of round-robin assignment rules?
Round-robin assignment distribute tickets among agents. When creating an assignment rule, you can select the "Assign To" option, choose a team, and enable the "Round Robin" setting. This automatically assigns incoming tickets to agents in the team in a rotation. There are three types of round robin assignment rule:
  1. Load Based Assignment - Assign tickets to agents based on their load until everyone receives the set threshold. For example, if three agents in a team, such as A with 5 tickets, B with 9 tickets, C with 3 tickets, and there is a new ticket that arrives, the load base round robin rule will assign the ticket to the agent C until they reach 5. After C reaches 5, the system will start to assign tickets to both agent A and Agent C until they reach 9 tickets. Meanwhile, agent B has higher number of tickets, so the system will not assign any ticket to them.
  2. Sequential Assignment - Assign tickets equally among agents in a sequential and round-robin fashion. For example if three agents (A, B, C) are in the team, and six tickets arrive, the system will assign them in this order: Ticket 1 → A, Ticket 2 → B, Ticket 3 → C, Ticket 4 → A, Ticket 5 → B, Ticket 6 → C, and so on.  This ordering will happen based on the alphabetical order of the agent's name. However, for the first time, agents will be assigned ticket based on the order on how the agents were added in the agents field.
  3. Skill Based Assignment - Assign Tickets to agents according to their designated skills.View Skills. For example, if a customer submits a technical issue, the ticket is automatically assigned to an agent with technical skills rather than a general support agent.
This combination of round robin and agent-level threshold helps prevent agent overload on ticket distribution.
23. How do I configure round a robin assignment rule and a skilled based rule in my desk account?
Round-robin ticket assignment is a department-specific rule that distributes incoming tickets equally among a group of agents. To prevent overloading agents, the support admin can set a threshold for tickets, which is the maximum number of tickets that can be assigned to each agent at a time. The threshold can be set from 1 to 200. Tickets are first assigned to the least loaded agent, and then to other agents in the group until they reach the threshold.
 
If all agents have reached their threshold and incoming tickets cannot be assigned, the support admin can toggle on "Assign Backlogs" and set a threshold for backlog tickets from 1 to 50. Once agents resolve tickets, the round-robin rule will check for and assign backlog tickets to agents with available threshold.
Your support admin can choose whether to assign backlog tickets based on the due date or the date it was created to available agents. They can also define whether the incoming tickets should be assigned to agents or added to backlogs.

Round robin assignment rules can be assigned to teams or agents. In the case of a team, the tickets will be assigned to the agents in that team according to the load.

The skilled based rule is similar to the round robin rule. The only difference is that the tickets will be assigned to the agents having the skill set defined in the criteria to handle tickets.
 
Users with the profile permission to manage Help Desk Automation can create assignment rules.


 

To configure a round robin assignment rule:
  1. Go to Setup (  ) > Automation > Assignment Rule.
  1. Click Round Robin under the Assignment Rules sub-menu.
  2. On the Round Robin Rules list page, click New Round Robin Assignment.
  1. Select the department from the available departments drop-down for which you want to create this rule.
  1. On the New Round Robin Assignment page for the selected department, complete the following steps:
    • Enter the Rule Name.
    • Specify the Execution Criteria for the rule.
    • You can choose either Ticket Creation or Ticket Updation or both.
  1. Click Add Target.
  1. On the Add Target page, complete the following steps:
    • Criteria: Enter criteria for the rule. You can associate up to 25 criteria using AND/OR operators.
    • Assignment Method: You may choose an assignment method from Round Robin assignment and Skill Based assignment.
    • Assign ticket to: Select the agent who should be assigned as the owner of the tickets.
  1. Click Save.
Similarly, while creating a round robin assignment rule, if you choose assignment method as skills, select Skill based Assignment as the Assigning Method. Specify who should be assigned to tickets based on their skills.
You can select between:
    • Agents: Select the assignees from the drop-down menu.
    • Team Select a team from the drop-down menu to add all of their agents.
      You can exclude agents within a team by checking the Exclude agents from this assignment option.


Note: 
  1. The rule will not reassign tickets that were assigned via other automations.
  2. The rule will not assign more tickets than the number specified under threshold.
24. What happens to incoming tickets once the agent threshold is met for a round-robin rule?
If an agent's threshold is reached, any surplus tickets created in Zoho Desk are held back in a queue (backlog queue). The tickets from this queue are assigned to agents as and when they resolve the tickets that are assigned to them.

25. What happens if the assigned agent is unavailable or out of office?
By default, if an agent is unavailable or out of office, the ticket remains assigned to them, and no automatic reassignment occurs. However, in Round-Robin Assignment, you can manage this by configuring the Assign tickets to offline agents setting:  
  1. Disabled: Tickets will be assigned only to online agents in the mail channel.
  2. Enabled: Tickets will be assigned to both online and offline agents.
26. What happens to the round-robin sequence if I add or remove agents from the rule?
If any modifications are made to the list of agents in the "Assign Tickets To" field — whether adding or removing agents — the round-robin sequence resets. It will start assigning tickets from the first agent on the updated list. However, this reset does not apply when tickets are assigned to teams; team-based assignments follow their own internal distribution logic.

When agents share identical names, the system uses their user IDs (auto-generated when a user is added to Zoho Desk) as unique identifiers. The agent who was added first to the Desk account will be first in the sequence, followed by other agents in alphabetical order.
27. Is there a limit to the number of agents that can be added under round-robin rule?
There is no limit to the number of agents that can be assigned under a round-robin rule. User can add as many agents as needed, and tickets will be distributed among the added agents.
28. What happens when an agent goes offline or reaches their ticket threshold in a Sequential round-robin?
When agents transition between online and offline status, or when they reach a predetermined threshold that leads to their exclusion from sequential assignment.

This is a decision made by administrators who choose not to assign tickets through sequential assignment in scenarios where agents are offline or have met a specified threshold. This ensures that tickets are not held up waiting for an unavailable agent and are instead routed to the next available person in the sequence.

29. What are the important points to remember when creating Round-Robin rules?
Several key constraints apply:
  1. Round-robin rules are department-specific.
  2. Admins can associate up to five targets per round-robin rule.
  3. If a ticket owner is already assigned via other automations (workflow, direct assignment, or macro), the round-robin rule will not reassign owners to those tickets.
  4. By default, tickets are assigned to agents who are online in the email channel. However, offline agents can also be included by setting the round-robin preferences accordingly.
  5. Unassigned or backlog tickets will only be assigned in a round-robin manner if the ticket has received a customer response within 30 days.

 Skill-based assignment

30. Can I assign tickets to specific agents based on their skill set?
Yes, you can assign tickets to specific agents based on their skill set using Round-Robin’s Skill-Based Assignment. This method allows you to automatically route tickets to agents who have the required skills for handling specific types of queries.
To do skill-based assignment:
  1. Navigate to Setup > Automations > Assignment Rules > Round robin.
  2. Click New Round Robin Assignment.
  3. Choose the Department.
  4. Enter a Name and Description.
  5. Choose the execution criteria:
    1. Ticket Create - Execute the rule immediately after the ticket is created.
    2. Ticket Update - Execute the rule after the ticket undergoes a field update.
  6. Click Add Target.
  7. Under criteria, select the field and values to filter out tickets.
  8. Select the Skill Based Assignment.
  9. Select the option to assign the ticket to Agent or Team.
  10. Select the list of Assignees or Teams.
  11. When selecting teams, check the Exclude Agents checkbox and select the agents you want to exclude from being assigned tickets through this assignment rule.
  12. Click Save.
Tickets will then be assigned only to agents who match the defined skill criteria.
31. How do Skill-based round-robin rules work, and how to configure skills?
Skill-based assignment routes tickets to agents based on their expertise. The system identifies skills based on criteria provided in the configuration — it matches the criteria in the incoming ticket and ascribes the relevant skills to it. Skills can also be assigned manually or via workflows.
To add skills and skill sets:
  1. Navigate to Setup > Customization > Skills.
  2. On the Skill Types tab, click Add Skill Type.
  3. Enter the Skill type and Save.
  4. Enter the Skill name and select the Skill Type from the drop-down list.
  5. Enter a Description if needed.
  6. Define the Criteria by selecting fields that will identify the skill in the ticket.
  7. Select the agents from the available list.
  8. Click Save.
Examples of skill sets include:
  1. Language expertise — French, German, Japanese
  2. Domain expertise — Data science, Designer, Programming language
  3. Business skills — Finance, Marketing, Sales, Engineering
  4. Leadership skills — Critical solution provider, planning and strategic thinker, information gathering and research

32. What are Skill Preferences, and how to configure Skill Preferences?
Skill Preferences allow admins to define whether skills should be added automatically to tickets when they are created or edited. If this toggle is turned off, skills would need to be added manually or via workflows.
Admins can also choose where new skills will be displayed within the ticket:
  1. Top of the list
  2. Bottom of the list
  3. Order in which they are added during settings
To configure skill preferences:
  1. Go to Setup > Customization > Skills.
  2. Click the Skill Preference icon.
  3. Toggle Auto-add skills to tickets.
  4. Choose the location where skills will be viewed within the ticket.
  5. Click Save.

 Assignment notifications and coordination

33. What happens when a ticket is assigned to an agent or a team — are notifications sent?
Yes. When a ticket is assigned to an agent, that agent receives an email notification informing them of the assignment. When a ticket is assigned to a team, a notification is sent out to all agents in that team. This ensures that assigned agents are immediately aware they have a new ticket to handle, reducing the risk of tickets being overlooked.
34. How do I stop email alerts to the agents for every ticket assignment?

If you don't want to notify the agent when a ticket is assigned to them or the team you can turn off the notification.

To stop email notification

  1. Navigate to Setup > Customization > Notification.

  2. Disable assigning a ticket under Agent Notifications.

35. How can multiple agents avoid replying to the same ticket simultaneously?
When a ticket is assigned to one support representative, other agents may be restricted from replying to that ticket, helping ensure that only the assigned agent handles the conversation and preventing multiple agents from responding simultaneously. This reduces duplicate replies, avoids confusion, and maintains clear ownership of customer communication.

 Other assignment scenarios

36. How can I assign tickets to different agents based on a specific time range?
To create a rule that assigns tickets based on specific days and time ranges, you can use time-based criteria.
Let’s say you want tickets received during Chicago, USA business hours to assign to Agent A, and tickets received between Melbourne VIC, Australia business hours to assign to Agent B. You can set this up using the Ticket Created Time condition in your rule.
Steps to set it up:
  1. Navigate to Setup > Automation > Assignment Rules.
  2. Click New Assignment Rule.
  3. Under Criteria, choose Ticket Created Time - During business hours of - Chicago, USA → Assign to Agent A.
This is useful for managing shift-based agent availability and for a faster response time based on when the ticket arrives.

Time-Based Conditions:

Time-based Criteria
Conditions
Example
Execution time

  1. During business hours of
  2. Outside business hours of
  3. On a holiday of
  4. Not a holiday of

Execution time - During business hours of - Tokyo GMT+9

The ticket assignment to the Agent A execution will be occurring during the business hours set in the Tokyo time zone GMT+9.
Created time

  1. is
  2. isn't
  3. is after
  4. is before
  5. between
  6. not between
Created time - between - Custom
17/04/2025 09:00 AM
19/04/2025 12:00 PM

Tickets created in between the time frame such as 17/04/2025 09:00 AM to 19/04/2025 12:00 PM will be assigned to Agent B.
Modified time

  1. is
  2. isn't
  3. is after
  4. is before
  5. between
  6. not between
Modified time - is after - Custom
14/04/2025 09:00 AM

Any ticket modified after 14/04/2025 09:00 AM will be assigned to Agent C.
Ticket closed time

  1. is
  2. isn't
  3. is after
  4. is before
  5. between
  6. not between
Ticket closed time - is before - Custom
13/04/2025 12:00 PM

All the tickets that have been closed before 12:00 PM on 13th April 2025 will be assigned to the Agent D.
37. How to automatically assign reopened or escalated tickets?
Tickets often require immediate attention or a higher level of expertise, and auto-assignment, which will help in routing them to the right agent or team without delay.
To automatically assign reopened tickets:
  1. When creating an assignment rule, select the Execute On option as Ticket Update.
  2. Add a criteria, such as: Status → is → Reopened.
  3. Under Add Target, select Assign Ticket and choose the desired agent or team.
To automatically assign escalated tickets:
  1. Add a criteria as: Is Escalated → is → ✅.
  2. Under Add Target, select Assign Ticket and choose the desired senior agent or the escalation team.
38. Can a ticket be reclassified automatically if its details change after creation?
Yes. Workflows can be configured to ensure that if a field is modified, the ticket will be reclassified to match the set criteria. For example, if the severity at the time of ticket creation was "L1" and it changes to "L3" as the resolution progresses, the ticket will be reclassified based on the latest status and assigned to the appropriate team. This ensures that tickets are always routed to the right team based on their current state, not just their state at creation.

 Ticket triaging

39. What is ticket triaging, and why is it important?
Ticket triaging is the process of tagging or classifying tickets to route them to the right teams. It should be done at the ticket creation stage to prevent delays, and also when ticket details are edited or updated.

Triaging is important because it ensures that every ticket reaches the appropriate team quickly, reducing resolution time and preventing tickets from being overlooked. Without triaging, tickets may sit in a general queue while agents manually review and route them, a process that is time-consuming, error-prone, and unsustainable as ticket volumes grow, especially when customers submit requests from multiple channels.
40. What is the difference between manual triaging and automatic triaging?
  1. Manual triaging — Businesses ensure that the ticket creation form includes all the necessary fields needed to classify tickets, such as product name, service type, and validity period. These fields must be marked as mandatory so that customers and agents enter an appropriate value before submitting the ticket. Tool tips and field validation further ensure correct values are entered. The classification itself is done by the person filling out the form.
  2. Automatic triaging — Tickets are classified based on severity, priority, agent skill sets, or status through workflows or assignment rules. By setting field values as criteria, the system automatically groups tickets into relevant categories and assigns them to predefined agents or teams. Workflows can also ensure that if a field is modified, the ticket is reclassified to match the updated criteria. For example, if the severity at ticket creation was "L1" and it changes to "L3" as resolution progresses, the ticket will be reclassified based on the latest status and assigned to the appropriate team.
41. What are the best practices for effective ticket triaging?
While every business is unique, common triaging strategies include:
  1. Priority ticketing — Group tickets based on urgency and business impact. Service outages that prevent product usage are critical/Tier 3 issues requiring immediate attention. Fields like "ticket category" or "issue type" help identify and group these tickets.
  2. Status-based grouping — Tickets that are "on hold" must be evaluated periodically to rule out unintentional delays. Grouping based on created time and response due date helps identify tickets with prolonged closure. Such tickets can be routed to a dedicated team of debug team members, support and product leads, and Subject Matter Experts.
  3. Channel-level classification — Distribute tickets from different channels to different teams. Channels receiving the most tickets can be routed to a small team of agents and product experts equipped to provide quick solutions.
  4. Agent's expertise — Agents highly skilled in a particular language, product, or critical issue management should be assigned those specific tickets. Fields like product type, region, language, and issue type help map tickets to the right person or team.
  5. Role-based routing — Implementation requests, onboarding assistance, and industry-based customized demos are usually handled by specialized teams. Identifying such requests and routing them directly to the appropriate role — such as product trainer, support lead, or presales executive — ensures effective ticket management.

 Automation and AI

42. How do the three automation methods work together for ticket assignment?
The three methods — workflow rules, assignment rules, and AI-based assignment — can complement each other:
  1. Zia (AI-based assignment) predicts and auto-fills field values on incoming tickets. For example, Zia might predict "Problem Type" as "Billing related" based on the ticket content.
  2. Workflow rules or Assignment rules then use those field values as criteria to assign the ticket. For example, when "Problem Type" is "Billing related," the ticket is automatically assigned to the "Payments Team."
This combination means that even tickets submitted without clear categorization can be intelligently routed — Zia fills in the missing classification, and the automation rules handle the assignment. The result is an end-to-end automated flow from ticket creation to team assignment, with minimal manual intervention.
43. How does AI-based assignment using Zia work?
Zia can be trained to predict field values of tickets. Once Zia predicts and auto-fills a field value, the existing assignment rule or workflow takes over to assign the ticket based on that predicted value.

For example, if Zia predicts and auto-fills the field "Problem Type" as "Billing related," the assignment rule or workflow configured for that criteria will automatically assign the ticket to the "Payments Team" for further action. This is particularly useful for tickets that arrive without clear categorization — Zia analyzes the ticket content and predicts the appropriate field values, enabling the automation to route the ticket correctly without any manual classification step.