Moving a Business Number Into GoHighLevel: A Remodeler's Plan After Missed Client Messages
By Alex Regueiro · November 9, 2026 · 5 min read
A remodeling owner had 60 unread messages waiting in a phone app that had never been opened on an actual phone. Client communications had been missed, and the branded business number lived outside the system the business was moving into.
60-second check
Take the 2-minute AI readiness survey →
Talk it through
Book a call with the Reshape team →
This is the story of a remodeling company that was moving its operations into GoHighLevel, and it applies to any of the home service businesses that still run their main phone line through a separate service.
The situation
The company already used GoHighLevel, but its branded business number sat with a legacy virtual phone service. Client messages came in there, so they never showed up next to the contacts and opportunities in the CRM.
On a working call with the owner, our goal was to close that gap and get the daily workflow into one place.
What was broken
Three things were wrong at once. The owner had never used the legacy phone app on a phone, so the unread messages piled up and clients went unanswered. The business number sat outside GoHighLevel, which left a tracking blind spot.
Third, useful connections were unused. The owner did not know a connector existed for the company's project-management tool, and the team talks constantly in Slack with no link to the CRM.
What we built
We worked through the connections and the data first, then set up the number move.
- Connected the project-management tool to GoHighLevel with an API token, and connected Slack.
- Re-audited all contact and opportunity records.
- Ran a live training exercise: we created an opportunity and booked an appointment in GoHighLevel together, as a hands-on walkthrough of the daily flow.
- Queued the next integration for the owner: connect the company's Google account and enable Google Business Profile call tracking, so the GoHighLevel dashboard can become the one central view.
- Turned on the full-address setting for calendar events. It only applies to future bookings, so existing events needed the address added by hand.
- Aligned on moving the branded business number from the legacy service into GoHighLevel, with coordinated transfer emails for both providers and a daily-use cheat sheet still to be drafted and sent, and a mobile walkthrough planned just before the transfer.
What changed
No result was reported yet, because the number had not been transferred when the call ended. The change is in how the system is meant to work: once the number moves, client communication is meant to land in GoHighLevel, next to the contact and opportunity records.
One more rule kept the move safe: the owner stays logged into the legacy phone app until the transfer is complete, so messages keep reaching the owner while the number is in motion.
Before you move a business number
If you are thinking about the same move, start by checking where your calls and texts actually land today. Open every app that can receive a client message and look for unread items. Then audit your contacts so the new home is clean.
Plan the transfer window, teach the mobile workflow before the switch, and keep the old app available until the transfer is confirmed. Test one call and one text afterward, and check that both appear on the right contact.
Frequently asked questions
Why move a business number into GoHighLevel?
When calls and texts arrive in a separate app, the CRM cannot show which ones became opportunities. The aim is to put every conversation on the contact record, which is meant to remove the tracking blind spot this company had.
What should you do before transferring a business phone number?
Audit your contacts and opportunities, draft the transfer requests for both providers, and walk the team through the mobile workflow. Keep the old app logged in until the transfer completes so messages are not missed.
Why did the full-address calendar setting not fix old events?
The setting applies only to future bookings. Events created before it was turned on need the address added manually, which is worth knowing before you promise a team that the change is retroactive.
How can a remodeler avoid missed client messages in a phone app?
Put every message channel where the team already works and make the mobile app part of training. In this case the owner had never opened the old app on a phone, so unread messages built up unseen.
If client messages are landing in apps your CRM cannot see, book a 30-minute AI follow-up and reporting audit. We map where every call and text arrives and show you what to move first.