Have you ever been disconnected from a support call while being transferred to someone else?
Warm transfer eliminates this problem. Using Twilio powered warm transfers your agents will have the ability to dial in another agent in real-time.
Here is how it works at a high level:
- The first agent becomes available when he/she connects through the web client.
- The second agent also becomes available when he/she connects through the web client.
- A client calls our support line.
- The client stays on hold while the first agent joins the call.
- While the first agent is on the phone with the client, he/she can dial a second agent into the call.
- Once the second agent is on the call, the first one can disconnect from it. The client and the second agent stay on the call.
Let's get started! Clone the sample application from Github, and click the button below to begin.
First let's configure the voice webhook for the Twilio number that customers will dial when they want to talk to a support agent.
This action method is the one that ASP.NET framework will generate to the public-facing URL.
Awesome, now you've got a webhook in place. Next up, we'll look at some of the code.
Here you can see all front-end code necessary to connect an agent using Twilio's Voice Web Client.
We essentially need three things to have a live web client:
- A capability token (provided by our ASP.NET MVC app)
- A unique identifier (string) for each agent
- Event listeners to handle different Twilio-triggered events
In the next step we'll take a closer look at capability token generation.
Next up, let's see how to handle incoming calls.
For this tutorial we used fixed identifier strings like
agent2 but you can use any generated strings for your call center clients. These identifiers will be used to create outbound calls to the specified agent using the Twilio REST API.
When a client makes a call to our Twilio number the application receives a POST request asking for instructions. We'll use TwiML to instruct the client to join a conference room and the Twilio REST API client to start a call with the first agent, this way he will be able to join the same conference.
When providing instructions to the client, we also provide a
waitUrl. This URL is another end point of our application, it returns more TwiML to say welcome to the user and also play some music while on hold. Take a look at the
We use the client's
callSid as the conference identifier. Since all the participants need this identifier to join the conference we'll need to store it in a database so that we can grab it when we dial the second agent in.
Now let's see how to provide TwiML instructions to the client.
Next up, we will look at how to dial our first agent into the call.
For our app we created a
CallCreator class to handle dialing our agents. This class uses Twilio's REST API to create a new call. The
InitiateOutboundCall method receives the following parameters:
from: Your Twilio number
to: The agent web client's identifier (
url: A URL to ask for TwiML instructions when the call connects
Once the agent answers the call in the web client, a request is made to the callback URL instructing the agent's call to join the conference room where the client is already waiting.
With that in mind, let's see how to add the second agent to the call.
When the client and the first agent are both in the call, we are ready to perform a warm transfer to a second agent. The first agent makes a request passing its
identifier that allows us to look for the
call.ConferenceId needed to dial the second agent in. Since we already have a
CallCreator class we can simply use the
CallAgent method to connect the second agent in.
Next up, we'll look at how to handle the first agent leaving the call.
When the three participants have joined the same call, the first agent has served his purpose. Now he can drop the call, leaving agent two and the client to have a pleasant conversation.
It is important to notice the differences between the TwiML each one of the participants received when joining the call. Both, agent one and two, have
startConferenceOnEnter set to
true. This means the conference will start when any of them joins the call. For the client calling and for agent two,
endConferenceOnExit is set to true. This causes the call to end when either one of these two participants drops the call.
That's it! We have just implemented warm transfers using ASP.NET MVC. Now your clients won't get disconnect from support calls while they are been transferred to some else.
If you're a ASP.NET MVC developer working with Twilio, you might also enjoy these tutorials:
Learn how to use Twilio Client to make browser-to-phone and browser-to-browser calls with ease.
Learn how to implement ETA Notifications using ASP.NET MVC and Twilio.
Thanks for checking this tutorial out! Let us know on Twitter what you've built... or what you're building.