Letter of authority for business ports
How do we collect the signed letter of authority and the customer service record for a multi-number business port before the port request is submitted?
Treat the letter of authority and the customer service record as the port's prerequisites, not its paperwork. When a business orders a port of several numbers, Callvu classifies the port (the losing carrier, the number count and types, the account structure, the port type under the rules and its interval), requests the customer service record from the losing carrier or from the customer, generates the letter of authority from the order with the numbers, the losing carrier's account details and the authorized signer, chases the signature from a signer whose authority is checked and the record from its holder on the port's schedule, reads and checks the record against the order (the billing name and address, the account number, the numbers and their status, the PIN where used), routes a mismatch or a partial port question to the porting desk in the Decision Desk, and submits the port request only when the letter and the record agree with the order, with the request written to the BSS and the requested date set under the porting rules.
In scopeComplex: multi-party handoffsCallvu moves: chase and verify, classify, write back
Last updated November 7, 2026.
The problem today
The port was rejected three times for an account number that did not match, and the customer's cutover date passed on the third rejection.
Business ports are rejected for the same reasons every time: the losing carrier's account number is wrong, the billing name or address does not match the customer service record, the numbers listed include one on a different account, the letter of authority is signed by someone the losing carrier does not recognize. Each rejection costs days under the porting intervals, and the customer's cutover is planned around a date the carrier cannot keep.
The porting rules set the information the losing carrier may require and the intervals once a valid request arrives; the customer service record is the losing carrier's own view of the account, and the port request must match it; the letter of authority is the customer's authorization naming the numbers and signed by someone with authority. Getting the record first, checking the order against it, and generating the letter from the checked order is how ports stop being rejected.
A port submitted to match the losing carrier's record is a port that completes in the interval.
How it runs
From the requestto the system of record.
A business order includes numbers to port from another carrier (through the enterprise order or a business activation). Callvu opens the port on the order and classifies it.
- Customer's authorized signer and contact
- Provide the losing carrier's account details and the customer service record where they hold it, and sign the letter of authority.
- Losing carrier
- Provides the customer service record on request and receives the port request.
- Porting desk
- Decides mismatches and partial ports in the Decision Desk.
- Callvu
- Classifies, requests the record, generates the letter, chases, checks, routes, submits and writes.
Classify the port
The losing carrier, the numbers (count, type, and the accounts they sit on), the port type under the rules (simple or complex, by the number count and the services on the numbers) and its interval, the requested date and the dependencies (a circuit order, an activation) classify the port and the items it needs: the customer service record, the letter of authority, the losing carrier's account number and PIN where used, and the authorized signer.
Chase and verify the record
The customer service record is requested from the losing carrier (through the industry process with the customer's authorization) or uploaded by the customer from their losing carrier's portal; it is read on arrival and checked against the order: the billing name and address, the account number, each number's presence and status on the account, the services and features that affect the port (a hunt group, a toll-free association), and the PIN where the losing carrier uses one; a difference is put to the customer's contact with the specifics.
Generate the letter and decide
The letter of authority is generated from the checked order with the numbers, the losing carrier's account details and the authorized signer, and sent for signature on the signer's own screen with their authority checked against the account's signers; a mismatch that the customer cannot resolve, a number on a different account, a partial port that would strand services, or a date inside the interval goes to the porting desk in the Decision Desk with the record and only the allowed outcomes (submit as checked, submit the matching numbers only, hold for the customer's correction with the losing carrier, or decline the date with an alternative).
Submit and write back
The port request is submitted to the losing carrier only when the letter and the record agree with the order, with the requested date set under the rules' interval, the request and its status are written to the BSS against the order, the customer's contact sees the status and the firm order commitment when it returns, and a rejection returns to the case with the reason mapped to the item that caused it.
Where it ends: The port request matched the losing carrier's own record because the record was checked first, the letter of authority was generated from the checked order and signed by an authorized signer, and the BSS, the system of record, holds the request with a date the interval supports. The Decision Trace shows the classification, each check and any decision; the Audit Trace shows the record's arrival, the signature and the submission with time.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The enterprise order or the business activation; the customer's contact and signer through their links.
The back office
The porting desk decides only mismatches and partial ports; the request is submitted from the gate.
The Decision Desk
- An unresolved mismatch, a number on a different account, a partial port that strands services or a date inside the interval goes to the porting desk in the Decision Desk with the record and only submit as checked, submit the matching numbers, hold for correction, or decline the date with an alternative.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
AT&T runs close to 100 processes on Callvu, used by 55,000 agents.
Questions
What buyers ask next,answered plainly.
Why obtain the customer service record first?
Because the port request must match the losing carrier's own record (the name, address, account number and numbers), and a mismatch is rejected, restarting the porting interval; checking the order against the record first is what stops the rejections.
Who signs the letter of authority?
A signer whose authority is checked against the business account's signers, on their own screen, with the letter generated from the checked order and the numbers.
What can the losing carrier require?
Only the standard validation fields under the porting rules; the record and the letter cover them, and anything more is a question for the porting desk.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.