Rich incident week: session drop while the catalog still says Setup

Rich incident week: session drop while the catalog still says Setup.

First rich-channel incident reality check

When WhatsApp or RCS sessions drop mid-campaign while your brand portal still lists 'Setup', panic is the default white-label operator reaction. You stare at the dashboard wondering if your USD 20 prepaid floor balance or webhook heartbeat failed. Resist the urge to invent status updates. If upstream catalogs report deployment queues, never tell clients everything is fine. Honesty protects your merchant trust far better than a fake 'Live' badge during an outage.

Spotting the session drop symptoms

True session drops manifest as sudden DLR timeouts, spiking queue errors, and silent webhook failures. Before filing tickets, inspect your JIT number provisioning logs and prepaid credit hold states. If you run a high-volume setup nearing the USD 1,000/month soft review threshold, throttling rules might kick in unexpectedly. Check whether your traffic profile matches the nuances discussed in Rich second month: session vs template mix after month one.

The Setup status versus live reality

Clients hate ambiguity, but they hate false assurances more. When configuration status remains stubbornly on 'Setup' during a fire, explain the technical gate cleanly. Use this comparison table to guide your communications:

Differentiating channel failures

Not all messaging breakdowns carry the same operational weight. A rich media drop differs fundamentally from standard fallback routing. Review WhatsApp vs RCS when not live to understand how non-live states impact secondary delivery paths. When rich features stall, your fallback strategy must preserve core OTP integrity without blowing past expected thresholds.

Cost management during platform stalls

Incidents often distort financial tracking. When sessions freeze and queues stall, verify that template charges and active session windows are calculated accurately. Misunderstandings here bleed operator margins fast. Re-read template vs session cost to audit your billing rules while traffic is paused.

Start with IOSOR

Open the IOSOR console immediately to freeze active dispatch queues and inspect your webhook heartbeat logs for silent DLR timeouts. Verify whether JIT number provisioning is held up at the catalog verification gate despite local traffic dispatching. Clear stalled session holds manually before resuming outbound traffic to prevent cost leaks during platform stalls.

IOSOR takeaway

This incident breakdown proved that a portal status showing 'Setup' does not always mean zero traffic activity, just as dropping sessions do not automatically indicate a revoked profile. Silent webhook timeouts and JIT provisioning gates often desynchronize live routing from catalog UI states during high-volume spikes.

Do audit your webhook error queues and session hold states the moment DLRs stall during major campaigns. Don't promise clients immediate live delivery based on portal UI indicators alone without confirming underlying channel gateway health.