- Scenario Builder Reference Guide Introduction
- Scenario Builder OverviewExercises
- Scenario-Building ExercisesScenario Blocks Definitions
- Scenario BlocksReference
- Scenario Reference Material
- Add to Calling List
- Ask a Bot
- Attached Data
- AWS Lambda
- Bright Pattern Create Object
- Bright Pattern Delete Object
- Bright Pattern Search Object
- Bright Pattern Update Object
- Chat Bot Select Account
- Collect Digits
- Connect Call
- Connect Chat
- DB Execute
- Exception Handler
- External Transfer Call
- Fetch URL
- Find Agent
- Get Agent State
- Get Next Record
- Get Statistics
- Get User Configuration
- Identify Contact
- Internal Message
- Microsoft Dynamics Create Object
- Microsoft Dynamics Delete Object
- Microsoft Dynamics Screen Pop
- Microsoft Dynamics Search Object
- Microsoft Dynamics Select Account
- Microsoft Dynamics Update Object
- 1.1 How It Works
- 1.2 Properties
- 1.3 Conditional Exits
- 1.4 Recommended Reading
- Play Prompt
- Request Callback
- Request Input
- Request Skill or Service
- Retrieve Internal Record
- RightNow Create Object
- RightNow Screen Pop
- RightNow Search
- RightNow Select Account
- RightNow Update
- Salesforce.com Delete
- Salesforce.com Insert
- Salesforce.com Screenpop
- Salesforce.com Search
- Salesforce.com Select Account
- Salesforce.com Update
- Save Survey Response
- Search Directory
- Self-Service Provided
- Send Message
- ServiceNow Create Object
- ServiceNow Screen Pop
- ServiceNow Search
- ServiceNow Select Account
- ServiceNow Update Object
- Set Agent State
- Set Case
- Set Custom Reporting Field
- Set Disposition
- Set Priority
- Set Prompt Language
- Set Variable
- Start Another Scenario
- Stop Prompt
- Web Screen Pop
- Zendesk API Request
- Zendesk Create Object
- Zendesk Screen Pop
- Zendesk Search
- Zendesk Select Account
- Zendesk Update Object
The Play-Listen scenario block is a key part of Bright Pattern's conversational IVR. The block enables natural conversation in an automated scenario, using the combination of integrated text-to-speech and speech-to-text technologies, along with integrated chatbots, to "talk" to customers on inbound voice calls and "listen" for their spoken or DTMF (i.e., touch tones) response.
(Note that for scenarios in which input from the caller is expected in response to a prompt, use the Menu block.)
How It Works
On a call, if the Play-Listen block detects that the caller is talking or entering touch tones on the phone, the voice prompt will stop playing, and one of the following will happen:
- If a DTMF key is detected, the DTMF exit will be taken, leaving the key in the buffer for subsequent DTMF blocks.
- If there is no change in voice detection, the Play-Listen block will take the Timeout exit.
- If a vocal change is detected, the caller's voice data will be fed into the selected transcriber (see below) until the voice changes back to a lower level. The transcription result will be saved into the specified recognized phrase variable (see below) and the Play-Listen block will take the normal exit.
In this block's properties, you will configure Play-Listen to play a voice prompt for the caller, collect the caller's spoken response or DTMF response, offer bot suggestions to the caller, and route the caller if the block fails.
Prompt to play
This is the prompt that the scenario will play to the caller.
The Play-Listen block uses text-to-speech technology to convert bot response text into speech in a specified language. The prompt will sound like a robot. You have the option to record your own voice segment and upload it to the Prompts list as a .WAV file.
Learn more about managing prompts in this guide's section, Voice Prompts.
Allow interrupting prompt by customer voice
When this checkbox is enabled, if the Play-Listen block detects that a caller is talking while the configured prompt is playing, the prompt will be interrupted. Note that this setting is unchecked by default.
The transcriber is the Speech-to-Text (STT) engine that takes the caller's vocal response and converts it to text, thus producing a text transcription of whatever was spoken.
Select the STT integration account that has been configured for your contact center.
The recognized phrase uses a variable to represent whatever the customer says. In this field, enter the variable that receives the caller's spoken "phrase" (e.g., "user_phrase" or "bot_phrase").
The variable name can be anything you want, as long as you use the same variable name consistently in your scenario. The variable/recognized phrase is set using the Set Variable block.
Confidence indicates the speech-to-text service's confidence in its identification of the speakers and the words that are spoken. In this field, confidence is represented by a variable that receives the confidence value from your integrated speech-to-text engine.
As with the recognized phrase variable, you can enter any variable you want here (e.g., "cc"), as long as you use it consistently later.
Your STT engine conveys confidence as a numeric value, where the higher the number (e.g., "0.999") is, the more confident the STT engine is that it has recognized vocals correctly. A low number (e.g., "0.001") shows that the engine has very low confidence in its vocal recognition. For example, if the customer says, "I need a new phone," and the engine hears, "I need a sea foam," the confidence will be likely very low. If confidence is low, the scenario can escalate the call to a real agent.
The default value is 20 seconds. When the max timeout is reached, the scenario will exit the Play-Listen block using the Timeout conditional exit (see below).
The scenario can exit the Play-Listen block through the DTMF exit, Failed exit, or Timeout exit.
Dual-tone multi-frequency (DTMF) refers to telephone touch-tones. If the Play-Listen block detects that the caller is transmitting numeric information (numbers from 0 to 9, as well as symbols # and *) on the phone, it will take the DTMF exit, running through the scenario as specified.
To define what the scenario will do once the exit is triggered, drag a scenario block over to the DTMF exit.
In the example shown above, when the DTMF exit is triggered, an internal message is sent to a specified agent, so that the agent knows that touch-tone information was provided via the IVR. Then, the scenario uses the Goto block to go to the Find Agent block.
The Failed exit is taken when the Play-Listen block has delivered the prompt but has failed to collect a response from the caller.
To define what the scenario will do once the exit is triggered, drag a scenario block over to the Failed exit.
In the example shown above, when the Failed exit is triggered, an internal message is sent to a specified agent, so that the agent knows that conversational IVR didn't get a response from the caller. Then, the scenario uses the Goto block to go to the Find Agent block.
If the Play-Listen block does not detect any changes in vocal input or if the call is silent, the block will take the Timeout exit.
Explore Bright Pattern's tutorials to learn more about how to use the Play-Listen block: