Follow the current submission route
CloudTalk’s current help instructions describe a dashboard porting process. Older marketing material still describes email-based steps. Follow the current account workflow and provider confirmation rather than combining two routes and accidentally submitting the same transfer twice. This site does not receive or submit porting documents.
Check completeness before release
Confirm the number scope, authority, registered details and any required supporting records. Use the actual form supplied for the relevant number type and country. Do not copy an authorisation template from another market and assume it applies.
Track one request identity
Keep the provider’s request reference and the latest status in a controlled project record. If submission is uncertain, inspect the existing request or ask the assigned provider team before resending. Preserve a correction history so a colleague can distinguish the original request from its revisions.
A fictional submission boundary
An administrator clicks submit but receives no clear confirmation. Rather than create another order, he checks the dashboard’s existing porting requests and the assigned conversation. The absence of a success banner is uncertainty, not proof that no request exists.
Assemble one controlled submission package
Make a checklist of the documents the receiving provider actually requests for this number and jurisdiction. Record the version, responsible preparer, signature requirement and secure submission route without attaching private documents to a widely shared planning sheet. Check that the names and scope agree across the package before sending it. If the provider changes a requirement, preserve the earlier submission and the new instruction so corrections remain traceable. Avoid collecting extra identity information merely because another country's checklist mentions it. After submission, retain the receipt and identify what happens next: review, correction, scheduling or completion. A complete package reduces avoidable uncertainty, but it does not guarantee carrier acceptance or authorise a particular date. Keep those subsequent events separate.
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 port preparation — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28