Make three responsibilities explicit
The porting lead coordinates the carrier request. The routing owner prepares the application and staff destinations. The acceptance reviewer checks whether the intended caller journeys work. One person may hold more than one role, but leaving a responsibility unnamed creates an avoidable gap.
Prepare cover before the date
Identify who can act if the main administrator is unavailable. Use legitimate delegated access with the least permissions needed; do not pass around one shared password. Confirm how the provider contacts the business during the transfer and who monitors that channel.
Record stop and escalation rights
Agree who may postpone the cutover and which unresolved requirements justify doing so. Make the support contact route available outside the new phone system. A plan that requires a broken line to contact its only owner is not usable incident coordination.
A fictional handover
The office manager coordinates the port, a service lead owns open-hours routing and a colleague checks the agreed journeys. When the date changes, the porting lead updates both owners. Nobody interprets silence from one team as evidence that its work is complete.
Give a small team distinct responsibilities
One person may hold several roles, but the roles should still be named: business decision owner, authorised account contact, routing administrator and acceptance reviewer. Add a deputy for the cutover period and a provider escalation contact. For a three-person office, the manager might authorise the change while a colleague maintains the route and another observes the agreed caller journey. This is a suggested allocation, not a requirement to hire specialists for routine administration. Identify decisions the deputy cannot make, such as accepting new contract terms or changing specialist equipment. When an issue occurs, the team should know who can investigate and who can authorise a consequential change. A list of names without those decision boundaries is not an effective handover.
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 porting requests — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28
- CloudTalk call-flow designer — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28