GoHighLevel Clean-Up for Mortgage Teams: Phone Numbers, Pipelines and Inactive Users

A phone number sitting in the wrong GoHighLevel sub-account does quiet damage. Calls get logged in the wrong place, leads route to the wrong person, and the team's numbers stop meaning anything. On one mortgage team we found that, plus duplicate pipelines, inactive users and a text automation sending the wrong message.

This story is about the owner of a mortgage brokerage and a related real estate business group, who asked for a full clean-up of the GoHighLevel setup. Below is what we found, what we changed and a short check you can run on your own account. For more on how we work with lenders, see our page for mortgage loan officers.

The situation

The business ran GoHighLevel across four related sub-accounts. Over time, users, phone numbers and pipelines had been added in each one without a common plan. The owner wanted a clean setup before the team started KPI tracking, because you cannot measure follow-up on a system nobody can read.

We worked out the new structure in one working session, around a single routing logic.

What was broken

Six problems, each one hiding the others.

Duplicate and irrelevant pipelines confused users and obscured the actual lead flow. Phone numbers were sitting in the wrong sub-accounts, so call data was captured in the wrong place and leads routed incorrectly. One user lost ownership visibility on his own leads when his account was briefly removed during the consolidation. A text automation was sending messages that led with the wrong loan program to one loan officer's leads. There was no call recording, so the team could not track follow-up cadence, response times or outcomes. And inactive users cluttered every account, which made it hard to see who was actually using the system and which numbers were in use.

A smaller finding mattered too. Calls from one of the related businesses were landing on one team member's line and were judged the lowest-value calls on the system. Where a number sits decides who gets those calls.

What we built

We reorganized the sub-accounts, the user assignments, the phone numbers and the pipelines together, since each one depends on the others. The structure was agreed on the call. Most of the hands-on moves below were assigned to be finished by the end of that week, so read them as the agreed work and not as a finished state.

• Phone numbers were moved and forwarded so each number sits in the sub-account that should capture its call data and route its leads.
• Pipelines were standardized, with the duplicate and irrelevant ones cleaned out, and a standard lending pipeline was built for the non-QM leads.
• Ownership and filters were restored for the user who lost visibility of his leads, and he was asked to confirm his access afterward.
• The text automations were fixed and reactivated with the correct messaging.
• A call-recording and transcription tool was to be set up, so calls could be reviewed for follow-up cadence, response times and outcomes.
• Follow-up service levels and a daily KPI reporting framework were defined.
• Inactive users were removed from the sub-accounts.
• All non-QM product leads were routed into one account for testing, with a reassignment review set for the following week.

What changed

No lead-volume or conversion figure came out of this call. The clean-up was a precondition for measuring anything.

The account is being organized the way the work flows. The plan puts each number where its calls should be captured, replaces the duplicates with one standard lending pipeline, leaves only people who use the system on the account and corrects the text automation. With call recording in place, the daily KPI report will have something to read: follow-up cadence, response time and outcome per call. Routing all the non-QM leads into one account for testing gives the team one controlled place to watch the flow before deciding who takes which leads.

Check your own account in ten minutes

List every phone number on your account and write down which sub-account holds it and which person's calls it should reach. Any number you cannot place in one line needs attention.

Then count your pipelines and ask what each one is for. If two share a purpose, merge them. Finally, list the users and remove anyone who has not logged in recently, after you confirm they are not needed. Do the user clean-up carefully, since removing an account can strip a person's view of their own leads.

Frequently asked questions

Why does phone number placement matter in GoHighLevel?

Number placement decides which sub-account captures the call data and which leads route to whom. A number in the wrong sub-account produces call records in the wrong place, which makes response times and ownership numbers unreliable.

What happens when a user account is removed from GoHighLevel?

In this case, a user lost ownership visibility on his leads when his account was briefly removed. The plan was to restore the owner filters and have him confirm his access. Before removing any user, check which leads and filters depend on that account.

Why add call recording before tracking KPIs?

Without recording, a team cannot see follow-up cadence, response times or outcomes. Recording and transcription give the daily KPI report real call data to read, and they give managers calls they can review and score together.

Why route all non-QM leads into one account for testing?

One account gives the team a single place to watch the lead flow and feel any friction before handing leads to individual loan officers. A reassignment review the following week then decides who takes which leads.

If you suspect your own numbers, pipelines and users have drifted apart, book a 30-minute AI follow-up and reporting audit. We review your GoHighLevel setup with you and list what to fix first.