- Scenario Builder Reference Guide Introduction
- Scenario Builder OverviewExercises
- Scenario-Building ExercisesScenario Blocks Definitions
- Scenario BlocksReference
- Scenario Reference Material
- Scenario Builder Basics
- All Scenario Exercises
- Create a Basic Scenario
- Pop Case or Contact Information
- Chat Scenario That Uses Bots
- How to Configure a Chat Scenario That Uses a Microsoft Azure Web App Bot
- How to Blacklist Specific Phone Numbers
- Distribute Surveys to a Percentage of Random Customers
- How to Configure Last-Agent Routing Using the Internal Database
- Route Callers to the Last Agent and Provide a Voicemail Option
- 1.1 Prerequisites
- 1.2 Scenario Flow
- 1.2.1 Action 1: "Get user configuration" looks up the last known agent
- 1.2.2 Action 2: Exception Handler's "Try" exit tells the scenario what might generate an exception
- 1.2.3 Action 3: The Exception Handler's "Catch" exit tells the scenario which blocks to use if an exception occurs
- 1.2.4 Action 4: "Exit" ends the scenario
- 1.2.5 Action 5: Save your scenario
- 1.3 Final Step: Enable service continuation
- 1.4 Related Information
- Sending Automatic Email Replies to Customers Who Use the "Leave a Message" Chat Form
- Skill-Based Call Routing with an Auto Attendant Choice
- Voice Scenario Survey
- Use Conversational IVR in a Scenario
- Scenario Example
- Downloadable Scenario Templates
How to Route Callers to the Last Agent and Provide a Voicemail Option
So your customer is calling again and wants to talk to the last known agent who helped her. How do you connect them?
This article will show you how to create a general voice scenario that
- Finds the last known agent (also called same agent routing)
- Connects the call to that agent or presents an IVR menu with the option to either leave a voicemail or look for the next available agent
For instructions on how to import this file into your contact center, see the Contact Center Administrator Guide, section Scenarios Overview > How to Export and Import Scenarios.
Scenarios are made up of scenario blocks that specify how interactions are processed. Detailed descriptions of Bright Pattern scenario blocks are available in this guide's Scenario Block Definitions section.
The following sequence of actions illustrates one way to organize scenario blocks to route a customer to either the last known agent, an IVR menu with the option to leave a voicemail for that agent, or to the next available agent.
Please note this is an example scenario only and not intended for production use. All conditional exits should be defined with actions for production use.
Action 1: "Get user configuration" looks up the last known agent
The Get user configuration block finds a specific contact center user and returns the user ID of the last known agent, using variable "lastagent."
Action 2: Exception Handler's "Try" exit tells the scenario what might generate an exception
Under Exception Handler's "Try" exit, you should enter the sequence of blocks that you predict might generate an exception, block error, or disconnect. In this example, we did so in the following order.
Find Agent looks for the last known agent.
In Find Agent properties, you must also use a "Specific agent" condition to specify which agent needs to be found.
- Under "Agent skills required," click add Interval.
- Under "Conditions," click add.
- From the drop-down menu, select Specific agent.
- In the variable value field, enter
variable $(item.continuationUserId). This variable is used to pull the last known agent's user ID when service continuation is enabled for your contact center. See the Final Step of this procedure for more information.
Play Prompt plays the voicemail option voice segment to the caller (e.g., "To leave a voicemail press 1, to speak with an agent now, press 2").
Menu specifies the two available IVR menu options as given in the Play Prompt block (i.e., 1 for voicemail, and 2 for finding an agent).
Voicemail tells the system how to encode the voicemail recording, who to deliver it to, and so forth.
Goto jumps to "Find Agent."
Action 3: The Exception Handler's "Catch" exit tells the scenario which blocks to use if an exception occurs
After defining the possible blocks that might start an exception, you work on the Catch exit.
Under Exception Handler's "Catch" exit, you should enter the sequence of blocks that you want the scenario to execute if an exception, block error, or disconnect occurs during the Try conditional exit. In this example, we did so in the following order.
Connect Call connects the customer to the last agent.
Find Agent finds the next available skilled agent (not the last known agent). There are no special conditions to add in this Find Agent block.
Action 4: "Exit" ends the scenario
The Exit block completes the scenario. Without it, the scenario will loop through this configured flow until the customer ends the call.
Action 5: Save your scenario
Be sure to save the scenario with a new name. Closing the browser tab or window will cancel out your work.
Final Step: Enable service continuation
Now that you have completed your scenario, you need to enable service continuation. This allows your contact center system to return an identified contact (i.e., your caller) to the same agent who last helped the caller.
- In the Contact Center Administrator application, go to Call Center configuration > Identification.
- Enable Enable Service continuation for up to __ hours and specify the number of hours.
For more information, see the Contact Center Administrator Guide, section Identification.
Note: It is possible to route additional interaction types from a customer to an agent during an active interaction (e.g., a caller sends an SMS to an agent during the same interaction) using the Find Agent block's wait condition Agent currently handling this interaction.