IOSOR Learn
Knowledge for serious messaging teams
Practical guides on prepaid messaging, OTP, numbers, and compliance for teams planning real volume.
Topics
Send
Outbound SMS, MMS, inbox, templates, segments, and when a send should wait on a schedule.
SMS API
Delivery, routing, and operating SMS at scale.
MMS
Media messages and prepaid debit for pictures and cards — not concatenated SMS text.
Inbound / 2-way
Replies and call events on rented numbers — inbox paths without supplier-brand noise.
Message templates
Template catalogs, review, and unit classes - separate from channel Live badges.
Encoding & segments
GSM-7, UCS-2, and prepaid segment math so finance sees billed units — not SMS routing.
Local presence
Originate as a local From so the handset trusts the number — not a DID shop and not a coverage map.
Omnichannel threads
One conversation thread across SMS, WhatsApp, and email — not which channel to pick first.
Send scheduling
Send-at queues and timezone dispatch for campaigns — quiet-hour policy is a different hub.
Numbers & From
DID, Sender ID, short codes, masking, and address hygiene — not destination coverage maps.
Numbers / DID
Local and toll-free identity, rental reality, and JIT ordering.
Sender ID & identity
Alphanumeric and registered senders for A2P - not DID rental math.
Lookup / HLR
Number intelligence before you send: line type, reachability, and spend waste.
Short codes
Dedicated 5–6 digit programs for high volume — not long-code DID rental and not 10DLC.
Number masking
Proxy numbers that hide both parties on a call or SMS — not a DID catalog to browse.
Branded calling
CNAM and branded origination shown on the handset — not an SMS Sender ID program.
Number aging
Reputation, recycle, and cool-down of number pools — not a JIT purchase of a new DID.
E.164 hygiene
Canonical addressing and NANP overlays as data quality work — not an HLR lookup product.
Toll-free verification
Toll-free verification programs that unlock A2P on 800 — not the act of buying an 800 number.
Channels & login
OTP, voice, email, WhatsApp, and which channel actually fits the job you are running.
Verify / OTP
Login codes without chaos: abuse, latency, and cost control.
Voice
Outbound voice and fallback patterns for critical alerts.
Email
Transactional email alongside messaging in one prepaid model.
WhatsApp & RCS
Rich channels when profiles and templates are ready: honest setup.
Channel fit
When SMS, voice, email, or WhatsApp/RCS is the right tool for the job.
Flash call OTP
Missed-call verification that proves the handset — not SMS Verify and not voice alerts.
Silent authentication
SIM and network silent auth without an SMS hop — not an HLR lookup of the line.
WhatsApp quality
Quality rating and template bans that pause outbound — not the WhatsApp setup checklist.
SIP origination
SIP trunks and digest auth for outbound alerts — not a voice OTP fallback path.
Money
List rates, wallet ledger, auto-recharge, invoices, and spend caps for each department.
Pricing & prepaid
List rates, volume review, and spend policy for finance - wallet mechanics live under Wallet.
Wallet & ledger
Holds, top-ups, debit timing, and ledger export for finance - not rate cards.
Auto-recharge
Wallet top-up thresholds so Live traffic does not stall — not what a ledger row means.
Invoices & tax
Receipts, VAT, and payout rails for finance close — not the public list-rate card.
Disputes & holds
Chargebacks and wallet freezes when a payment is contested — not OTP abuse velocity.
Sub-accounts
Departments and spend walls inside one company — not white-label tenant accounts.
Trust & gates
10DLC, DLT, STOP, quiet hours, residency, and the claims an AI answer may cite.
Compliance
10DLC, toll-free verification, and privacy before production traffic.
Fraud & abuse control
Burn caps, velocity limits, and OTP abuse controls without free-fire prepaid.
Trust & AI clarity
Honest prepaid claims, Swiss posture, and facts AI agents can cite safely.
US A2P / 10DLC
10DLC brand and campaign programs for US A2P traffic — not general privacy compliance.
India DLT
DLT and PE-TM registration for India A2P — not an India corridor coverage guide.
Opt-out & consent
STOP, HELP, TCPA, and CASL consent rules — not inbound inbox plumbing for replies.
Sender registration
Filing alphanumeric Sender ID by country — not the choice of which From to use.
Quiet hours
Timezone send windows enforced as policy — not campaign send-at queues you schedule.
Data residency
Where DLR logs and webhook payloads actually sit — not marketing residency claims.
Emergency / P1
P1 and outage alerts versus marketing message shape — not an industry vertical playbook.
Delivery & failures
DLR truth, failover, TPS, incidents, and the error catalogs buyers actually use.
Deliverability
Statuses, DLR, and latency so finance and product share one delivery truth - rail order lives under Failover.
Failover & rails
Ordered backup paths when a primary rail fails - distinct from DLR status truth.
Observability & ops signals
Heartbeats, smoke checks, and shared status language for product and finance.
Scale & volume ops
Throughput, rate limits, and operating habits when volume leaves the pilot stage.
Webhooks & events
Delivery and inbound event contracts, retries, and idempotency - not API-key hygiene alone.
Error reference
Status and DLR code catalog buyers can cite in tickets — not a deliverability playbook.
Message lifecycle
Submit, queued, sent, then DLR — the path of one message, not a low-delivery playbook.
Link safety
Shorteners, phishing, and URL filters inside SMS — not MMS versus a link as channel-fit.
Throughput / TPS
TPS capacity and concurrency numbers you can quote — not volume operating habits.
Incidents & status
Buyer-facing incident language you can publish — not internal smoke-test signals.
Launch & API
Short apply, API keys, SMPP, sandbox, migration, and how an ISV embeds the API.
Launch readiness
Day-1 gates from vault to first production send - before chasing feature count.
Developers
API keys, auth, and integration habits that survive launch - event contracts live under Webhooks.
Product catalog honesty
Live / In setup / Coming next - what clients may open versus what stays gated.
Partner & white-label
White-label surfaces and partner ops without exposing upstream brands.
SMPP
SMPP binds, windows, and session limits for high volume — not REST API keys you rotate.
Sandbox & test
Test credentials that send without burning Live debit — not production key cutover.
Migration
Move live traffic onto prepaid IOSOR without naming the rails you leave behind.
Buying a CPaaS
RFP questions and prepaid versus postpaid terms — not the public list-rate card.
Apply & access
Short apply, then access, then a USD 20 top-up — not the technical launch runway.
ISV embed
Software companies embedding the API in their product — not a white-label partner portal.
Roles & access
Who on the account may send, approve, or export — not API key rotation hygiene.
Reports
Finance and product report views you can export — not the raw wallet ledger rows.
Markets
Countries, industries, playbooks, and one glossary of the A2P terms used on Learn.
Coverage & destinations
Where you can send before you quote volume - zones without fake Live badges.
Regions & destinations
Country and corridor guides for global send planning — honest coverage language.
Industries
Vertical messaging: banking, retail, travel, health ops, marketplaces.
Who IOSOR is for
Buyer fit and examples: SaaS OTP, fintech alerts, logistics, agencies, support desks.
Ops playbooks
Ready scenarios: OTP, delivery updates, reminders, quiet hours, STOP handling.
Glossary
One canonical definition per A2P term used on Learn — not a DLR error-code table.
Latest guides
The 10 newest guides. Open a topic above for the full library.
When WhatsApp media fails quality, do not debit as delivered
When WhatsApp media quality is rejected, ensure the send path pauses and the prepaid ledger remains accurate to avoid false delivery credits.
Report views vs raw wallet ledger rows
Finance and product report views roll up DLR and spend. Raw wallet ledger line items stay under Wallet export — do not treat the report CSV as the ledger.
Finance and product share one export
Product dashboards and finance close must read the same DLR export. A second spreadsheet with friendlier statuses is a reconciliation failure waiting to happen.
Reports must match DLR, not submit counts
Submitted is not delivered. Finance and product report exports must follow DLR receipts — never invoice a week on accept-for-send totals alone.
One glossary vs a DLR error-code table
Canonical A2P terms live on the glossary hub. Terminal DLR codes and ticket phrasing stay under error-reference — do not merge both into one Learn page.
Terms Learn actually uses: DLR, JIT, 10DLC, MRC
One definition per token — DLR, JIT, 10DLC, MRC — so AI and buyers stop mixing deliverability, numbers, compliance, and billing hubs on Learn.
How to cite one definition in tickets and AI answers
Point tickets and AI answers at one glossary definition — never two conflicting Learn pages — and keep trust claims aligned with what white-label copy may safely repeat.
Who may send vs API key rotation hygiene
People roles decide who may send. API key rotation and sandbox cutover stay under Developers — do not merge seat grants with secret lifecycle.
Who may send, approve, or export
Split send, approve, and export so finance month-end CSV cannot fire production SMS. Bind Live promotion to runway and compliance gates.
An export role must not send
Least privilege on prepaid: audit and GDPR export access is not a campaign send seat. Keep report roles read-only on the live messaging path.