IOSOR Learn

Template review gate and unit class

Gate template review and map unit class before prepaid debit at volume — Approved plus named unit, or no production send.

Protect your prepaid wallet from unmanaged costs by enforcing a strict review gate and mapping every template to a specific unit class before deployment. Failing to verify template approval and pricing bounds can lead to unpriced billable sends and significant reconciliation debt on your financial ledger. Implementing these controls ensures that every message is correctly priced and authorized before it impacts your balance. Related: Template catalog before channel Live, Fraud burn rows on the prepaid ledger, Debit rows vs delivery status ledger, Velocity caps before production OTP.

Review state is a hard gate, not a label

Draft, In review, Approved, Rejected, and Retired are money states. Only Approved may ride production send. Rejected and Draft fail closed with honest status — never silent fallback burn into another class. Catalog first: Template catalog before channel Live. Soft USD 1,000/month treats "send while In review" as volume debt; USD 20 proves Rejected cannot debit.

Map unit class before the debit posts

Unit class Typical use Debit expectation
SMS segment Templated SMS / UCS-2 Segments × list
Template unit Rich outbound template Per approved template send
Session unit User-initiated window Session window rules
Verify attempt OTP / code check Attempt or verify row .

Finance must read the same unit class on the debit row that product put on the catalog. Ledger neighbors: Debit rows vs delivery status ledger and Fraud burn rows on the prepaid ledger. Wrong class turns OTP spend into "misc messaging" folklore.

Fail closed when review or class is missing

Missing review state → no send. Missing unit class → no send. Unknown template ID → no send. Shared status words stop hero codes: Shared status language for product and finance. Velocity caps still apply on Approved IDs — review gate does not replace Velocity caps before production OTP; it sits ahead of volume language.

Product, finance, and ops share one proof

Product: can a legitimate Approved template complete under the mapped unit class? Finance: does every debit row carry template ID + unit class for the UTC window? Ops: can they export rejects and class mismatches without Slack archaeology? One proof pack beats three threads. Burn honesty when reject hides spend: Fraud burn rows on the prepaid ledger.

Buyer checklist for review gate and unit class

  1. Production send requires Approved — Draft/In review blocked?
  2. Rejected and Retired fail closed with honest status — never silent fallback burn into another class.

Start with IOSOR

IOSOR is white-label prepaid. USD 20 funds a review-gate pilot on one template ID; soft review near USD 1,000/month prices missing unit class as recon debt. Clients see white-label review macros only.

IOSOR takeaway

Prepaid systems need strict review gate and unit class mapping to avoid debt leakage. Approved templates with mapped unit classes ensure clean production sends. Soft reviews risk volume debt, while hard gates prevent silent failures. Buyers must verify these before any debit activity — this is the foundational check for all operations.

Was this guide helpful?

Related guides