Queued Callback and Voicemail
Automate agent callback requests from customers
This solution features sample code that is provided “as is” and is not production grade. The featured code does not account for edge case handling, scalability, and reliability. It is not covered under Twilio's Service Level Agreement (SLA) and support plans.
This solution supports Flex applications that can handle upto 1 call per second. We do not recommend this solution if your contact center exceeds that limit as you will run into API limits enforced by TaskRouter.
The Queued Callback and Voicemail for Flex solution helps Flex admins automate handling of agent callback requests from customers instead of having them wait longer in a queue. In this solution, the customer hears the callback menu options as soon as they call the number provisioned on your Flex application. Your contact center agents will receive the details including the requested callback number, and a localized time for the customer's inbound call.
The call is on hold for the period of time that you've configured within queue-menu.protected.js. When the time period expires, it will go on and route according to the workflow configuration.
Architecture
User leaving a voicemail message or requesting a callback from an agent
Agent calling the user
This solution leverages Twilio Studio and Twilio Functions & Assets (Serverless) to give the customer options to register for a callback or leave a voicemail. When the customer decides on:
- Registering for a callback
- A new Callback task is created in TaskRouter
- The task is routed to the same workflow that the originating call was on, which means that it follows the same logic of routing calls to agents as the originating call placed by the customer
- Leaving a voicemail message
- Limitation: 20-30 second audio recording and transcription
- After the agent gives the customer a callback (3 attempts), they get the option to delete the recording
Prerequisites
To deploy this solution, you will need:
- An active Twilio account with Flex provisioned. Refer to the Flex Quickstart to create one.
- npm version 6.0.0 or higher (type
npm -v
in your terminal to check) - A Node.js long-term-support (LTS) version installed, 14 recommended (type
node -v
in your terminal to check) - Native Dialpad configured on your Flex application
- Twilio CLI along with the Flex CLI Plugin and the Serverless Plugin. Run the following commands to install them:
# Install the Twilio CLI npm install twilio-cli@2.0 -g # Install the Serverless and Flex as Plugins twilio plugins:install @twilio-labs/plugin-serverless twilio plugins:install @twilio-labs/plugin-flex
If you're running Linux, click on the Linux tab for the Twilio CLI installation instructions. If you're running Windows, make sure to run the Windows command prompt as an administrator to install the Serverles/Flex plugins for the Twilio CLI. The Windows commands in this guide use PowerShell (for Node.js/npm installation).
To provision Twilio resources and deploy this solution using a script, skip to the download step. After installing the dependencies, run node provision
and follow the instructions.
Make sure to activate the correct Twilio account before deploying the Flex plugin.
After the script is complete, enable the plugin on your Flex application.
Deployment Time
30-45 minutes
Tested Flex Versions and Operating Systems
- Flex v1.18.1 - 1.30.1
- macOS / Unix
- Windows 10
Configure your Flex Workspace
In order to use the solution, you need to prepare your Flex Task Assignment workspace.
Retrieve your Flex settings
Step 1
Navigate to your Flex project in the Twilio Console. Copy your ACCOUNT SID and AUTH TOKEN, and create a new Twilio CLI profile using those credentials:
twilio profiles:create
You will be prompted to enter your Twilio Account SID, Auth Token, and a shorthand identifier for your profile. When choosing a shorthand identifier, pick one that is meaningful and easy to remember. Once your profile has been created, activate it by running:
twilio profiles:use <profile_name>
Keep in mind that this account will be used for the rest of the deployment. In order to switch accounts, use the following command:
twilio profiles:use <different_profile>
Step 2
Retrieve your Flex Task Assignment workspace ID:
twilio api:taskrouter:v1:workspaces:list
Example Workspace SID
SID Friendly Name Prioritize Queue Order WSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Flex Task Assignment FIFO
To retrieve your Flex workspace SID from the Twilio Console, navigate to the TaskRouter Dashboard.
Step 3
In the Twilio Console, select your Flex project and navigate to All Products & Services > TaskRouter > Workspaces > Flex Task Assignment > TaskChannels. Create two task channels: one for callback and one for voicemail, so you can route the associated tasks to available agents.
Make sure the unique names are set to "callback" and "voicemail". Also, before you proceed to the next step, note that this solution is for use cases that may see up to 1,000 callback requests and voicemails queued at any given time. If you require more than that, please contact our Professional Services team to work with you on the appropriate architecture design.
Step 4
Create a task queue for callback and voicemail tasks named CallbackandVoicemailQueue. Make sure to pass 1==0
as the queue expression. This effectively “queues” callback and voicemail tasks.
Step 5
Create workflow filters for each callback attempt. In this guide, we will modify the "Assign To Anyone" workflow and configure three filters. Run the following command in a command shell:
-
For each filter, replace the
queue
fields in the JSON configuration with the SIDs of the "Callback and Voicemail" queue and the "Everyone" queue. - Pass the "Assign to Anyone" workflow SID to the
--sid
CLI flag. -
Also set the default queue to the SID of the "Everyone" Queue. Replace the
--workspace-sid
value in the API request with your Flex Task Assignment workspace.
CONFIGURATION=$(cat << EOF
{
"task_routing": {
"filters": [
{
"filter_friendly_name": "Attempt 1",
"expression": "(taskType=='callback' OR taskType=='voicemail') AND placeCallRetry==1",
"targets": [
{
"queue": "WQXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"timeout": 10
},
{
"queue": "WQYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
}
]
},
{
"filter_friendly_name": "Attempt 2",
"expression": "(taskType=='callback' OR taskType=='voicemail') AND placeCallRetry==2",
"targets": [
{
"queue": "WQXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"timeout": 20
},
{
"queue": "WQYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
}
]
},
{
"filter_friendly_name": "Attempt 3",
"expression": "(taskType=='callback' OR taskType=='voicemail') AND placeCallRetry==3",
"targets": [
{
"queue": "WQXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"timeout": 30
},
{
"queue": "WQYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
}
]
}
],
"default_filter": {
"queue": "WQYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
}
}
}
EOF
)
twilio api:taskrouter:v1:workspaces:workflows:update --sid="WWXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" --workspace-sid="WSyyyy" --configuration "$CONFIGURATION"
First, set your required Queue SIDs, your Flex workspace SID, and your "Assign to Anyone" workflow SID as environment variables.
set QUEUESID1=WQXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
set QUEUESID2=WQYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
set WORKSPACESID=WSYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
set WORKFLOWSID=WWXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
To confirm that an environment variable has been set, run echo %ENVVAR%
.
twilio api:taskrouter:v1:workspaces:workflows:update --sid=%WORKFLOWSID% --workspace-sid=%WORKSPACESID% --configuration="{ ""task_routing"": { ""filters"": [ { ""filter_friendly_name"": ""Attempt 1"", ""expression"": ""(taskType=='callback' OR taskType=='voicemail') AND placeCallRetry==1"", ""targets"": [ { ""queue"": ""%QUEUESID1%"", ""timeout"": 10 }, { ""queue"": ""%QUEUESID2%"" } ] }, { ""filter_friendly_name"": ""Attempt 2"", ""expression"": ""(taskType=='callback' OR taskType=='voicemail') AND placeCallRetry==2"", ""targets"": [ { ""queue"": ""%QUEUESID1%"", ""timeout"": 20 }, { ""queue"": ""%QUEUESID2%"" } ] }, { ""filter_friendly_name"": ""Attempt 3"", ""expression"": ""(taskType=='callback' OR taskType=='voicemail') AND placeCallRetry==3"", ""targets"": [ { ""queue"": ""%QUEUESID1%"", ""timeout"": 30 }, { ""queue"": ""%QUEUESID2%"" } ] } ], ""default_filter"": { ""queue"": ""%QUEUESID2%"" } }}"
Example API Response
SID Friendly Name Document Content Type WWXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Assign to Anyone null
To learn about configuring more complex workflows, see Create a Workflow Resource and Configuring Workflows: Complex Routing Example.
Download the Flex Queued Callbacks and Voicemail Plugin
Step 1: In your browser, download the plugin source code and unzip the files in a local directory.
Step 2: Run npm install
to install the plugin package dependencies.
Deploy your Twilio Functions and Assets
We will deploy the functions associated with the Callback and Voicemail Flex plugin to your Flex application. The functions are called from the plugin you will deploy in the next step and integrate with TaskRouter, passing in required attributes to generate the callback and voicemail tasks, depending on the customer selection while listening to the in-queue menu options.
Pre-deployment Steps
Step 1: From the root directory of your copy of the source code, change into serverless and rename .env.example
to .env
.
cd serverless && mv .env.example .env
C:\Users\xxxxxx\plugin-queued-callbacks-and-voicemail-main> cd serverless && move .env.example .env
Output
1 file(s) moved.
Step 2: Open .env
with your text editor and modify TWILIO_WORKSPACE_SID
with your Flex Task Assignment SID.
TWILIO_WORKSPACE_SID=WSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Step 3: Run npm install
to install your Serverless dependencies.
To deploy your Callback and Voicemail functions and assets, run the following:
serverless $ twilio serverless:deploy --assets
When running on Windows, you may see an error with the Twilio Serverless deployment command. To work around the issue, set your TWILO_ACCOUNT_SID
and TWILO_AUTH_TOKEN
as environment variables. Refer to the previous section for examples of how to set an environment variable in Windows.
Example Output
Deploying functions & assets to the Twilio Runtime Env Variables ⠇ Creating 4 Functions ✔ Serverless project successfully deployed Deployment Details Domain: https://plugin-queued-callbacks-voicemail-functions-xxx-dev.twil.io Service: plugin-queued-callbacks-voicemail-functions Functions: https://plugin-queued-callbacks-voicemail-functions-xxx-dev.twil.io/inqueue-callback https://plugin-queued-callbacks-voicemail-functions-xxx-dev.twil.io/inqueue-utils https://plugin-queued-callbacks-voicemail-functions-xxx-dev.twil.io/queue-menu https://plugin-queued-callbacks-voicemail-functions-xxx-dev.twil.io/inqueue-voicemail Assets: https://plugin-queued-callbacks-voicemail-functions-xxx-dev.twil.io/assets/alertTone.mp3 https://plugin-queued-callbacks-voicemail-functions-xxx-dev.twil.io/assets/guitar_music.mp3
Copy and save the domain returned when you deploy a function. You will need it in the next step.
If you forget to copy the domain, you can also find it by navigating to Functions > API in the Twilio Console.
Debugging Tip: Pass the -l
or logging flag to review deployment logs. For example, you can pass -l debug
to turn on debugging logs.
Create a Studio Flow
Step 1: With your Flex project selected, navigate to the Studio Dashboard.
Step 2: Click "+" to create a new flow. Give it a friendly name. For example, "CallbackVoicemailFlow".
Step 3: Select "Start from scratch".
Step 4: Drag and drop "Send To Flex" from the Widget Library on the right corner of the screen.
Step 5: Connect it with the "Incoming Call" trigger.
Step 6: In the Config tab, enter the following details:
- Widget Name: Friendly name for your Send To Flex widget
- Workflow: Assign to Anyone
- Channel: Voice
- Attributes:
{ "type": "inbound", "name": "{{trigger.call.From}}", "direction": "inbound" }
- URL Method: POST
- Hold Music TwiML URL:
https://<deployment-domain-name>/queue-menu?mode=main
(Replace with the value you saved from the Functions and Assets deployment step)
Step 7: Click Save and Publish to apply your changes.
Associate Incoming Calls with Studio Flow
Step 1: Navigate to the Phone Numbers page in the Twilio Console and click on the number associated with your Flex application.
Step 2: Scroll down to the "Voice" section and update the incoming call trigger with the Studio Flow that you created.
Step 3: Click Save.
Deploy your Flex Plugin
Once you have deployed the function, it is time to deploy the plugin to your Flex application.
Run the following commands in the plugin root directory. We will leverage the Twilio CLI to build and deploy the Plugin. First, rename .env.example
to .env
.
plugin-queued-callbacks-and-voicemail $ mv .env.example .env
C:\Users\mbermudez\plugin-queued-callbacks-and-voicemail-main>move .env.example .env
Output
1 file(s) moved.
Open .env
with your text editor and modify the REACT_APP_SERVICE_BASE_URL
property to the Domain name you copied in the previous step. Make sure to prefix it with "https://".
# .env REACT_APP_SERVICE_BASE_URL=https://plugin-queued-callbacks-voicemail-functions-xxx-dev.twil.io
When you are ready to deploy the plugin, run the following in a command shell:
plugin-queued-callbacks-and-voicemail $ twilio flex:plugins:deploy --major --changelog "Change plugin to use the latest Flex plugin for the Twilio CLI" --description "Queued Callback and Voicemail Plugin"
Example Deployment Output
✔ Validating deployment of plugin plugin-queued-callbacks-and-voicemail ⠧ Compiling a production build of plugin-queued-callbacks-and-voicemail ✔ Compiling a production build of plugin-queued-callbacks-and-voicemail ✔ Uploading plugin-queued-callbacks-and-voicemail ✔ Registering plugin plugin-queued-callbacks-and-voicemail with Plugins API ✔ Registering version v1.0.0 with Plugins API 🚀 Plugin (private) plugin-queued-callbacks-and-voicemail@1.0.0 was successfully deployed using Plugins API Next Steps: Run $ twilio flex:plugins:release --plugin plugin-queued-callbacks-and-voicemail@1.0.0 --name "Autogenerated Release 1602189036080" --description "The description of this Flex Plugin Configuration" to enable this plugin on your Flex application
Enable the Plugin on your Flex application
The previous step only deploys your plugin. You still need to enable the Plugin on your Flex application. To enable, run the following:
twilio flex:plugins:release --plugin plugin-queued-callbacks-and-voicemail@1.0.0 --name "Queued Callback and Voicemail" --description "Enabling queued callback and voicemail using Solution Guide"
View plugin on the Plugins Dashboard
After running the suggested next step, navigate to the Plugins Dashboard to review your recently deployed plugin and confirm that it’s enabled for your contact center.
You are all set to test Queued Callback and Voicemail on your Flex application!
Keep in mind that your Agents need to refresh their browsers in order to get the latest changes.
Testing the solution
Step 1: Log in as an admin to the Flex instance where you deployed the plugin.
Step 2: Change your status to Available on the upper right corner of the Flex UI. This enables you to receive incoming calls and messages (SMS or chat).
Step 3: Call the number displayed on the landing page of your Flex application.
Step 4: Press "1" to listen to the menu options:
Press "1" again to remain in the queue.
Press "2" to receive a callback. Follow the callback number confirmation prompt.
Press "3" to leave a voicemail for the agent. Follow the prompt and leave your voicemail message. Press *
when you're done. Note that your voicemail will be transcribed up to 30 seconds.
Step 5: When choosing the "callback" option, a preview callback task pops up on the Agent Desktop after the configured "timeout" setting in your workflow filter. In this example, we set it to 10 seconds.
- Accept the task. Upon accepting the task, the agent should see an Info panel with all the callback details as shown in the following image:
-
The agent can either place the callback immediately or forward the call to a queue of other agents.
-
After wrapping up the call with the customer, the agent should also complete the callback task.
Step 6: When choosing the "voicemail" option, a preview voicemail task pops up on the Agent Desktop after the configured "timeout" setting in your workflow filter. In this example, we set it to 10 seconds.
- Accept the task. On accepting the task, the agent should see an Info panel with all the voicemail audio and text transcription as shown in the following image:
-
Similar to the callback task, the agent can either place the callback immediately or forward the call to a queue of other agents. After the third requeue attempt, you then have the option to delete the recording.
-
After wrapping up the call with the customer, the agent should also complete the voicemail task.
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.