Twilio Lookup allows you to get information about phone numbers programmatically. This information can include the name of the phone number's carrier, their type (landline, mobile, VoIP, etc.), the name of the caller, and far more than this example page can cover.
All this data can be indispensable in making your applications dynamic and able to handle different carriers. The following examples illustrate a small sample of what Lookup can enable in Twilio Functions, and we can't wait to see what else you will build.
To get started, use the following instructions to create a Function to host your code.
In order to run any of the following examples, you will first need to create a Function into which you can paste the example code. You can create a Function using the Twilio Console or the Serverless Toolkit as explained below:
If you prefer a UI-driven approach, creating and deploying a Function can be done entirely using the Twilio Console and the following steps:
https://<service-name>-<random-characters>-<optional-domain-suffix>.twil.io/<function-path>
test-function-3548.twil.io/hello-world
.
Your Function is now ready to be invoked by HTTP requests, set as the webhook of a Twilio phone number, invoked by a Twilio Studio Run Function Widget, and more!
The core functionality of Lookup is determining the carrier and type of a phone number. For example, the following Function code returns true for incoming calls from landline or mobile callers, and false for calls from VoIP callers. An application could use this information to filter out unsupported call types in a Studio Flow if called by a Run Function widget, or simply called as a REST API by your application.
_29exports.handler = async (context, event, callback) => {_29 // The pre-initialized Twilio client is available from the `context` object_29 const client = context.getTwilioClient();_29_29 // Grab the incoming phone number from a call/message webhook via event.From_29 // If invoked by a REST API call or Studio Run Function widget, it may be a_29 // parameter such as phoneNumber_29 // Example: https://x.x.x.x/<path>?phoneNumber=%2b15105550100_29 const phoneNumber = event.From || event.phoneNumber || '+15105550100';_29_29 try {_29 // Discover the phone number's carrier and type using the Lookup API with_29 // the `type: 'carrier'` argument_29 const result = await client.lookups_29 .phoneNumbers(phoneNumber)_29 .fetch({ type: 'carrier' });_29_29 console.log('Carrier name: ', result.carrier.name);_29 // 'Carrier name: AT&T'_29 console.log('Carrier type: ', result.carrier.type);_29 // 'Carrier type: mobile'_29_29 // Reject calls from VoIP numbers, and allow all others_29 return callback(null, result.carrier.type !== 'voip');_29 } catch (error) {_29 console.error(error);_29 return callback(error, null);_29 }_29};
Lookup can also retrieve the name of the individual or business associated with a phone number. Expanding on the previous example, convert the type
argument to an array, and add 'caller-name'
after 'carrier'
.
If available, the response will include a name for the phone number and whether the name is for a business
or consumer
.
Keep in mind that not all numbers will have names available.
You can then use this information to adjust application logic, format responses to use names to add personalization, and more.
For this example, the code attempts to format the caller's name and use it in a response, falling back to referencing the carrier name if the caller's name isn't accessible. To test this code out, paste the code into your existing Function, 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.
_47// lodash is a default dependency for deployed Functions, so it can be imported_47// with no changes on your end_47const { startCase } = require('lodash');_47_47exports.handler = async (context, event, callback) => {_47 // The pre-initialized Twilio client is available from the `context` object_47 const client = context.getTwilioClient();_47_47 // Grab the incoming phone number from a call webhook via event.From_47 const phoneNumber = event.From;_47_47 try {_47 // Create a new voice response object_47 const twiml = new Twilio.twiml.VoiceResponse();_47 // Discover the phone number's name (if possible) by converting type_47 // to an array and appending 'caller-name' to the type argument_47 const result = await client.lookups_47 .phoneNumbers(phoneNumber)_47 .fetch({ type: ['carrier', 'caller-name'] });_47_47 console.log('Carrier name: ', result.carrier.name);_47 // 'Carrier name: AT&T'_47 console.log('Carrier type: ', result.carrier.type);_47 // 'Carrier type: mobile'_47 console.log('Caller name: ', result.callerName.caller_name);_47 // 'Caller name: DOE,JOHN'_47 console.log('Caller type: ', result.callerName.caller_type);_47 // Caller type: CONSUMER'_47_47 if (result.callerName.caller_name) {_47 // Attempt to nicely format the users name in a response, if it exists_47 const [lastName, firstName] = result.callerName.caller_name_47 .toLowerCase()_47 .split(',');_47 const properName = startCase(`${firstName} ${lastName}`);_47 twiml.say(`Great to hear from you, ${properName}!`);_47 } else {_47 // If we don't have a name, fallback to reference the carrier instead_47 twiml.say(`We love hearing from ${result.carrier.name} customers!`);_47 }_47_47 return callback(null, twiml);_47 } catch (error) {_47 console.error(error);_47 return callback(error, null);_47 }_47};
In order for your Function to react to incoming SMS and/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, as detailed below:
You can use the Twilio Console UI as a straightforward way of connecting your Function as a webhook:
ui
unless you have created
custom domains
), and finally
Function Path
of your Function from the respective dropdown menus.