A business should know who controls its phone number and connected accounts before the receptionist becomes part of daily operations. Access ownership affects recovery, billing, handover, and the ability to change suppliers.
Create an asset register with legal or administrative owner, billing party, account administrator, delegated operators, recovery route, and transfer constraints. Distinguish using an asset from owning or controlling it.
Verify the actual account model
Phone providers and AI services use different organization, user, and transfer models. Inspect the current account and vendor documentation for the intended arrangement rather than assuming an agency login can be handed over later without consequences.
Use role-based delegated access where supported and appropriate. Avoid sharing one person's password as the operating model. Keep secrets separate from the ordinary asset register and record who may authorize connection changes.
Work through a fictional agency transition
A client wants to bring its receptionist service in-house. The phone number is billed through the agency, the integration application is developer-owned, and alerts go to a contractor's email.
The handover plan must address each dependency independently. Moving the prompt does not transfer the number, billing, application ownership, or recovery capability. The client should review concrete transfer or replacement steps before relying on the new arrangement.
| Asset | Ownership evidence |
|---|---|
| Business phone number | Provider account control and transfer route |
| AI service account | Organization administrator and billing |
| Integration authorization | Authorized client scope and reconnection owner |
| Secrets | Controlled storage and rotation responsibility |
| Alerts and domains | Current operational recipients and control |
Test recovery before removing old access
Have the intended administrator demonstrate supported access and recovery. Verify that the client can identify active routing and suspend consequential actions if needed. Revoke departing access according to the approved transition after replacement control works.
Client-owned accounts can simplify independence while adding onboarding and billing coordination. Agency-managed accounts can simplify a bundled service while requiring explicit exit and access terms. Neither arrangement should remain an unstated assumption.
Review client handover for operational acceptance beyond an export file.
Questions about account ownership
Should every account be in the client's name?
Choose an explicit arrangement that matches the service and vendor capabilities, with recovery and exit responsibilities documented.
Does paying an invoice establish account control?
Not necessarily. Verify administrator access and the provider's actual ownership and transfer model.
What should the asset register exclude?
Do not put raw passwords or tokens in a general handover document. Reference the approved secure access process instead.