IOSOR

IOSOR Learn

Verify Corridor Degradation: Recovery Week Operations

Navigate the recovery week after a Verify corridor degradation. Rebuild OTP route health, honestly replay failed sessions, and reconcile prepaid balances using IOSOR's robust operational tools.

Verify Corridor Degradation: Recovery Week Operations.

1. Initial Assessment & Data Review

Following a Verify corridor degradation, the immediate recovery phase begins with a meticulous review of all incident data. Operators must access the IOSOR console to pull detailed DLR logs and webhook delivery statuses for the affected period. This involves cross-referencing SMS traffic volumes against successful OTP delivery rates. Identify specific E.164 number ranges or geographic regions that experienced the most significant impact. The goal is to establish a clear baseline of service interruption and pinpoint the exact moments of degradation and initial recovery.

2. OTP Route Health Restoration

Restoring OTP route health is paramount. This involves actively monitoring the performance of all assigned routes within the Verify cluster. Operators should initiate JIT (Just-In-Time) number assignments, ensuring that new numbers are provisioned with a prepaid hold, ready for immediate use. This process bypasses any potentially degraded routes by dynamically assigning fresh, healthy E.164 numbers. Thorough testing of these new routes with synthetic OTP messages is critical to confirm DLR receipt and webhook functionality.

3. Session Replay & DLR Reconciliation

An honest replay of failed OTP sessions is crucial for maintaining trust and accurate billing. For sessions that did not receive a Verify OK status or a final DLR, operators must carefully re-evaluate the original request parameters. The IOSOR platform allows for re-triggering specific OTP attempts, ensuring that the system attempts delivery through the newly verified healthy routes. Each replayed session's DLR must be meticulously reconciled against the original attempt.

4. Prepaid Ledger Adjustment & Review

Reconciling prepaid balances after a degradation incident requires careful attention. Failed OTP attempts that were billed but never delivered must be credited back to the customer's prepaid balance. The IOSOR ledger provides granular transaction details, allowing operators to identify and reverse charges for undelivered messages. It is essential to maintain transparency in these adjustments. For accounts with a prepaid floor of USD 20, ensure that any credits do not drop the balance below this operational minimum without explicit review.

5. Post-Incident Analysis & Reporting

The recovery week culminates in a comprehensive post-incident analysis. This involves compiling all data from the initial assessment, route restoration efforts, and session reconciliation.

Start with IOSOR

Log into the IOSOR console and open the Verify cluster route management tab to evaluate current DLR latency metrics. Apply JIT number assignment holds and trigger a controlled replay for unconfirmed sessions logged during the incident window. Complete the recovery cycle by running the ledger reconciliation tool to credit unverified attempts back to affected prepaid accounts.

IOSOR takeaway

Recovering from a corridor degradation requires strict alignment between DLR tracking, route health checks, and billing integrity. Replaying failed OTP sessions transparently while adjusting the prepaid ledger restores account trust without risking double-charging or message duplication.

Do re-verify webhook delivery hooks and route health before opening full throughput for live OTP sessions. Don't perform blanket automated session replays without first validating final DLR statuses and adjusting prepaid balances.

Was this guide helpful?

Related guides