An agency handover can leave a business able to answer calls but unable to change its own number settings. Access to the AI dashboard and authority over the telephone account are separate parts of the operating arrangement.
For agencies and clients ending or transferring an engagement, inventory the number-related accounts before the handover date. Resolve missing administrators while the current team is still available to help.
What does phone account ownership mean operationally?
Identify who is the account holder, who pays bills, who can change routing and who can authorise any supported transfer. These roles may sit with different people or organisations.
This is an operational checklist rather than a legal conclusion about number rights. Have qualified advice address disputed contract terms or ownership claims. The engineering task is to make the current control and dependency structure visible.
Create a number-by-number inventory
Do not assume the main office number, test number and regional numbers use the same account. Record each one with its current purpose and responsible administrator.
| Inventory field | Why it matters |
|---|---|
| Number and business purpose | Prevents forgotten regional or campaign routes |
| Hosting provider and account | Identifies where changes are made |
| Billing and renewal contact | Prevents accidental suspension |
| Authorised administrators | Establishes practical access |
| Forwarding and fallback rules | Preserves the current caller workflow |
Keep sensitive account details in the appropriate controlled system. A handover spreadsheet should reference the access process rather than contain raw credentials.
Verify receiving-team access with a safe task
Ask the new administrator to inspect the routing settings and approved contact information. If a harmless test change is appropriate, perform it through the agreed procedure and restore the intended configuration.
An invitation email alone does not establish that the recipient has the required role. Check whether they can perform the specific responsibilities being handed over without relying on the departing agency's personal account.
The software project asset checklist covers related repository, domain and cloud-account dependencies.
Preserve continuity during the transfer
Coordinate access changes, billing changes and routing changes as separate actions. Avoid removing the only working administrator before the receiving team confirms access. Any supported provider transfer should follow its current process.
Retain an approved route map and identify the rollback or escalation owner. My voice platform contribution provides project context, while the client's actual provider accounts determine what a safe handover requires.
Does paying the agency invoice establish phone-account access?
It does not demonstrate the permissions needed to operate the account. Verify the actual roles and contractual arrangement separately.
Should the agency email its credentials to the client?
Use supported account access or transfer procedures instead of sharing personal credentials.
What should be checked before the handover ends?
Confirm authorised control, billing contacts and the live route through a voice AI handover review.