Job title is not enough
A company owner, office manager or consultant may understand the business without being the recorded authorised contact on the carrier account. CloudTalk’s porting guidance warns that signatory details can matter. Ask the current provider to confirm the applicable authority process; do not improvise a signature or claim another person’s permission.
Resolve account access safely
Use the organisation’s approved account-recovery or administration route when the named contact has left. Do not share passwords among staff or send private authentication codes in ordinary planning documents. The work may require a protected identity or legal step beyond a routine software purchase.
Keep the evidence with the order
Record that authority was confirmed, who owns the request and where the controlled supporting evidence is held. Avoid duplicating identity documents in a broad project sheet. Ask the receiving provider which exact form and signature method it accepts.
A fictional delay avoided
A founder assumes she can sign because she owns the company, but the carrier lists a former administrator. The team resolves the account record through the carrier’s process before submitting the port. This is an authority check, not a claim that any particular legal relationship permits transfer.
Prepare the handoff to the authorised person
Give the signatory the proposed scope, purpose of the transfer and provider instructions before asking for a signature. Identify which account or number record the authority check concerns, without sending authentication secrets in the same message. Ask the provider how a rejected or expired authorisation should be corrected; do not edit a signed document after the fact. Record the submission reference and responsible contact in the controlled project file. If the named person is unavailable, use the provider's legitimate alternative process rather than borrowing their login. Completion of this step means the appropriate authority was established for the intended request. It does not mean the carrier accepted the order, scheduled the transfer or waived any contractual obligation.
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 requests — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28