Click To Call with C# and ASP.NET MVC

Wish your users could get in touch as easily as they can surf? It's your lucky day!

Let's go over the steps necessary to implement click-to-call in a C# and ASP.NET MVC application.

1. A website visitor submits a web form with a phone number.
2. Your web application receives the submission and initiates an HTTP request to Twilio asking to initiate an outbound call.
3. Twilio receives the request and initiates a call to the user's phone number.
4. The user picks up the call.
5. After the call connects, we provide TwiML instructions to connect the user to our sales or support teams.

What We Will Learn

This tutorial demonstrates how to initialize a call using the Twilio REST API and how to create a call using the TwiML Say verb.

Let's get started! Click the button below to move to the next step of the tutorial.

Set up your environment

Before we create our click-to-call application we need to set up our environment first.

Let's put our Twilio credentials in a place where our application can access them. For the purposes of this tutorial, we'll store them in environment variables that our application can read. Create a Local.config file under the ClickToCall.Web/ directory with the following content:

<?xml version="1.0" encoding="utf-8"?>
  <appSettings>
    <add key="TwilioAccountSID" value="your_twilio_account_sid" />
    <add key="TwilioAuthToken" value="your_twilio_auth_token" />
    <add key="TwilioNumber" value="your_twilio_number" />
  </appSettings>

Replace the Account_SID, Auth_Token, and Twilio_Number placeholder values with your unique values, which you can find in the Twilio Console. You can use an existing Twilio phone number or obtain a new number.

Next, let's look at making a friendly web form.

The web form

For our solution, we'll need a form where the user can enter a phone number.

No need to overthink this step as the real goal is to POST the user's phone number to your controller.

What information does this form need?

• An input for the User's phone number
• An input for the sales team phone number
• A submit button

Since the page doesn't need to render new content after clicking, we decided to implement the POST action via AJAX using jQuery. Let's take a look at that code next.

Submit the form

To make the click to call feature more seamless we used Ajax to send the form asynchronously.

This code shows one way you could implement this functionality using jQuery:

• Watch for the user "submitting" the form element
• Submit the form's data to our controller
• Let the user know if the submission was successful or not

This is a common implementation of jQuery's jQuery.post() method. Notice that we are returning the response message when the call has connected.

Now that we have the front end done let's build the back end that will receive this data. We'll start our exploration in the next step.

Outbound call routing

Back on the server, we'll define a route that handles the HTTP POST requests to the /Call URL. This is the code that we're calling via our AJAX request in the browser. It will be responsible for placing the outbound call.

Before we place the call we first check that the POST data is valid, which requires that our CallViewModel has a user number and a sales number present.

Next, we'll use the REST API to make an outgoing phone call which requires we pass it a From number, a To number and the URL Parameter uriHandler that tells Twilio what to do after it connects the call to our customer.

Now let's look at how we prepare TwiML to send to Twilio.

Generate TwiML

TwiML is a set of verbs and nouns written in XML that Twilio reads as instructions.

In this case our instructions inform Twilio to SAY something to the user and then DIAL the support agent's number so the customer can talk to him or her.

We will use the Twilio .NET Helper Library to create a TwiML response.

The first thing we do is validate that the incoming request is coming from Twilio. For this we'll use a Twilio Validation Service implemented by us using the Twilio .NET Helper Library's RequestValidator class.

And with that, you've helped us get a working click-to-call form, ready to be integrated into your own application.

Test your app locally

Now you can run and test your Twilio app.

However, you probably want to test it using a publicly available endpoint without having to go "public" with your app. The best option is to use ngrok.

Note: For more information about running the application, see the Readme file in the app github repository.

About ngrok

ngrok generates a secure URL that forwards traffic to a port, usually 5000, on your localhost server. It allows you to run applications locally but make them a publicly available endpoint via secure tunneling. This allows you to test your application and do all the things you want your app to do but in a secure public space.

ngrok is an executable (ngrok.exe) that you run on the command line or terminal.

Setting Up ngrok

Head over to ngrok's website, download the ngrok.zip file for your OS of choice, then unzip the file into an easily accessible location.

For example, on Windows, you can place it in your \Users directory in \AppData\Roaming\<ngrok-directory-name>\ngrok.exe. Then, update your PATH environment variables to the location of the ngrok executable. On Linux or OSX, it's much easier (see the instructions on the ngrok site).

And that's it.

Accessing your app from an endpoint using ngrok

Before you start ngrok, it might be a good idea to have your Twilio Console open.

For Mac and Linux, open a terminal and run this command to start ngrok:

$ ./ngrok http 4040

On Windows, open a command prompt and run this command to start ngrok:

$ Path-to-ngrok> ngrok http 4040

Alternately, you can start ngrok using the following command:

$ ngrok http 4040 -host-header="localhost:4040"

The port number "4040" is arbitrary. If your local server is running on another port, replace "4040" in the command with the appropriate port number.

This will start ngrok. A running instance of ngrok will appear in the terminal showing the local web interface (in this case http://127.0.0.1:4040) and the public URL (in this case, https://28dd499b.ngrok.io).

The forwarding public URL needs to be set in the Twilio Console. In the Console, select the active phone number you set in Local.config and enter the public URL from ngrok (shown above) in the "A Call Comes In" field under Voice & Fax. Be sure to select Webhook from the dropdown list.

Remember, each time you run ngrok, a new public URL will be generated. You will need to set this new URL in the Console.

You now have a publicly available endpoint for your app, so now you can take a look at your running app and enter the phone numbers using your ngrok address: https://xxxxxx.ngrok.io

Where to Next?

• Check out how iAdvize uses Twilo click-to-call to connect to online shoppers with customer support representatives
• Appointment Reminders - automate the process of reaching out to your customers in advance of an upcoming appointment.
• Automated Survey - instantly collect structured data from your customers with a survey conducted over a voice call or SMS text messages.

Did this help?

Thanks for checking out this tutorial! Tweet to us @twilio and let us know what you're building!