IOSOR

IOSOR Learn

Compliance Second Month: Evidence Pack Persistence

Understand why your 10DLC and Toll-Free evidence packs remain critical during the second month of operations and how they gate production access.

Compliance Second Month: Evidence Pack Persistence.

Maintaining Compliance Continuity

Transitioning into the second month of operations on the IOSOR platform requires more than just maintaining a positive balance. While the initial setup focuses on onboarding, the second month is where the stability of your messaging ecosystem is tested. The evidence pack you submitted during the first 30 days is not a one-time formality; it is a persistent requirement that ensures your traffic remains within the bounds of global carrier expectations. Unlike the Compliance invoice week: evidence pack gaps on the bill month, which focuses on financial reconciliation, this phase is about operational hygiene.

Evidence Pack Standards for 10DLC and TF

To keep your production access active, the evidence pack must accurately reflect the live traffic patterns observed by our monitoring systems. This includes verified opt-in flows, clear brand identification in every SMS, and functional help/stop keywords. If your traffic profile shifts—for example, moving from simple OTP notifications to marketing broadcasts—the existing evidence pack may no longer suffice. Our compliance gates before A2P are designed to trigger a re-evaluation if the DLR failure rates spike or if the content deviates from your original submission.

Scaling Thresholds and Soft Reviews

As your volume grows, the IOSOR platform implements specific financial and technical checkpoints. We maintain a strict USD 20 prepaid floor to ensure account liquidity for JIT number assignments. Once your monthly spend approaches the USD 1,000 soft review mark, our compliance team performs a manual audit of your current evidence pack. This review ensures that as you scale, your messaging practices still align with the documentation provided during the Compliance volume review: evidence pack before the closer. This is a proactive measure to prevent sudden service interruptions.

JIT Provisioning and Prepaid Logic

IOSOR operates on a Just-In-Time (JIT) provisioning model. We do not maintain a static inventory of numbers; instead, numbers are assigned and provisioned dynamically based on your active prepaid balance. This model prevents the accumulation of stale resources and ensures that every 10DLC or TF number associated with your account is actively tied to a verified use case. The prepaid hold mechanism ensures that resources are only allocated when there is sufficient coverage for both the acquisition and the projected traffic volume for the billing cycle.

Distinguishing Gates from Invoice Gaps

It is vital to distinguish between production gates and invoice-related holds. A production gate is a technical block triggered by a lack of valid evidence or a violation of messaging policies. An invoice gap, conversely, is a reconciliation issue where billing amounts do not match usage evidence.

Start with IOSOR

Name the month-two evidence owner before any MT resumes. Re-export last month’s pack — 10DLC or TF proof, consent timestamps, Sender ID file — and park it under a hold that stays live. Prove a send is blocked while any artifact is stale or archived. An invoice export is not this gate; a volume-review folder is a different job.

IOSOR takeaway

Month two is an evidence hold, not a new campaign and not a volume-review dump.

Do: keep the pack current, named, and blocking until every artifact is fresh. Don’t: resume MT on last month’s screenshots, or hand finance a closer pack in place of this hold.

Was this guide helpful?

Related guides