IOSOR
LearnSign InConnection applicationRestore Access
  1. IOSOR
  2. /Knowledge hub
  3. /Message templates

Message templates

Template catalogs, review, and unit classes - separate from channel Live badges.

25 guides in this topic

  • Template unit class on debit rows

    Every prepaid debit row must carry a named unit class — template, session, segment, or verify — so finance can join spend without folklore spreadsheets.

  • Template catalog ops at volume

    Operate versioning, named owners, and retire rules when many templates are Live — one catalog rhythm product and finance can open without hero threads.

  • Template reject: no silent fallback burn

    Fail path: a rejected template must stop the send — no silent SMS or session burn without a named fallback policy product and finance can audit.

  • 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.

  • 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.

Page 3 of 3

  1. Previous
  2. 1
  3. 2
  4. 3
  5. Next

Adjacent topics

  • WhatsApp quality
  • Sender ID & identity

Not this hub: WhatsApp & RCS

Ready for a controlled prepaid path?

Tell us destinations, monthly volume, and compliance constraints. We will map onboarding clearly.

Apply for access
AboutKnowledge hubSite mapnFADP Privacy PolicyGDPR ComplianceTerms of ServiceSLA AgreementB2B Master AgreementApply for access

English is the sole legally binding language of IOSOR legal documents. Summaries in other languages are for convenience only.

© 2026 IOSOR · All rights reserved.🇨🇭 Switzerland