IOSOR Learn
Coverage gap list finance can attach to a quote
Export one gap sheet — prefix shells vs Live vs capped WORLD — so sales and finance attach the same coverage truth to every volume quote.
A gap list is not a marketing map. Finance attaches one exportable sheet: shells, Live corridors with held proof, and capped WORLD exceptions with owners. Sales and finance open the same file — not two decks that diverge after the call.
IOSOR is white-label prepaid. Fund the wallet, hold before debit, buy JIT numbers only after assign. Floor USD 20; soft review near USD 1,000/month is when unsynced gap lists become night disputes. Quote honesty: Check coverage before you quote volume. Gate: Zone vs WORLD gate before production. Reject path: Uncovered prefix: reject honestly, do not silent-burn.
One gap sheet finance can attach
The annex is a platform export, not a slide. Columns answer: which destinations we promised, which are Live, which remain shells, which sit under a written WORLD cap. Chat pins and personal spreadsheets are not the annex. If finance cannot attach the same rows sales used in the room, the quote is fiction. Attach the file to the signed commercial pack; regenerate from the platform when corridors change — never a hand-edited overnight CSV.
Prefix shells versus Live truth
A prefix shell is a destination class without zone-live proof. Live means named zone plus a held prepaid send export — or an explicit capped WORLD exception with owner and expiry. Never label shells as Live to close a deal.
| Gap class | May appear in quote annex | Must stay out of Live claim |
|---|---|---|
| Zone + held send proof | Volume corridor | — |
| WORLD under written cap | Capped pilot only | Full-zone Live |
| Prefix shell / setup | Timeline to open | Any Live badge |
| Uncovered / reject path | Honest reject language | Sent or delivered |
Uncovered traffic follows the reject path — not silent burn. Pair gap honesty with the zone gate so prod keys never treat shells as Live.
Sales and finance share one export
Sales owns buyer language; finance owns attachable truth. Both open one CSV/JSON: ISO or prefix class, gap class, owner, override expiry, last held-proof id, annex version. Soft USD 1,000/month owners track WORLD spill here; USD 20 funds first held proofs that move a shell toward Live.
Money rows stay on the wallet ledger — Debit rows vs delivery status ledger — adjacent, not merged. Gap list = coverage class; debit rows = prepaid movement. Floor context: USD 20 floor vs volume review.
Quote language that survives soft review
Volume language only where the annex shows Live or a documented cap. Shells get open dates, not implied delivery. If sales promised zone and later sends reject as uncovered, fix the annex first — then keep reject honesty strict. Regenerate before each volume annex; expired overrides drop to shell or reject. JIT assign still follows hold → buy → assign.
Buyer checklist for the finance gap list
- One platform export attached to the signed quote pack?
- Shells clearly marked — never sold as Live?
Start with IOSOR
Export the gap list for every ISO on the draft quote. Mark each row shell, Live with held proof, or capped WORLD with owner and expiry. Attach the same file finance will sign. This is the commercial annex — not the 02:00 delta, not the three-destination pre-quote ritual, and not an incident stop on blasting prefixes.
IOSOR takeaway
Sales and finance attach one gap sheet or the quote is fiction.
Do: regenerate the annex from the platform when corridors change.
Don't: let two decks diverge after the call, or label a prefix shell as Live to close.
Was this guide helpful?
Related guides
- Verifying Secondary Routing Fallbacks When Primary Network Reach Drops
Establish operational checks for fallback routing reach when primary network corridors experience coverage degraded states with IOSOR.
- Syncing Just-in-Time Number Allocation with Country Reach Limits
Learn how to sync real-time JIT number provisioning with regional regulatory reach and prefix availability on the white-label IOSOR platform.
- Configuring High-Reliability Reach Gates for Transactional 2FA Corridors
Learn how to configure strict delivery reach verification and routing gates on IOSOR to prevent silent OTP drop-offs for critical authentication traffic.