While creating a workflow rule, you can decide whether the ticket should be assigned during creation or upon edit. Using criteria, tickets of a certain kind can be identified, and when the condition is met, the ticket is auto-assigned to the predefined agent, team, role, etc.
To assign tickets using workflows
Navigate to Setup > Automation > Workflow Rules.
Click Create Rules.
Select the Tickets module from the drop-down and enter the Rule Name.
Click Next.
Select Execute On, Create, Edit, or Customer Reply, then click Next.
Select a Criteria if needed, then click Next.
Under Actions, select Assign Ticket.
In the Assign Ticket page, enter the Name and select an Assignee (Agent, Team, or Agent in a team).
Click Save.
Assigning tickets using Assignment rules
Assignment rule can be set in two ways:
Direct assignment
Using direct assignment, tickets can be assigned to an agent or team directly. The tickets can also be moved to another department if needed. For example, if a ticket requesting implementation assistance is submitted to any department, then you can use this rule to define the department it should be moved to.
To create a direct assignment rule
Go to Setup > Automation > Assignment Rules > Direct Assignment.
Click New Direct Assignment.
Enter the Rule name and Description, then select Execute Rule on Ticket Create and/or Ticket Update.
Click Add Target.
Under Tickets coming to, select any department or a specific department. By default, the department in which you are creating the rule will be displayed here. You can change this, if necessary.
Enter a Criteria.
Under Move Ticket To, select a department, if needed.
Assign To an Agent, or leave the ticket unassigned.
Click Save.
Round-robin assignment
This method ensures tickets are assigned to agents in a circular fashion, maintaining an orderly approach. The round-robin method is divided into three types:
Load based - This rule optimizes the ticket load of each agent. Tickets are assigned to the least loaded agent first. The load balancing will continue until all of your agents are assigned an equal number of tickets. After that, tickets are distributed to agents in the round-robin fashion.
Sequential - Tickets are assigned to agents in the order in which they are added during the configuration. For example, if John, Ben, and Amy are added to a rule in this order, then the tickets will be assigned first to John, then Ben, and subsequently to Amy. If all agents or a team are chosen, then the agents will be assigned tickets in alphabetical order (Amy, Ben, then John).
Skill based - Agents who have domain expertise, language proficiency, or negotiation abilities can be handled tickets based on their skill-sets. This will ensure that the customers get the best service from the experts.
Types of Round-robin rules
Load based assignment rule
Sequential assignment rule
Skill based assignment rule
Load based assignment rule
Despite adapting effective triaging and routing methodologies, support teams can feel overwhelmed when a large volume of tickets arrive. Every customer request requires a dedicated response from the agent, and it's important for the business to maintain a high quality of standard. To prevent burnout and ensure ticket resolution guidelines are adhered to, orgs can consider distribution of tickets through load management.
Load balancing ensures every agent has tickets within the threshold limit at any point in time. The remaining tickets are added to the backlog and will again be assigned in the round-robin manner to agents as they continue closing the existing tickets.
Sequential assignment rule
This rule ensures that tickets are assigned to agents following the sequence in which they were added to the rule during configuration.
For example, if John, Ben, and Amy are added to a rule in this order, then the tickets will be assigned first to John, then Ben, and subsequently to Amy. If all agents or a team are chosen, then the tickets will be assigned to the agents in alphabetical order (Amy, Ben, then John).
Sequential assignments can be helpful for teams that are specialized in handling specific types of issues. The senior team members and SMEs added at the beginning will ensure that customer problem are inferred correctly and the proper solution is provided.
Note:
Adding or removing agents - If any modifications are made to the list of agents in the "Assign Tickets To" field by adding or removing, then the round-robin sequence will reset. It will start assigning tickets from the first agent on the list. Note that this reset does not apply when the tickets are assigned to teams.
When choosing all agents or a specific team, in cases where agents share identical names, then the user IDs (auto-generated by the system when a user is added to Zoho Desk) will be used as unique identifiers. The agent who was added first to the Desk account will be first in the sequence followed by other agents. After that, the alphabetical order will be followed.
When agents transition between online and offline status, or when they reach a predetermined threshold leading to their exclusion from sequential assignment, they are marked as "SKIPPED" and positioned at the end of the queue. This decision is made by administrators who choose not to assign tickets through sequential assignment in scenarios where agents are offline or have met a specified threshold.
Skill based assignment rule
Agents may have expertise in a particular domain, fluency in specific languages, or be a subject matter expert with good analytical and problem solving skills. Agents who have these skills can be associated with specific skill sets, which will ensure tickets are routed to the right team and the resolution is provided quickly.
Organizations can add a list of skill sets based on the ticket history, customer requirements, or business perspectives. For example, some skill sets that can be added are:
Language expertise - French, German, Japanese.
Domain expertise - Data science, Designer, Programming language
Business skills - Finance, Marketing, Sales, Engineering
Leadership skills - Critical solution provider, planning and strategic thinker, information gathering and research
Agents can be associated with each of these skills. Once a ticket is categorized based on the skill set, they will be assigned to the respective team or agent automatically. This significantly reduces the time spent in understanding the requirement, routing it to the right team, and providing a relevant solution.
The system can identify the skills based on the skill sets that have been added, based on which it will ascribe the skills to a ticket. You can also assign skills manually or via workflows.
To add skills and skill sets
Navigate to Setup ( ) > Automation > Skills.
On the Skill Types tab, click Add Skill Type on the upper-right corner.
Enter the Skill type and Save.
Enter the Skill name and select Skill Type from the drop-down list.
Enter Description, if needed.
Define the Criteria by selecting fields that will identify the skill in the ticket.
Select the agents from the available list.
Click Save.
Skill preferences
Allows to define whether skills should be added automatically to the tickets when they are created or edited. If this is toggled, then skills would be added manually or via workflows. Under preferences, admins can choose where and how the new skills will be displayed within the tickets:
Skills can be positioned:
Top of the list
Bottom of the list
Order in which they are added during settings
To add skill preferences
Go to Setup > Automation > Skills.
Click the Skill Preference icon ( ).
Toggle Auto-add skills to tickets.
Choose the location where the skills can be viewed within the ticket from the available options.
Creating round robin rules
Points to remember
Round robin rules are department specific.
You can associate up to five targets per round-robin rule.
If a ticket owner is already assigned via other automations, such as workflow or direct assignment or macro, then the round-robin rule will not reassign owners to those tickets.
By default, tickets are assigned to agents who are online in the email channel. However, offline agents can also be included while setting the round-robin preferences.
Unassigned or Backlog tickets will only be assigned in a round-robin manner if the ticket has received a customer response within 30 days.
The tickets will be assigned in the following sequence when all the automations are active: Direct assignment > Workflow > SLA > Round robin (sequential > load balancing > skill based) > Blueprint > Notifications.
To create a round robin rule
Navigate to Setup > Automation > Assignment Rules > Round-robin.
Click New Round Robin Assignment.
Specify the Rule name and Description.
Select when the rule should be executed: Ticket Create, Ticket Update, or both.
Click Add target and do the following:
Specify the Criteria for the rule.
Select the round-robin method: Load balancing, Sequential, or Skill-based.
Under Assign To, select agents or teams.
Check Exclude agents from this assignment, if required, then select the agent.
Click Save.
Setting up round robin preferences
The preferences allow you to set further criteria for the assignment rules:
Assign tickets to offline agents
By default, only agents who are online on the email channel are assigned tickets. Organizations can include the offline agents in the round-robin queue to manage various tickets.
Department-wise threshold
The total number of open tickets the agents in a department can have at any point will ensure a balanced approach.The admin can set a department-wise threshold for the tickets. For example, if the admin sets the threshold as 10 tickets for a department, then all the agents in that department will have only 10 open tickets, and the subsequent tickets will be assigned to the agent who has fewer than 10 tickets.
Agent level threshold
The admin can set a threshold for specific agents in specific departments. For example, if you want experienced agents to handle more tickets, then specify the agents' names and set a ticket count threshold such as 20 tickets.
Note
If both department and agent thresholds are defined, then the agent level threshold will take precedence, and the department wise threshold value will be overridden.
A maximum of 1500 agents can be assigned agent-level thresholds.
Assigning backlog
When the agents are offline or have reached the ticket threshold, tickets are held in the backlog. The backlog limit lets you decide the maximum number of backlog tickets that can be assigned to the agent in bulk. So, if the backlog limit is set to 10, each agent will be assigned 10 tickets from the backlog at a time. Once the department threshold limit is reached, no other tickets will be assigned.
Note
If ticket threshold is enabled, then the tickets from the backlog will also be assigned according to the threshold limits.
Incoming ticket assignment
When there are new incoming tickets, we have to ensure that it is assigned to the right agent for quick resolution. These new tickets can either be assigned to agents until they reach the threshold limit, or can be pushed into the backlog from which they are assigned. When the agent closes a few tickets, the new tickets will be assigned again based on the threshold limit.
On the Round Robin page, click the More icon ( ) in the top-right corner.
In the Round Robin Preferences menu, do the following:
Toggle Assign tickets to offline agents.
Toggle Department-wise threshold and select a value from the drop-down.
Toggle Agent Level Threshold. Enter the names of the specific agents you want to set a threshold for and select a ticket count from the drop-down.
Click + to add multiple rows.
Toggle Assign Backlogs and select a value for the Backlog Limit and the choose Assign Based on Due Date or Created Time.
Click Apply to set the preferences.
Reordering round-robin rules and targets
When there are multiple rules and targets, the system will check the criteria for the first rule and target in the order they are listed. By default, the rules are listed in chronological order, with the first rule created at the top of the list. If a ticket meets the criteria of more than one rule entry, it will enter the first rule that it matches.
To reorder rules and targets
In the Round Robin page, the rules for the department will be listed.
Hover on a rule and click the Reorder icon ( ) corresponding to it.
Drag and drop the rules on the order that you want.
Click Save order.
Deactivating round robin rules
You can deactivate the rules that are not used anymore. If you enable the rule again, the targets will remain unchanged. Deactivated rules are listed under the Inactive list.
To deactivate a rule
In the Assignment Rules page, click Round Robin from the left panel.
In the Round Robin page, hover your mouse pointer and click the Deactivate icon ( ) corresponding to the rule. Click the Activate icon ( ) to reactivate an inactive rule.
To disable all rules
In the Assignment Rules page, click Round Robin from the left panel.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
Install the PageSense code snippet on your site in a matter of minutes and start collecting in-depth data about the website visitors to grow your business.
Set up goals in PageSense to measure every single action performed by visitors on your website like button or link clicks, form submissions, and page engagements.
Create funnels in PageSense to quickly see which pages visitors use to enter your website, where they navigate to next, and which pages they decide to leave without converting.
Visualize your visitor's behavior with color codes
Set up heatmaps in PageSense to see where users have clicked more, how far they've scrolled, and on which parts of a page they've spent the most time using color-coded patterns in reports.
Use form analytics in PageSense to see how people interact with different fields in your form, whether they complete the form successfully or not, and where exactly they drop out on your form.
Use session recordings in PageSense to watch a video of all the visitor actions performed on your website including the pages they navigate, the buttons they click, the UX issues they face, and more.
Run A/B or Split URL tests in PageSense to figure out which version of your web page works best for your business and results in the best conversion rate.
Use personalization in PageSense to deliver customized versions of your website for every individual customer based on their demographics, local weather, browsing history, and more.
Run polls on your website using PageSense to understand what your customers think about your products/services and what needs improvement on your site.
Use web push notifications in PageSense to schedule and notify your customers about an upcoming flash sale, product releases, promotional coupons, and a lot more that can spark conversions on your website.
Use pop-ups in PageSense to instantly grab the attention of visitors by showing attractive signup offers, coupon code discounts, or email newsletters that can eventually convert them into subscribers.
Use PageSense's advanced features like creating mutually exclusive groups, enabling cross-domain tracking, configuring customized project JS, and more to get deeper insights about your website.
Download the PageSense extension app available for your web browser with a few clicks and start collecting all of your required website metrics in real time.
Discover your favorite integrations with PageSense
Get a deeper look at your website's data by seamlessly integrating PageSense with a host of popular third-party apps like Google Analytics, Mixpanel, Intercom, and more.
As a B2C, your customer support team may be directly involved with resolving customer questions, or you may be bound by the contract to extend support services to other businesses as a service provider. In either case, the key factors that determine ...
Skill-based ticket routing is an advanced routing strategy that routes tickets to customer support agents who are best qualified to reply to the incoming tickets. It works by matching the skills required to answer a ticket with those assigned to the ...
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 ...
Assigning tickets to the correct agent results in a faster response from the right person. To accomplish this, you need to know which agents are available, so you can assign tickets to agents who can provide the right response immediately. You also ...
What are Tickets Tabs in Zoho Desk? Tickets Tabs in Zoho Desk are designed to organize and provide contextual information about support tickets within the help desk system. These tabs enable users to connect tickets with other standard modules of ...