IOSOR Learn
Template catalog before channel Live
Buyer path: approved templates must exist before any Live badge on rich or SMS message classes — catalog first, volume talk later.
A Live badge on a message class without an approved template catalog is a prepaid burn with a green chip. Buyers need a named catalog of production templates before sales says Live for rich or SMS classes. This page is that buyer path — not a vault deep-dive and not a general SMS API shopping list.
Related: Failover gates before any Live badge, Day-1 runway: what must be green, When launch is blocked: status without lying, Template review gate and unit class.
IOSOR is white-label prepaid. USD 20 funds a catalog pilot on one corridor; soft review near USD 1,000/month prices empty-catalog Live as volume debt. Clients see white-label catalog states.
Catalog is the Live gate for message classes
Live means the class can take prepaid volume with honest status. Catalog means every production template ID is listed, approved, owned, and mapped to a unit class before send. Failover and runway may look ready, yet Live on WhatsApp, RCS, or templated SMS stays blocked until the catalog row exists. See Failover gates before any Live badge and Day-1 runway: what must be green. Do not paint Live from a slide while the catalog is a chat spreadsheet.
What an approved catalog row carries
| Field | Why buyers care |
|---|---|
| Template ID + version | Same object product and finance reconcile |
| Message class (OTP, alert, notice) | Stops class bleed into marketing copy |
| Review state | Approved only — draft never rides Live |
| Unit class | Segment, session, or template unit before debit |
| Owner + retire rule | Who fixes reject and when the ID dies |
Missing fields become folklore. Soft USD 1,000/month treats folklore as recon risk; USD 20 proves one corridor with every field filled. Unit class: Template review gate and unit class.
Channel Live vs catalog Live are different chips
A channel can be In setup while templates are drafted. A catalog can be approved for OTP while marketing templates stay draft. Do not collapse chips: channel ready ≠ “any template may send.” Prepaid hold fails closed on unknown IDs — Prepaid hold before first debit. Empty catalog + Live UI is a launch lie: When launch is blocked: status without lying.
Buyer path before any Live badge
- List month-one templates by message class.
- Submit review; wait for Approved — not “looks fine in staging.”
- Map each ID to unit class and debit tag.
- Smoke one send per class with catalog ID on the receipt.
- Only then allow Live language for that class.
Buyer checklist for template catalog
- Every Live message class has at least one Approved template ID?
- Draft and rejected IDs blocked from production send?
Start with IOSOR
Open the IOSOR console and cross-check your active template IDs against approved catalog statuses before attempting any Live channel transition. Ensure every message class has an explicit template mapping and verified unit class attached to its debit gate. Run a single smoke test transaction per class to confirm that DLR webhooks capture the exact catalog ID on delivery receipts before lifting production holds.
IOSOR takeaway
Channel readiness and template catalog approval operate on distinct execution gates. Marking a channel as operational without explicit, approved template IDs in the catalog causes prepaid hold systems to fail closed on unmapped payloads, regardless of underlying gateway status.
Was this guide helpful?
Related guides
- Managing Bulk Template Re-Submissions During Recovery Sequences
Learn how to systematically re-verify modified template bodies following carrier policy updates within the IOSOR ecosystem to maintain high delivery rates.
- Verifying Rich Media Header Assets Prior to Template Submission
Learn how to validate header images and document URLs in IOSOR to prevent template rejection. Ensure your rich media assets meet compliance standards before submission.
- Synchronizing Approved Message Templates Across Sub-Account Environments
Master the orchestration of approved templates within a white-label CPaaS ecosystem. Learn to maintain strict data isolation while ensuring sub-account compliance and rapid deployment via JIT provisioning.