Who Actually Owns a Business Texting Number?
Control of a number, permission to transfer it, and contractual rights between an agency and client are separate questions. Start with the provider account and the service agreement. Record whose business is listed, who can request changes, and what the agreement says happens at termination. Paying the bill or using a number publicly should not be treated as conclusive proof of ownership. Ask the provider to confirm its requirements for that specific line before promising a transfer.
On Beam, dedicated business numbers are assigned to a workspace. Each client or reseller has a separate inbox, numbers, team, and CRM connection. See Getting your numbers for provisioning and Team and workspaces for those boundaries. The provisioning guide says a client owner normally signs in and pays directly, even when an agency created the workspace. That describes account operation; it does not establish a port-out entitlement or settle an agency-client ownership dispute.
What Does a Letter of Agency Actually Authorize During a Port?
A Letter of Agency (LOA) records authorization for a service change in processes that require one. It should identify the authorized customer and the requested change. Ask the receiving provider which documents and account details it needs, who must sign, and how it verifies authority. Do not assume that possession of a signed document alone guarantees a port or resolves conflicting claims between an agency and its client.
If the client also uses Apple Messages for Business, check that account separately. Apple’s business registration process uses an organization profile and a business Apple Account or Managed Apple Account. That documentation concerns Apple Messages for Business, not Beam’s device-based iMessage service. It does not establish a Beam registration requirement or promise that a messaging identity transfers with a telephone number.
How Can a Text-Enabled Toll-Free Number Transfer Be Challenged?
Somos publishes a dispute process for text-enabled toll-free numbers moved between Service Registrars in the TSSRegistry. The former registrar must provide an existing LOA for the help desk to continue the dispute. The current registrar must then provide a qualifying LOA, and the help desk gives precedence to the more recent LOA when reviewing both.
That is a specific text-enablement dispute procedure. It is not a general rule for local-number porting, a description of every toll-free voice transfer, or a ruling on the client’s contract rights. The practical lesson for an agency is narrower: retain authorization records and identify the provider process that actually applies to each number. Do not promise that the newest signature settles every disagreement.
Why Is a Client’s Storefront Number a Different Risk Than a Number the Agency Bought?
Not every number in an agency’s book has the same operational importance if a client leaves. A number printed on a client’s storefront sign, Google Business Profile, or invoices is part of how customers reach that business. Losing access could interrupt those conversations. Record where each number appears so the handoff plan reflects its use, even when the agency originally arranged the service.
A tracking or campaign number may have a different purpose, but check where it was published before assuming it is disposable. Beam’s number assignment guide describes how leads are paired with assigned lines. That routing behavior does not determine who has a contractual right to keep a number after an agency split. Inventory both long-standing business numbers and campaign lines, then confirm the agreed destination and provider requirements for each.
Where Does the Text Message History Actually Live?
Conversation history lives in the systems that received and stored it. In a setup that forwards only summaries from Beam into a CRM, those summaries should not be mistaken for complete threads. If messages are copied into both systems, verify what each copy contains and which account the client will retain. Beam’s conversation history documentation describes reading a contact’s history and listing recent workspace messages. Its iMessage guide for GoHighLevel agencies provides the rollout context; the exit question is what the client can still access afterward.
Say this before a split, not during one: a client who never confirmed where their conversation history lives can be surprised to learn, on the way out, that “their” conversations were never stored anywhere they have direct access to.
What Has to Be Exported, and What Has to Be Deleted?
Agree on the records the receiving team needs: message text, direction, timestamps, available delivery status, contact identifiers, and any required attachments. Check a sample against the original conversation before accepting the handoff. A contact summary is not a substitute for a thread when a customer asks about an earlier exchange. Confirm which fields and date ranges the provider can supply rather than promising a complete export without testing it.
Deletion is a separate decision from export. Beam’s Privacy Notice says information is retained as needed to provide the service, meet legal obligations, resolve disputes, and enforce agreements. It does not publish an automatic deletion countdown triggered by cancellation. Agree on who requests access or deletion and ask support what remains available before changing the account. The workspace readiness guide describes provisioning and sending states; those states are not an export or retention guarantee.
How Do You Put This in Writing at Onboarding Instead of the Breakup?
Decide these responsibilities during onboarding, then review them before the relationship ends. A written handoff plan should cover:
- Who controls the account. Record the business and authorized contacts for every provider account and workspace. Separately state the agreed rights to use or request transfer of each number.
- Who can authorize a transfer. Identify the authorized signer and confirm the provider’s requirements, including whether the assigned number can move to the intended destination.
- What records are handed over. Define the requested format, fields, date range, consent evidence, and opt-out records. Confirm availability with the provider and test a sample.
- When access changes. Agree on a handoff date, the person checking completion, and when agency access and automations should stop. Confirm the receiving team can work before closing the old account.
This is the same discipline behind handing off any AI-run system to a client cleanly; MetaTechAi’s AI automation handover checklist covers the broader version of that problem, and the same principle applies here: write the handover terms before you need them, not after.
How Do You Check the Handoff Before Removing Agency Access?
Have the receiving team open a sample conversation and find the earlier messages, contact details, and available delivery records. Use a test contact you control to check a reply and its CRM destination. Confirm the intended workspace and sending number, then check that an opted-out test contact remains blocked. These are proposed acceptance checks, not a claim that a provider migration automatically performs them.
Pause the agency’s scheduled follow-ups before enabling replacement automations. Record which team answers new replies during the transition and how unresolved conversations are assigned. Once the receiving team confirms access and the agreed records, remove obsolete seats and connections through the provider’s supported process. Keep the handoff record with the client agreement so a later question can be answered from evidence.
For the documented opt-out behavior behind these handoff checks, see Beam’s consent and opt-out guide.
What else should you know before choosing?
Can a Client Port a Number Away Without Telling the Agency?
Do not assume the agency will receive advance notice. Ask the provider who is authorized to request a transfer, what verification it performs, and what notices it sends. Record a separate notification requirement in the client handoff agreement. A valid LOA matters in processes that require it, but it does not by itself establish every condition for a transfer.
Do Opt-Out Records Transfer With the Number?
Do not assume they do. Beam documents a send-layer block for opted-out contacts and an event that lets a connected CRM record the request. Include those records deliberately in the handoff and verify suppression in the receiving system before resuming follow-ups. Moving a number is not evidence that the new platform has the old contact records.
What Happens When a Client Never Registered the Number in Their Own Name?
Review the provider account, authorized contacts, and agency-client agreement together. Confirm what changes the provider supports and what authorization it requires. The agency paying for a line does not, by itself, settle the client's contractual rights. Document the agreed destination and responsibility for the transfer before cancelling service.
Who Owns the Message History If the Platform Account Gets Cancelled?
Account access alone does not settle rights to customer data. Review the client agreement and provider terms, confirm which records can be retrieved, and complete the agreed handoff before cancellation. Beam's Privacy Notice describes retention for service, legal, dispute, and agreement purposes, rather than promising immediate deletion or indefinite retrieval after an account closes.