IOSOR Learn
Catalog Pilot Week: Live vs Setup After First Workshop
Learn how to distinguish live routes from setup states in your CPaaS catalog dashboard during your pilot week, including JIT number holds and balance limits.
Catalog Pilot Week: Live vs Setup After First Workshop.
Disambiguating Pilot Week Statuses
During the first week after launching your CPaaS platform workshop, the catalog dashboard presents distinct states: active channels versus items undergoing provisioning. A common misinterpretation occurs when team members confuse technical setup readiness with public tenant availability. To ensure clean operations, the administrative view clearly separates live routes from pending carrier approvals.
Dashboard State vs Catalog Gate
Your internal console uses real-time webhooks and status flags to report gateway health. A route marked as «Setup» means provisioning profiles are generated, but production traffic is blocked until security tests pass. Conversely, a «Live» status confirms that route health checks (HB) and balance checks are operational.
Deposit Thresholds and Soft Reviews
Prepaid balance management is central to the pilot workflow. Every platform account operates under a strict USD 20 prepaid floor to safeguard upstream routing and prevent negative balance exposure. When funds fall below this boundary, automated holds pause route dispatching without deleting configured templates.
JIT Number Allocation During Pilot
Rather than pre-purchasing virtual numbers, the platform relies on Just-In-Time (JIT) number provisioning. When a tenant requests a longcode or 10DLC identity, a prepaid hold triggers instant allocation from upstream pools. This eliminates stock holding costs and ensures clean sender reputations.
Status Comparison Table
| State | Operational Meaning | Tenant Visibility | Balance Impact |
|---|---|---|---|
| Setup | Profile built, testing pending | Hidden | Zero |
| Testing | HB and OTP synthetic checks | Admin only | Micro-charge |
| Live | Ready for client traffic | Visible | Active Hold |
| Hold | Below prepaid floor | Paused | Blocked |
Start with IOSOR
After the first workshop, open the catalog next to the dashboard. For each product the workshop called ready, read the catalog badge. Keep In setup until a delivered pilot send exists for that product. A workshop checkbox does not mint a Live debit.
Related: Catalog Incident Week: False Live During an Incident Still Must Not Debit Catalog invoice week: false Live must not bill as Live.
IOSOR takeaway
Do: treat pilot week as Live versus In setup on the catalog chip, not on the workshop slide. A delivered pilot send is the gate.
Don't: flip Live because the dashboard looks green after one workshop, or debit workshop traffic as production.
Was this guide helpful?
Related guides
- Gate Premium Catalog Features Behind Monthly Volume Thresholds
Learn how to secure high-throughput enterprise catalog SKUs by enforcing volume-based access gates for subaccounts within the IOSOR platform ecosystem.
- Configuring Multi-Currency Catalog Display Rules for International Resellers
Learn how to configure IOSOR catalog display rules to show native currency rates to subaccounts while maintaining a unified USD settlement ledger for global operations.
- Enforce Role-Based Access Controls for Catalog State and Pricing Edits
Secure your white-label CPaaS environment by restricting catalog configuration changes to authorized administrative roles, ensuring pricing and status integrity.