Your business number may sit on your agency's account, not yours. Here is how to check, what to put in the contract, and how to move it if you leave.
Short answer: It depends on which account the number was bought in and who pays the bill. If the number sits in a sub-account billed to your agency, the agency controls it and you need their help to move it. If it sits in an account you own, or in a Twilio account opened in your name, you keep it when you leave. Find out which setup you have before you sign anything and before you end anything.
Prefer to watch? The 42-second version
If your agency bought your GoHighLevel number, they may control it. Here is how to find out before it becomes a problem.
Watch it on its own page, with the transcript.
A number bought through GoHighLevel's built-in phone system belongs to one sub-account, and the calls and texts on it are billed to that sub-account's wallet. Nothing on the screen says "owner". In practice the owner is whoever controls that sub-account and whoever's card funds the wallet.
That is the part that surprises people. A small agency builds the whole system: the website, the missed call text back, the reminders, the number. The business owner uses it every day and never opens the billing page. A year later they want to leave, and the number on their trucks, their Google profile and their invoices turns out to sit in an account they cannot log into.
This question showed up in the GoHighLevel community on Reddit this week, asked by someone thinking it through from the agency side (the thread is here). The workflows were the easy part of the question. The number was the one that worried people.
| Setup | Who controls it | What leaving looks like |
|---|---|---|
| Client's own sub-account, client's card on the wallet, agency added as a user | The client | The client removes the agency user. Nothing moves. |
| Agency's sub-account, billed to the agency and rebilled to the client | The agency | The client needs the agency to cooperate on a port or transfer. Timing is in the agency's hands. |
| Twilio account opened in the client's name, connected to GoHighLevel | The client, through Twilio | The client keeps the number and reconnects it elsewhere. See our article on running GoHighLevel with your own Twilio account. |
| Existing number that stays with your current carrier, with texting handled by HighLevel | The client, through the carrier | The number never left. See how hosted numbers work. |
Neither of the two agency-friendly setups is wrong. Rebilling is how many agencies run their business, and it is convenient. The risk is not the arrangement itself. It is that nobody wrote down what happens at the end.
Workflows can be rebuilt. A snapshot copies pipelines, workflows, forms and pages into a new account, and if the agency is helpful you can have a working copy in a day or two. Contacts can be exported to a spreadsheet. A phone number is different: it is printed on vans, listed on directories, saved in your customers' phones, and tied to your Google Business Profile.
It is also tied to your text registration. Under A2P 10DLC, US carriers expect the business sending texts to be registered, and the registration covers the brand and the campaign that uses your numbers. If the agency registered under its own company details, your texting rests on their paperwork. If you moved the number and had to register again, you would be waiting for approval while texts were blocked. We walk through that process in our A2P 10DLC approval guide. This is practical guidance, not legal advice.
You do not need to be technical or suspicious to ask these. A good agency will answer them in one email.
Ask for the answers in writing, then ask that the same points be added to your agreement. If the agency hesitates on question four, that is useful information too.
We would not promise a one-click transfer. Moving a number between accounts or providers is a port or a support request, and the timing depends on the carriers involved. Ask HighLevel support what the process is for your specific number type before you set a date.
The safe order is the same either way. Keep the old setup running. Stand up the new account with workflows, forms and calendars, and test it with a different number first. Confirm the move on the carrier side, then switch the workflows over on the day, not before. If the new setup also needs a text registration, start that early, because approval is the slowest step.
The mistake we see is cancelling the old account the same week the new one goes live. When the number sits in the old account, cancelling can take the number with it. Do not cancel anything until you have a confirmed copy of the number working where you want it.
Putting the number in the client's name protects you as much as it protects them. Nobody can accuse you of holding anything hostage, and a departing client takes a clean exit instead of a dispute. It also fits the broader handoff problem we wrote about in how to stop clients from breaking workflows after handoff. If you run an agency, our agency page covers how we set these accounts up for partners.
The practical version: new clients get a number in a sub-account that bills to them, or on their own Twilio account, with you as an admin user. Existing clients get a short email asking to confirm where the number sits. If you rebill for convenience, say so in the agreement and say what the exit process is.
We would start by listing every number, who pays for it, which sub-account it sits in and whose name is on the text registration. That inventory takes minutes and tells you whether you have a problem. If the account was inherited or built by someone who is no longer around, our GoHighLevel account audit covers that along with the rest of the account, starting at $497.
Yaakov (Koby) Oranski, Founder and CEO of Yotomations
Certified GoHighLevel Admin and Partner. Koby designs CRM migrations, two-way integrations, billing systems and AI agents for service businesses, and writes from the engagements described on this site.
It can if the number sits in an account the agency owns and pays for, and your contract does not say otherwise. Most agencies do not do this on purpose, but the control exists. Ask in writing which account holds the number and what the handoff process is.
Ask whoever set it up to show you the number under Phone Numbers in the sub-account settings, and ask who pays the wallet that funds it. If you have your own login to that sub-account as an admin and your card funds it, you are probably in good shape. If you cannot log in at all, assume the agency holds it.
Numbers can generally be ported, but the process, timing and rules depend on the number type and the carriers involved. Ask HighLevel support what their port-out process is for your specific number before you commit to a date. Keep the old setup running until the new one is confirmed.
Registration is tied to the business details submitted and to the number and campaign it covers. If the registration was filed under your company, your records stay yours. If it was filed under the agency, plan to register again under your own details. This is practical guidance, not legal advice.
It is one clean way to make ownership obvious, because the numbers live in an account in your name. It adds a vendor and a bill to manage. We cover the tradeoffs in our article on running GoHighLevel with your own Twilio account.
You cannot write one GoHighLevel workflow at the agency level and have it run for every client. Here is the pattern we use today, the risks, and what to retire if it ships.
Learn moreA client asks for something GoHighLevel can't do. Sort the request into four buckets before you say yes, then build it outside GHL and price it as fixed scope.
Learn more
The question that keeps SaaS founders up at night: you have 50 or 100 sub-accounts on one master snapshot and need to ship an update. A versioning and rollout process that does not break every account.
Learn moreBook a 30-minute call. We look at the account live and tell you what is broken, what we would fix first and what it would cost.
No pitch deck. We look at your current setup and tell you what we would do and what it would cost.Need more than GoHighLevel? Yotomations, our parent company, also builds AI agents, custom software and websites.
