Identify what the successor must do
List routine tasks such as checking hours, finding the relevant route, locating support and identifying unresolved port requests. Include billing and cancellation responsibility where appropriate, but keep legal or financial approvals with the people authorised to provide them.
Use the account’s legitimate access process
Confirm appropriate administrator access through the provider’s supported process. Do not share a departing colleague’s password or copy private recovery information into a general operations document. Access permissions and a written responsibility assignment are separate requirements.
Demonstrate the ordinary tasks
Have the successor locate the current route and relevant evidence using authorised access. Resolve missing documentation while the current owner is available. Record where number-registration details and provider conversations are securely held without reproducing them unnecessarily.
A fictional succession
A manager leaves after a successful port. The successor can see the account but cannot explain the temporary forwarding rule. The handover includes its purpose and removal condition, preventing a well-intended cleanup from breaking a still-needed route.
Check understanding with a bounded walkthrough
Ask the successor to explain the opening-hours rule, locate the no-answer destination and identify the owner of voicemail using their own authorised access. They need not make changes to demonstrate understanding. Then ask where an unresolved port request, provider support conversation and current quote are recorded. If a reference is missing, repair the handover document rather than copying private account contents into it. Agree what the successor may change independently and what requires further approval. Include the date when the former administrator's responsibilities end and arrange access review through the organisation's normal process. A useful handover leaves the successor able to maintain routine service and recognise when to stop. It does not require sharing passwords, bypassing verification or transferring authority the departing person never held.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- CloudTalk call-flow designer — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28
- CloudTalk porting away — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28