IOSOR Learn
DLR incident week: unknown spike is a stop line
How to handle your first delivery receipt unknown share spike on prepaid CPaaS without waiting for invoice shock.
An unknown DLR spike in incident week is a stop line: freeze outbound now.
First DLR incident: unknown share is freeze, not wait for the next bill
When your platform dashboard shows an unexpected surge in unknown delivery receipt statuses during a campaign, treating it as a minor tracking glitch is a costly mistake. For white-label resellers, an unverified spike means traffic is burning funds without clear delivery proof. You need an immediate traffic pause to protect client prepaid balances.
Spotting the root cause before balances drain
Unknown statuses typically indicate upstream gateway timeout issues, silent route drops, or carrier filtering. Because you operate on a prepaid model, every single undelivered OTP or promotional SMS sitting in limbo depletes client funds. Check your gateway logs, verify webhook endpoints, and inspect recent route updates.
The USD 20 prepaid floor and soft review trigger
Maintaining strict financial controls starts with your baseline funding. Enforce a mandatory USD 20 prepaid floor for all new sub-accounts to prevent rapid negative balances during traffic anomalies. When a client scales and approaches USD 1,000/month in volume, initiate a proactive soft review of their sender ID registration and message templates.
Managing numbers with JIT and instant assignment
Resource allocation must remain entirely digital. Use Just-In-Time provisioning combined with instant prepaid holds to assign phone numbers or 10DLC brands instantly. There is no physical inventory or shipping lag; numbers activate the moment funds clear.
Preventive habits and avoiding invoice surprises
Do not wait until the end of the billing cycle to investigate anomaly patterns. Review our guide on the DLR second month: unknown share that became a habit to spot recurring operational traps before they become systemic. Early detection safeguards margins and prevents painful disputes.
Start with IOSOR
Freeze outbound on the unknown-spike class this hour. Export the first unknown stamp, the corridor, and who owns the freeze. Do not wait for invoice week to notice the burn. Unknown is not still in flight while prepaid keeps debiting. This week is a send stop, not a reprint and not a habit review.
Related: undelivered, rejected, expired DLR invoice week: unknown share is not delivered.
IOSOR takeaway
An unknown DLR spike is a freeze, not a tracking glitch you bill later.
Do: pause the class, export the spike window, and name the freeze owner.
Don’t: keep sending hoping DLR arrives, or park the spike for invoice week.
Was this guide helpful?
Related guides
- Comparing Deliverability Metrics Across Short Code and Toll-Free Routes
Analyze SMS deliverability metrics between short codes and toll-free numbers for white-label CPaaS clients, detailing filtering and DLR tracking.
- Establishing Baseline Deliverability Metrics During New Route Pilots
Run rigorous delivery test suites, analyze carrier performance, and establish baseline messaging metrics before scaling your white-label traffic on new routes.
- Auditing Delivery Rates and Clearing Queues After Network Maintenance
Step-by-step technical playbook for platform managers to verify route health and flush delayed DLR queues safely after carrier and telecom network maintenance windows.