The client initially reached out hoping to migrate from CallRail to CallTrackerFX but keep all of their relevant call tracking numbers (looking to cut unnecessary additional costs). Upon investigation, it was evident to me that their CallRail was super unorganized. On my end, I spent time breaking down call volume per phone number per 30 days to identify the numbers and channels that are most relevant as well as breaking down where these phone numbers are located. They had numbers labeled “MFG,” multiple PPC numbers for the same location, and outdated print ad campaigns, just to name a few. They had over 88 call tracking numbers within their CallRail. Additionally, call forwarding numbers were all over the place! They only have 4 locations, but they had over 13 forwarding numbers listed and active in their CallRail. We had to hop on multiple calls and loop in additional team members on their side to figure what their real/actual business line was.
Once we finalized plans, we went to port the numbers; however, it was initially rejected and required an additional form to be submitted for the port to go through!
We had multiple calls over nearly 3 months to get an action plan in place on what numbers we are porting, figuring out their business lines, finalizing plans, and agreeing upon the necessary add-ons to accomodate for an increased amount of call tracking numbers and call volume per month.
Now, we have a comprehensive call tracking setup that is simplified for their needs: SEO, Local SEO, PPC, Direct, Yelp, Social, and LSA for each location. It took us a long time to get here and a lot of communication, but I am super happy to have completed this for my client and successfully completed a porting process.
Cleaned up a very messy call tracking system and migrated the client over to our tool!
See this Guru on updated porting process documentation: https://app.getguru.com/card/TxqE7BBc/CallTrackerFX-Twilio-Number-Ports-Releasing-Numbers-Etc