Local IVR

overview a "local ivr" is a full fledged interactive voice response (ivr) system that runs locally within a campaign's context while a standard ivr typically handles incoming customer calls before they reach an agent, a local ivr is often used during an active call agents can conference a customer into a local ivr to automate specific processes, capture sensitive data, or collect post call feedback without disconnecting the line interactive voice response (ivr) is an automated system that allows customers to interact with a contact center using their telephone keypad (dtmf tones) note local ivr is a licensable feature ensure you have procured the appropriate license to view and use this tab in your campaign settings business use cases secure data collection (automated payments) an agent conferences a customer into a secure local ivr to enter credit card details or pins the information entered via dtmf tones is processed by the system and is not visible to the agent , ensuring pci compliance and security customer verification agents can route a caller to an ivr to verify their account number or identity before proceeding with a sensitive transaction self service providing customers with options to check account balances or track an order automatically how it works a call is directed to a pre configured call flow (nodeflow) the ivr plays audio prompts (e g , "press 1 for sales"), and the customer's key press determines the next step, such as transferring to a queue or another ivr menu agents can also conference a customer into a local ivr for assisted processes prerequisites licensing this is a licensed feature and requires the appropriate license component to be procured and visible in the campaign settings campaign assignment must be configured within the interactive voice application campaign settings (inbound campaign) call context the local ivr must be associated with a call context that has been assigned to the campaign nodeflow a nodeflow must be designed by professional services team as per the business requirement configuration steps administrator/voice admin configuration "local ivr" tab in interactive voice application campaign settings lets the administrator create the local ivrs add a local ivr perform the following steps to add a local ivr click "add" to add a local ivr using the following pop up provide a name for the new ivr "call context" drop down menu lists all call contexts that you have assigned to this campaign select anyone of them select "override source phone" option to override the source number (from which a call is being received) of the incoming call with the provided number after checking it, provide a number in its relevant textbox select "override destination phone" option to override the destination number (to which a call is being dialled) of the outbound call with the provided number after checking it, provide a number in its relevant textbox provide a description in "description" text box click "apply" to create the local ivr using the selected call context rather you can click "cancel" to not create it you can follow these steps to create multiple local ivrs modifying an ivr perform the following steps to modify an existing local ivr in the campaign settings in "local ivr" tab, select a local ivr to view its details in the right panel you can change the following fields while modifying a local ivr name call context enable or disable the option to override the source phone already provided source phone number enable or disable the option to override the destination phone already provided destination phone number description if the system level call routing plan is created based upon the call context, source phone number, or destination phone number, then call routing will not work for this ivr if you change any of these fields if the campaign level call routing feature is created based upon the call context, then the call routing will not work for this ivr if you change the call context validate the changes carefully as the call routing can be disabled for this local ivr if any change is made to call context, source phone, or destination phone click "apply" to apply the changes rather, you can click "cancel" to discard the changes delete an existing local ivr the deleted local ivr will not be played at the assigned call context feature, source phone number, or destination phone number the deleted local ivr cannot be restored using any method sometimes an existing local ivr becomes obsolete and it has to be replaced with an all new ivr if you are planning to delete an ivr, then you have to plan properly before going ahead as the deleted ivr will not be played in the call flow perform the following steps to delete a local ivr in "local ivr" tab, select a local ivr to view its details in the right panel click "delete" button in the top right section it shows the following warning message click "yes" to delete the local ivr rather, you can click "no" to not delete the local ivr defining the call context at the system level or campaign level scenario 1 system level call routing for ivr you have to define the call routing at the system level if any of the following conditions is true system level (or contact center level) call context has been selected to add the local ivr source phone is specified to add the local ivr destination phone is specified to add the local ivr refer to " docid 7d egijs 7zn6v swcxtp " page to know about the steps to create a call routing plan scenario 2 campaign level call routing for ivr you have to define the call routing in "call routing" tab of campaign settings only if the above conditions specified for system level routing are not true the call context, which is used to add the local ivr, have to be used to create a context feature in "call routing" of campaign settings refer to " docid\ smyfpd zz hp9fgaz1c47 " page to know the steps to create a call routing in the campaign settings how call routing works with local ivr? call routing means that a call is being moved from an endpoint to another the decisions in the call routing can be made using many reasons sucha as caller identification, dialed number, time of day, and custom defined parameters established in an ivr (interactive voice response) program script in exotel cc, we use term profiles for different routing sequence currently, the following three types of profiles are being used source based destination based call context based important point the contact center system supports more than one "conferwithivr" profiles to serve different types of call conferences as per the different business requirements benefits increased operational efficiency automates routine inquiries, freeing up agents for more complex interactions improved customer experience empowers customers with self service options and ensures they are quickly directed to the right department 24/7 availability provides basic support and information to customers even outside of normal business hours limitations local ivr is not supported for outbound campaigns agents can only conference a customer with a local ivr; they cannot perform a direct transfer to it