MVNO wholesale order and porting handoff
How do we pass orders and number ports between an MVNO and the host network with each side's data validated before submission, so activations and ports do not fail at the handoff?
Validate the handoff on both sides before the order crosses. Callvu prefills the MVNO's order from its own systems (the subscriber, the plan mapped to the host's wholesale product, the SIM or eSIM, the device's identifier and compatibility, the service address), classifies the order type (a new activation, a port-in from another carrier, a port-out, a change, a deactivation) and the host's requirements for it, chases and verifies the data the host will reject if wrong (the porting details against the losing carrier's customer service record, the account number and the port PIN, the device's eligibility on the host network, the address for 911), submits the order to the host's wholesale interface in the host's format, tracks the host's response and the port's status on the porting clock, routes a rejection or a port conflict to the wholesale operations desk in the Decision Desk with the reason codes, and writes the result to the MVNO's BSS, the system of record, with the subscriber told.
In scopeComplex: multi-party handoffsCallvu moves: prefill, chase and verify, classify, write back
Last updated November 7, 2026.
The problem today
The port was rejected three times for a mismatched account number the MVNO's agent never saw, and the subscriber's old carrier kept billing.
An MVNO sells the service and the host network runs it. Every activation, port and change is an order that crosses between two companies' systems, in the host's format, with the host's rules. The errors are at the edge: a plan that maps to the wrong wholesale product, a device the host does not support, a port with the losing carrier's details typed wrong, an address the 911 system rejects. Each rejection is a day lost and a subscriber without service.
The porting rules set what a simple port needs and how fast it must complete, and the losing carrier may reject for a mismatch in the account number, the PIN or the address. The host's wholesale agreement sets the order format, the product catalog and the response codes. Validating the order against both before it is submitted turns the handoff from a retry loop into a single submission with a known outcome.
An order validated on both sides crosses once.
How it runs
From the requestto the system of record.
An MVNO subscriber orders a new line, a port-in, a change or a deactivation through the MVNO's channels, or the host sends a port-out notification. Callvu opens the wholesale order.
- Subscriber
- Provides the porting details and confirms the device and the address on their phone.
- MVNO operations
- Decides rejections and conflicts in the Decision Desk.
- Host network wholesale interface
- Receives the order and returns the response and the port status.
- Callvu
- Prefills, classifies, validates, submits, tracks, routes and writes.
Prefill and classify
The order is prefilled from the MVNO's BSS (the subscriber, the plan and its mapping to the host's wholesale product and features, the SIM or eSIM profile, the device identifier, the service address); the order type classifies the host's requirements and the data to validate (a new activation, a simple or a complex port-in, a port-out, a plan or feature change, a suspension or deactivation).
Chase and verify before submission
The data the host or the losing carrier will reject is validated first: the device's identifier against the host's compatibility and blocklist, the SIM's state, the address against the 911 address guide, and for a port-in the subscriber's account number, port PIN, name and address with the losing carrier as they appear on the customer service record, with the subscriber asked on their phone for what is missing or wrong, and the letter of authorization captured where the port needs it.
Submit and track
The order is submitted to the host's wholesale interface in the host's format with the mapped product and the validated data; the host's response codes are read, the port's status is tracked against the porting clock (the simple port interval, the losing carrier's response window, the scheduled port date), and the subscriber is told the status and the activation time.
Route rejections and write back
A rejection or a conflict (a losing carrier mismatch after validation, a host fallout, a port-out with a fraud indicator, a jeopardy on the port date) goes to the wholesale operations desk in the Decision Desk with the reason codes and the data and only the allowed outcomes (correct and resubmit, cancel and notify, escalate to the host, or hold for fraud review); the result (the activation, the ported number, the change, the deactivation) is written to the MVNO's BSS, the system of record, and the subscriber's account, with the billing started from the activation date the host confirmed.
Where it ends: Every wholesale order crossed to the host once with the product mapped and the porting and device data validated, was tracked on the porting clock, and the rejections that remained were decided with their reason codes, with the MVNO's BSS holding the result. The Decision Trace shows the classification, the validations and any decision; the Audit Trace shows the submission, the host's responses and the port status 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 MVNO's channels; the subscriber supplies porting details and confirms on their phone.
The back office
The wholesale operations desk decides only rejections and conflicts; the BSS is written from the host's confirmation.
The Decision Desk
- A rejection, a losing carrier mismatch, a host fallout, a port-out fraud indicator or a port date in jeopardy goes to the wholesale operations desk in the Decision Desk with the reason codes and only correct and resubmit, cancel and notify, escalate to the host, or hold for fraud review.
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.
What is validated before the order goes to the host?
The plan's mapping to the host's product, the device's identifier against the host's compatibility, the SIM's state, the address against the 911 guide, and for a port the subscriber's account number, PIN, name and address as the losing carrier holds them.
How is a port tracked?
Against the porting clock: the simple port interval, the losing carrier's response window and the scheduled port date, with the subscriber told the status and the activation time.
What happens on a rejection?
The wholesale desk decides with the host's reason codes: correct and resubmit, cancel and notify, escalate to the host, or hold for fraud review; nothing is retried blindly.
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.