Billing and service addresses can differ
A current invoice may show the place that receives bills rather than the address held in the number’s service record. Ask which details the port request must match. Do not repair a mismatch by trying several plausible addresses or changing legal information without authority.
Handle codes as protected information
Some number types and countries use a PIN or migration code. Ask for the correct process and store such details securely with restricted access. A public article cannot establish which code applies to a particular number, and this site has no field for receiving one.
Use a controlled correction
If a provider rejects details, preserve the specific reason and correct the relevant field through the authorised route. Avoid opening parallel orders with slightly different information. Record whether a correction changes the scheduled date or requires renewed acceptance.
A fictional mismatch
An organisation has moved its office but retained a number registered at the old service address. The project lead confirms the record with the carrier and follows its correction instructions. She does not assume that updating an invoice contact automatically updates number-porting data.
Keep a mismatch log instead of trying variants
Use three fields in the private project record: the provider's stated mismatch, the authoritative source for the correction and the person authorised to make it. Keep the actual sensitive value in its approved location rather than copying it into every status update. For example, a service-address discrepancy should be resolved against the relevant carrier record, not by selecting whichever address makes a form validate. Before another submission, confirm whether the original request is awaiting correction or has been closed. A second order can make responsibility harder to track. Once the receiving provider acknowledges the corrected information, preserve that receipt and the remaining status. A successful form save establishes only that the form accepted input, not that the number record now matches.
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 port preparation — 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