Introducing Trestle Reverse Phone Twilio Add-On

Trestle focuses on providing identity data for caller identification, call routing, and lead verification/append use cases. Part of fulfilling this mission is to provide the data where the integration is the easiest for our customers. In that regard, Twilio is one of the biggest CPaaS platforms out there, used by millions of developers and thousands of enterprises for everything related to telephony communication. Naturally, it was our first priority to enable Twilio’s customers to access this data for better call identification, routing, and prioritization decisions for incoming customers and prospects. 

Today, we are proud to announce that we now have the Trestle Reverse Phone Add-On available for Twilio and its customers. The Add-On can be found here. 

The Trestle Reverse Phone Add-On provides the following data:

Trestle Attribute Categories:	Description:	How to Leverage the Data:
Phone Metadata	Validity, ported carrier, line type, is prepaid, etc.	Not only does this data help to weed out bad leads, but it also helps with lead prioritization. For example, businesses might want to prioritize a call from Verizon Wireless higher than a call from a burner phone or Google Voice number.
Phone Subscriber(s)	Who does this phone belong to? In the case of family plans, additional owners associated with this phone are also provided in the associated_people attribute, categorized as ‘PotentialOwner’.	This data can be used for caller identification, cross-check with the existing CRM databases, and for incoming leads so the appended information can help handle the leads better resulting in higher conversions.
Phone Subscriber Demographics	Age and gender of the subscriber	This demographic data can further help with lead prioritization or call routing.
Address history of the phone subscriber	The current address of the subscriber along with their previous address history.	This data helps call centers to route the call from a national phone number to local agents. More on this can be found here.
Associated people of the phone subscriber	Associated people living in the same household, as well as relatives.	Businesses can leverage this data to deduce the marital status, as well as other people living in the household that can help pitch appropriate products to the lead.
Phone subscriber alternate phones	Additional phones, including mobile numbers.	Businesses can leverage these additional contact points for better contactability and conversions.

For customers migrating from Ekata to the Trestle Add-On, the migration is pretty straightforward. Please see the documentation tab, which describes the process in which you can migrate services before the shut-off date. 

A few questions I am sure the audience will have:

Is the data being returned the same as Ekata?

Yes, and it’s actually better, both coverage and accuracy-wise. Trestle will be 3-5% points additional coverage on the name front. On the full address front associated with the phone, the coverage will be 8-10% higher. The accuracy of the name returned is also higher. More on it can be found here. 

Does the API response remain the same? What work is involved in parsing the new response?

Once the Add-On is installed, the API response mapping remains exactly the same as Ekata, so developers do not have to do any additional work to get this data integrated within their existing systems. Everything  should continue to work as-is. You are just calling the Trestle endpoint instead of Ekata going forward.

Is the pricing the same?

As you can see on the Add-on page, it is exactly the same price as Ekata Reverse Phone Add-On. 

Tell me more about this team?

Read through our founding story blog, and it will give you a good idea of who we are and what we do at Trestle.

We are incredibly excited about how our customers use this data and what new use cases it can enable. If we can help brainstorm on the use cases or even help with the transition, please reach out to me at kshah [at] trestleiq [dot] com.