Control New Catalog Product Visibility via Subaccount Feature Flags

Managing product visibility across multiple tenants requires a precise approach to avoid overwhelming users with irrelevant services. By utilizing feature flags within the IOSOR dashboard, you can toggle specific catalog entries for individual subaccounts without impacting the global platform state. This JIT method ensures that only authorized clients see new modules, maintaining a clean and professional interface.

Configuring Feature Flags for Subaccount Access.

To manage product visibility, navigate to the IOSOR dashboard and access the Subaccount Management module. Feature flags allow you to toggle specific catalog entries for individual tenants without affecting the global platform state. Select the target subaccount and locate the 'Features' tab to enable or disable specific product modules. This JIT approach ensures that new services are only visible to authorized clients, maintaining a clean interface for your end-users.

Managing Beta Tiers and Early Access

When launching new communication features, use the feature flag system to create beta tiers. By assigning specific flags to high-value accounts, you can test new functionality before a full rollout. Ensure that your subaccounts maintain a USD 20 prepaid floor to keep services active during these pilot phases. This granular control prevents unauthorized access to experimental features while allowing you to gather feedback from selected partners.

Scaling Rollouts Across the Platform

Once testing is complete, you can toggle the feature flag globally or for specific segments. This transition is direct, as the IOSOR ledger handles the provisioning of new services instantly. If a client scales their usage beyond USD 1,000/month, a soft review of their account settings is recommended to optimize their configuration. This process ensures that your platform remains stable while introducing new catalog items.

Handling Provisioning and E.164 Compliance

Every product entry in the catalog is linked to specific provisioning logic. When a feature flag is enabled, the system triggers the JIT allocation of resources. Ensure that all numbers assigned to these new products comply with E.164 standards. The platform automatically handles the prepaid hold for these resources, ensuring that your subaccounts have sufficient balance before the service goes live.

Integrating Webhooks and DLR Tracking

For new catalog products, ensure your developers have configured the necessary webhooks to track DLR and OTP delivery status. Proper integration is critical for maintaining service quality. Refer to these guides for technical implementation:

• Catalog Pilot Week: Live vs Setup After First Workshop
• Second catalog product: badge handover
• API Pilot Week: Keys and Webhooks on Live Traffic.

Start with IOSOR

Open the IOSOR console, head to Subaccount Management, and assign your beta feature flags to target client tiers before pushing catalog updates live. Map your JIT provisioning webhooks and verify E.164 number formats across enabled subaccounts. Validate DLR tracking endpoints to ensure real-time reporting operates correctly during phased tenant rollouts.

IOSOR takeaway

Phased catalog deployment isolates risk when introducing new communication products across multi-tenant environments. Toggling feature flags at the subaccount level allows your team to validate resource allocation, compliance checks, and delivery hooks in production with trusted beta users before full market exposure.

Do establish clear feature-flag criteria for beta tiers and monitor DLR delivery webhooks continuously during staged rollouts. Don't enable new catalog entries globally across all subaccounts without first verifying JIT provisioning logic and E.164 endpoint validation.