overview intelligent routing offers administrators of servicely a means to automatically route tickets to agents within assignment groups based on pre defined logic intelligent routing rules can be created to automatically assign tickets using a number of different routing rules, including active ticket count performs round robin balancing of tickets up to a specified cap or limit ticket priority volumes balances tickets based on priority across pre specified caps or limits time since last assignment continually balances tickets based on the time since last assignment for a given user static routing always routes tickets directly to a specified individual custom routing allows administrators to define their own routing rules and logic using servicely’s scripting elements intelligent routing supports additional configuration options to provide flexible and dynamic routing of tickets, including assignment assignability support servicely user records include a selectable for assignment flag that can be taken into consideration when performing intelligent routing this ensures that only users that can be assigned tickets participate in intelligent routing, allowing for managers to live within groups for reporting, or agent leave/shifts to be taken into consideration configuring assignability intelligent routing can take into consideration the availability of a user when performing intelligent routing this allows for intelligent rules to ignore users who are (for example) on leave, or are working on projects and should not be a part of the core routability this assignability is also critical for team leaders, who live within their assignment groups, but should not be a part of the day to day routing of tickets on the user table, users can manage the selectable for assignment field in conjunction with the respect assignment selectabiltiy field on the intelligent routing rule \ title intelligent routing \## do not modify the theme variables config theme base themevariables primarycolor '#afd3f0' secondarycolor 'white' \ flowchart lr classdef portal fill #fdaa43 classdef subcat fill #02012d, color white rule(rule condition met) > order(evaluate order) > assignability(respect assignability?) assignability "no" > assignall(assign to any user) assignability "yes" > assignselect(assign only to selecatable users) assignall > assignticket(ticket assigned based on rule) assignselect > assignticket support for all work types when configuring an intelligent routing rule, administrators can specify any work type, including it service management tickets (request, incident, change, problem, etc ), hr cases, customer service management cases, and more this includes custom work types created for bespoke applications, provided they are extended from the out of the box work table work journal stamps intelligent routing leaves notes in the work journal of routed tickets to provide context into how the record was assigned to the group, ensuring that there is no confusion as to the path of escalation performed automatically dynamic record filtering intelligent routing rules can apply to all records assigned to a specific group, however additional filters can be applied to ensure that only specific records are routed using a particular rule this, in conjunction with the ability to order routing rules for execution, allows for multiple rules to be configured for a specific group for flexible and dynamic routing when to use intelligent routing intelligent routing is best used in conjunction with sofi’s intelligent classification to direct newly created tickets that have been assigned to specific groups to users directly, bypassing the need for queue managers or triage units primary use cases for intelligent routing include balancing new/incoming tickets across a large pool of possible assignees to ensure equalised assignment using time since last assignment routing rules assigning tickets for particular business services directly to subject matter experts within an assignment group automatically using static routing ensuring high priority tickets are never left unassigned by automatically assigning them using ticket priority volumes setting up intelligent routing to enable intelligent routing on your instance, you must first ensure that you’re on a supported version of servicely intelligent routing is available in all instances of servicely running v 1 10 66+ you can confirm your version of servicely by hovering over the logo in the top right corner of your instance’s homepage if the version is blank, or reads less than v1 10 66, please engage your administrator or servicely support to upgrade to a supported version installing intelligent routing as with all new features of servicely, installation and configuration should be performed in a non production instance the intelligent routing application can be installed by platform administrators by navigating to the applications list by searching for applications in the left hand navigation, and selecting the appropriate menu item find the intelligent routing application, and perform the installation once installed, a new menu item will be created under intelligent automations → intelligent routing that allows administrators to set up and configure routing rules finally, a platform wide system property is created that enables or disables intelligent routing across the instance by default, this property is disabled to ensure no disruption to services will establishing and configuring routing rules to enable intelligent routing, navigate to the system intelligent routing auto routing enabled application property record and set the application property value to true configuring intelligent routing rules creating or configuring intelligent routing rules can be done via the intelligent automations → intelligent routing menu item by administrators of the platform follow the steps below to create a new intelligent routing rule create a new intelligent routing rule by navigating to the intelligent automations → intelligent routing menu item, and from the list, select the new button to create the rule provide a name and short description for the routing rule this ensures clear readability and understanding for future configuration set the active state of the rule to true to ensure the rule functions as intended specify an order for the rule to be executed in this is only required if there is an explicit order that rules must be evaluated within e g , two rules for the same assignment group one that performs active ticket routing to a cap, and then statically assigns all extras to a queue manager specify the table and assignment group to apply the rule to e g , our routing rule may wish to handle all incoming incidents for the service desk assignment group select the appropriate routing rule, and perform any rule specific configuration as required determine if the rule should respect the assignment selectability of the user this is especially useful when managing large teams with follow the sun shifts or other support arrangements finally, specify the condition (if any) that must be true for the rule to take effect e g , we only want incidents with a short description that contains “ urgent ” to be included in our routing once complete, save the record and test the configuration if intelligent routing is configured correctly, work journal entries should be created whenever the intelligent routing is performed