Reinstating Suspended Sub-Tenants After Compliance Clearance

Reinstating Suspended Sub-Tenants After Compliance Clearance.

Verifying Compliance Clearance Status

Once a sub-tenant has successfully passed the internal audit, the compliance team updates the status flag within the IOSOR dashboard. You must verify that the specific sub-tenant ID is marked as 'Cleared' in the ledger before initiating any restoration. Ensure that all flagged traffic patterns have been addressed and that the sub-tenant has acknowledged the updated usage policy. This step prevents immediate re-suspension due to lingering policy violations.

Restoring Messaging Path Connectivity

After clearance, navigate to the sub-tenant management console to toggle the messaging path status from 'Suspended' to 'Active'. This action triggers a JIT provisioning sequence that re-establishes the DLR and webhook endpoints. Verify that the E.164 routing tables are correctly mapped to the sub-tenant's current balance. If the sub-tenant was previously disabled due to a low balance, ensure they have met the USD 20 prepaid floor requirement to resume service.

Re-enabling OTP and Verify Services

With the messaging path live, you must manually re-enable the OTP and Verify services if they were disabled during the isolation phase. Check the sub-tenant configuration to ensure that the STOP command logic is correctly applied to all active sender IDs. This ensures that end-user opt-out requests are processed correctly, maintaining compliance with global messaging standards. Test the flow with a single message to confirm delivery.

Managing Financial Thresholds and Limits

Review the sub-tenant's financial settings to ensure that the account is properly funded. For sub-tenants approaching a soft review near USD 1,000/month, verify that their credit limits are adjusted to prevent future automated suspensions. Monitor the ledger for any pending MRC charges that might trigger a negative balance immediately upon reactivation. Proper financial hygiene is critical for maintaining long-term sub-tenant stability.

Required Documentation and Recovery Links

To ensure full alignment with our operational standards, review the following documentation regarding tenant safety and incident management protocols:

• Partner Recovery Week: Reopen Tenant Exports Only When Isolation Holds
• Partner incident week: isolation break is a freeze, not a shared export
• Compliance Recovery Week: Reopen Traffic Only When Evidence Pack Exists

Start with IOSOR

Open the IOSOR sub-tenant management console and verify that the compliance clearance status flag displays 'Cleared' in the audit ledger. Toggle the messaging path from 'Suspended' to 'Active' to trigger the JIT provisioning sequence for DLR and webhook endpoints. Finally, re-enable the OTP and Verify services while confirming E.164 routing table accuracy across all active sender IDs.

IOSOR takeaway

Reinstating a suspended sub-tenant requires a structured sequence starting with verified compliance clearance before restoring live traffic. Unfreezing messaging paths and JIT webhooks without validating ledger status risks re-triggering automated safety holds or leaking unverified traffic across active corridors.

Do check that E.164 routing tables, OTP services, and credit limits are aligned in the console before making the messaging path live. Don't restore outbound traffic manually until the compliance ledger explicitly flags the sub-tenant account as cleared and STOP command logic is validated.