Inbound Routing Strategies /Automatic Call Distributor

overview the automatic call distributor (acd) is an intelligent mechanism designed to streamline high volume inbound processes its primary function is to route incoming calls to the most suitable agent who can address the caller’s specific needs appropriately by eliminating the dependence on traditional pbx systems and manual intervention, the acd ensures smooth call routing, reduces call abandonment, and optimizes resource utilization robust routing capabilities (in voice campaign) the acd system offers flexible algorithms that can be customized based on crm data, ivr selection, business hours, and agent skills the core routing strategies include 1\ docid 8x80nkr36a lgs11ueu13 this logic connects callers to the best suited agent based on the agent's specific skills and level of expertise benefit ensures agents only handle queries within their purview, reducing frustration and improving resolution quality use cases/example language based skill routing when a customer chooses a preferred language (for example, english or spanish), the system routes the call to the available agent with the highest skill rating in that language lower rated agents receive calls only when higher skilled agents are busy, ensuring better call outcomes and efficient use of agent capacity multi skilled agent priority if an agent has multiple language skills but is stronger in one (for example, spanish over english), the system prioritizes routing calls that match their strongest skill the agent will handle other skill queues only when there are no pending calls in their primary skill, or when doing so is necessary to meet sla commitments 2\ queue based routing queue based routing focuses on routing calls to queues (teams) based on queue level priority instead of individual agent skills queues typically represent different groups, such as senior vs junior agents or separate departments how it works you create different queues (e g , "expert team," "general support") and assign them priority levels the system offers calls to the highest priority queue first best for managing tiered support teams or specialized departments example a call is first routed to the "senior agents queue" (priority 1) to ensure high quality resolution if all senior agents are busy, the call automatically overflows to the "general support queue" (priority 2) to minimize wait times 3 preferred agent routing often referred to as "sticky agent" logic, this routes the caller to the specific agent they spoke with previously configuration the system checks for interactions within a configurable amount of time to ensure continuity 4\ priority based routing a priority based routing in a voice call campaign is based upon the priority given to the calls initiated by the customers it means that the calls which are more important for the business gets priority and answered first than to the calls with less priority best for prioritizing high value calls or urgent inquiries how it works priority is assigned to the call itself based on the customer type or the ivr selection (e g , sales vs support) higher priority calls jump ahead of lower priority calls in the waiting line example a "sales" call (priority 1) will be answered before a "general inquiry" call (priority 2), even if the general inquiry caller has been waiting longer this ensures revenue generating or critical calls are never delayed 5\ run time queue changes design workflows that seamlessly route a caller from one queue to another user experience the transfer happens without any break or additional wait time for the caller operational advantages implementing an intelligent acd mechanism addresses common challenges such as frequent transfers, long hold times, and scalability restrictions increased agent productivity reduced aht agents handle calls they are specifically trained for and have subject knowledge on, which significantly reduces average handling time (aht) effective utilization prevents ineffective resource utilization by matching demand with the right supply of skills improved first call resolution (fcr) accuracy routing to the right agent ensures a faster and more accurate response efficiency higher fcr is achieved by removing the need to transfer calls between different departments streamlined operations & scalability integration the system supports easy integration to enable call conferencing and transfers with real time customer data instant scalability there is no requirement for additional hardware or it involvement to scale up or down instantly (up to a certain limit of call volume) reduced costs by achieving higher fcr and reducing transfer times, overall call center costs are reduced how to do routing in a voice campaign (from administrator interface) here, you can create and manage the routing for both inbound and outbound calls in interactive voice application campaign, outbound campaign, and parallel predictive campaign routing for inbound add a nodeflow for routing perform the following steps to create a nodeflow click "add" button to create a nodeflow it shows a new row in the white area just below the column header provide a name for the context flow in "node flow name" column, you have to upload either a nodeflow or anfx flow service engineer will provide you the required nodeflow files click "browse" to open a nodeflow file select the location where the file stored select the required file and click "open" check "transferable" if you want to transfer the call from this nodeflow to another nodeflow click "apply" to add the nodeflow assign nodeflow to a queue perform the following steps to assign a nodeflow to a queue in the campaign check the box to select a queue click "assignment" to assign this nodeflow to a queue it shows the following pop up select "acd" node in "available acd node" section, and click icon select the nodeflow in "assigned acd node" section in "queue" drop down menu, select the queue to which you want to assign this ndoeflow click "save" to assign the nodeflow to the selected queue it takes you back to "routing" tab you can perform the same steps to create the nodeflow and to assign it to a queue you can fetch a nodeflow and download it as a file on the disk, assign or unassign it to a queue, and delete the nodeflow delete routing policy select the routing policy for which you want to delete permanently click "delete" button a confirmation pop up comes up click "yes" if you want to delete the routing policy, else click "no" routing for outbound in "outbound feature context" section, perform the following steps click "add" to add a routing policy for the outbound feature context it creates a new row in the blank area select any of the following policy types basic single call context type it is the policy type in which outbound calls will be dialed out from the single call context phone based call context type it is the policy type in which administrator can define the pattern on basis of which numbers will be dialed out from multiple call context it will only reflect after procuring appropriate licenses basic multiple call context type (licensable) it is the policy type in which outbound calls will be dialed out from multiple call context it will only reflect after procuring appropriate licenses multiple type round robin call context type it is the policy in which if a call tried by a call context fails to get connected, then it will be tried by the different call contexts that are selected for calling as per round robin algorithm as per round robin algorithm, each call context is used to call for a fixed amount of time and if the call does not get connected in that duration, another call context is used the left over call context is reused when all other call contexts in the loop are used and the call is still not connected make sure to not provide a name for the routing for any "outbound feature context" the name will be assigned automatically after selecting the call contexts the outbound routing with manual names will not work click "assign" link under "assignment" header to select a call context that you have assigned in this campaign in "call context" tab following pop up is displayed for "basic single call context type" on the page for "phone based call type", "basic multiple call context type", and "multiple type round robin call context type", the following pop up appears to select the multiple call contexts perform the following steps to assign call contexts to this new policy select the call contexts in "available" section click icon to proceed to assign the selected call contexts click "save" to assign the call contexts to this campaign rather, you can click "cancel" to not assign the call contexts to unassign a call context, click the link under "assign" header for a new or existing outbound routing policy, select a call context in "assigned call contexts" section, click icon, and click "save" to unassign the selected call context from the campaign click "save" to proceed to add the selected context to the routing policy click "apply" to create the routing plan for outbound you can create multiple routing policies for the outbound feature in the interactive voice application (inbound) campaign you can only change the selected call contexts while modifying an outbound routing policy in addition to that, you can also delete a routing policy delete routing policy select the routing policy for which you want to delete permanently click "delete" button a confirmation pop up comes up click "yes" if you want to delete the routing policy, else click "no" saving routing test result when an administrator creates a routing test case, they may want to check that test case frequently so that any issues in the routing can be figured out easily allowing the administrator to save these test results saves an enormous amount of time for them on the routing test screen, the administrator can save the test cases the saved test cases are listed on the same screen administrator can also perform the following actions delete a test case or select multiple test cases and delete them search for a test case select the test case(s) they want to run edit a test case