Normalize telephone numbers
Twilio's APIs consistently use the E.164 standard for phone numbers. This format is fine within your code, but it presents a couple of user-facing issues:
- E.164 is difficult to understand when presented as plain text, such as in an SMS
- When read aloud by a Twilio Say verb or Say Widget, numbers such as
+15095550100will be read literally as a large number, instead of digit-by-digit. (ex. "Plus fifteen billion, ninety-five million, five hundred fifty thousand, one hundred")
Fortunately, Twilio Lookup enables you to convert a given E.164 phone number into the national format used by that country, which Twilio will read aloud as one would normally say it in their region.
To get started, use the following instructions to create a Function to host your code.
Before you run any of the examples on this page, create a Function and paste the example code into it. You can create a Function in the Twilio Console or by using the Serverless Toolkit.
If you prefer a UI-driven approach, complete these steps in the Twilio Console:
- Log in to the Twilio Console and navigate to Develop > Functions & Assets. If you're using the legacy Console, open the Functions tab.
- Functions are contained within Services. Click Create Service to create a new Service.
- Click Add + and select Add Function from the dropdown.
- The Console creates a new protected Function that you can rename. The filename becomes the URL path of the Function.
- Copy one of the example code snippets from this page and paste the code into your newly created Function. You can switch examples by using the dropdown menu in the code rail.
- Click Save.
- Click Deploy All to build and deploy the Function. After deployment, you can access your Function at
https://<service-name>-<random-characters>-<optional-domain-suffix>.twil.io/<function-path>
For example:test-function-3548.twil.io/hello-world.
You can now invoke your Function with HTTP requests, configure it as the webhook for a Twilio phone number, call it from a Twilio Studio Run Function Widget, and more.
The following Function is one which will tell the user their phone number, in the format that they would expect in normal conversation. This will also work for international phone numbers!
To verify this for yourself, paste the code into the Function that you just made, and set it as the A Call Comes In webhook handler for the Twilio phone number you wish to test. The following instructions will show you how to do so.
1exports.handler = async (context, event, callback) => {2// The pre-initialized Twilio client is available from the `context` object3const client = context.getTwilioClient();4// Create a new voice response object5const twiml = new Twilio.twiml.VoiceResponse();67// The From value is provided by Twilio to this webhook Function, and contains the caller's8// phone number in E.164 format, ex. '+15095550100'9const from = event.From;1011// Call Twilio Lookup to get information about the number, including its national format12const result = await client.lookups.phoneNumbers(from).fetch();1314// Read back the caller's phone number in the way it would normally spoken, not as a15// massive integer!16twiml.say(`Your phone number is ${result.nationalFormat}`);17return callback(null, twiml);18};
For your Function to react to incoming SMS or voice calls, it must be set as a webhook for your Twilio number. There are a variety of methods to set a Function as a webhook:
Use the Twilio Console UI to connect your Function as a webhook:
- Go to Products & Services > Numbers & Senders > Phone Numbers.
- Select the phone number you'd like to connect to your Function.
- Go to the Configuration Details tab.
- To configure Messaging, choose Edit details in the Messaging section.
- To configure Voice calls, choose Edit details in the Voice and emergency calling section.
- Select the webhook method and provide your webhook URL. Select an HTTP method to handle responses.
- Optional: Configure a secondary webhook in case the primary webhook fails.
- Click the Save button.
This functionality also lends itself well to Studio Flows, where you may share a phone number as part of your IVR. The Say widget doesn't natively read E.164 formatted numbers in the national format, but clever use of the Run Function widget with the following sample code will enable this.
First, create a new Studio Flow. We suggest following the Create Your Flow directions from a Studio tutorial.
Once you have created a Flow, drag a Run Function and a Say/Play widget onto the Studio canvas. Connect the Incoming Call trigger to the Run Function widget by dragging from the trigger to on top of the widget, and similarly connect the Run Function widget's "Success" condition to the Say/Play widget.
With the widgets connected, the next step is to configure them.
Click on the Run Function widget, which should cause the Widget Library to show the configuration options for the widget. Name the widget as you like, and use the drop-down menus to select the Service and path of the Function that you created previously. To wrap up the configuration, click Add under Function Parameters, set the "Key" to From, and "Value" to {{contact.channel.address}}. This will cause the phone number of the incoming caller to be passed to the Function as a parameter called From.
Your configuration and connections should look similar to this:

Following a similar process, configure the Say/Play widget with your desired name, and paste the following into the "Text to Say" field:
Hi! Your phone number is {{widgets.<widget-name>.parsed.normalizedPhoneNumber}}.
Replace <widget-name> with the name of your Run Function widget. This means the Say/Play widget will access the results of the Run Function widget, retrieve a value named normalizedPhoneNumber, and will attempt to read it back to the caller. You can read here to get more context around the parsed property.
Click Publish to publish your Studio Flow.
With the Studio Flow published and expecting new behavior from your Function, it will need some slight modifications.
Edit or replace the body of your Function with the following sample code. Note that it is returning the normalizedPhoneNumber that is expected by the Say/Play widget.
With your code changes complete, save and deploy your Function.
Provides readable phone numbers to Studio Flows
1exports.handler = async (context, event, callback) => {2// The pre-initialized Twilio client is available from the `context` object3const client = context.getTwilioClient();4// The From value should be provided as a parameter by the Run Function widget, and contains5// the caller's phone number in E.164 format, ex. '+15095550100'6const from = event.From;78// Call Twilio Lookup to get information about the number, including its national format9const result = await client.lookups.phoneNumbers(from).fetch();1011// Return the caller's phone number in the way it would normally spoken12// Access this in a Studio Flow with `{{widgets.<widget-name>.parsed.normalizedPhoneNumber}}`13return callback(null, {14normalizedPhoneNumber: result.nationalFormat,15});16};
To test your Flow, connect your Twilio phone number to the Studio Flow.
With your Twilio phone number connected to the Studio Flow, you can call your Twilio phone number and have a synthesized voice read out the number you are calling from in a human-friendly manner.

