Call Porting From Vonage to Twilio

Posted by: Macenzi Barker Date Posted: December 29, 2023
Back to Case Studies

Issue

This client is an upscale florist in NYC and saw the value of CallTrackerFX, but didn’t want to sacrifice their prestigious 212 Manhattan area code.

  • No 212 numbers were available in Twilio for purchase
  • The client explained that “Manhattanites want to do business with Manhattan businesses.”

The client had many old Verizon hunt group numbers that ring to the business by default, and maintained ownership of these numbers but no longer advertised them. I wasn’t sure if call porting was an option because these numbers would not be ported in from another call-tracking software and may require a different configuration, if they worked at all.

Solution

We worked with the client to obtain the necessary documents for the Twilio porting process (outlined in Guru) and were able to port the numbers in!

One issue remained – the data wasn’t populating in CallTrackerFX and calls weren’t being logged in Twilio’s call logs. After some troubleshooting, the team was able to identify the issue and update the “Caller Name Lookup” field, and that was the solution! The team has updated the documentation for any future use cases as well.

Calls are now logged in CallTrackerFX with attribution and the client gets to keep their reputable area code!

Achievement

The team was able to port in old Verizon hunt group numbers to Twilio for CallTrackerFX attribution, creating a win-win for our team and the client! The client gets to keep their Manhattan numbers, and we get to report on all of that great call data!