Coverage Second Month: Managing Uncovered Prefixes

By the second month on the IOSOR platform, routing strategy must transition from row-by-row invoice fixes to structured zone management. Prefixes left without explicit zone mapping automatically revert to default fallback rates, raising costs for SMS and OTP traffic. Grouping these recurring prefixes into dedicated zones while maintaining the USD 20 prepaid floor secures reliable delivery at predictable rates.

Transitioning from Invoice Rows to Zone Management

By the second month of operations on the IOSOR platform, the administrative focus shifts from reactive troubleshooting to proactive zone optimization. During the initial setup, you likely focused on Coverage invoice week: uncovered rejects on the bill to ensure immediate delivery. Now, the objective is to identify prefixes that appeared in your billing history but were not explicitly mapped to a specific pricing or routing zone. This is a structural job: you are moving away from reconciling individual rows and toward defining zones.

Analyzing Prefixes Billed Without Zone Mapping

When a prefix is not assigned to a specific zone, it typically falls into a catch-all category, often referred to as the WORLD gate. While this ensures that SMS and OTP traffic continue to flow, it can lead to unpredictable costs. Reviewing the previous month's billing data allows you to spot these outliers. If a specific prefix shows consistent volume, it should be moved out of the general pool and into a dedicated zone. This prevents the Zone vs WORLD gate before production logic from defaulting to the highest possible rate.

Maintaining the USD 20 Prepaid Floor for Coverage

To ensure that your zone adjustments and prefix mapping remain active, your account must maintain the USD 20 prepaid floor. This minimum balance acts as a buffer for the JIT (Just-In-Time) number assignment process. When you identify an uncovered prefix and decide to assign a dedicated number for it, the system places a prepaid hold on your balance. Without maintaining this floor, the automated assignment of resources for new prefixes may fail, leading to DLR errors and dropped traffic during the transition phase.

Scaling Toward the USD 1,000 Soft Review Threshold

As your traffic patterns stabilize and you refine your prefix mapping, your monthly spend will likely increase. IOSOR implements a soft review near USD 1,000/month. This is not a hard cap but a manual sanity check to ensure your zone configurations are optimized for your actual volume. During this review, we look at your Coverage volume review: uncovered still rejects metrics to verify that the prefixes you have recently moved from the WORLD gate into specific zones are performing efficiently.

Technical Implementation of JIT and HB Logic

Mapping a prefix is more than just a pricing change; it affects the technical telemetry of your traffic. When a prefix is correctly zoned, the platform can better optimize the HB (heartbeat) monitoring for that specific route. For 10DLC or international SMS, the JIT assignment logic ensures numbers are only provisioned when needed, reducing idle costs.

Start with IOSOR

In month two, pull the same uncovered prefixes that printed as reject last month. If they still hit WORLD fallback, that is mapping debt — schedule a zone row or keep them rejected. Do not wait for next invoice week to discover the same prefix again.

IOSOR takeaway

Second month is a prefix-watch habit, not another invoice surprise.

Do: keep a living list of prefixes that hit WORLD two months running.

Don’t: treat recurring WORLD-fallback hits as one-off bill noise.