Cracking Zain: Restoring Voice Reach to Iraqi Leads

How targeted route engineering and continuous Caller ID rotation took an e-commerce client’s Iraq outreach from unreachable to a stable 60%+ ASR

Client Snapshot

The client is a fast-growing e-commerce platform expanding its outbound sales and customer-contact operations into new Middle Eastern markets, including Iraq. Voice contact with inbound leads is central to their conversion funnel — if a call doesn’t connect, the lead goes cold.

The Challenge

As the client scaled outreach to leads on Iraq’s Zain network, connection rates collapsed. Calls were going out but simply weren’t landing: numbers were being silently filtered, mislabeled, or dropped before they ever rang through. The pattern pointed to Zain’s network-level spam-detection systems, which had begun flagging the client’s outbound Caller IDs as suspicious or high-volume nuisance traffic — a common outcome when routes and CLIs aren’t matched to how a destination network actually screens traffic.

The business impact was immediate: leads that had already shown intent were going unreached, sales cycles were stalling, and the client had no visibility into why performance had fallen off so sharply.

Diagnosis

Our routing engineering team audited the client’s Iraq traffic lane end to end — termination routes, Caller ID sourcing, and call-completion data broken out by network. The data confirmed the suspicion: Zain specifically, more than other Iraqi carriers, was aggressively filtering the client’s existing CLIs. Generic or previously overused Caller IDs had accumulated a poor trust profile with Zain’s filtering logic, and no amount of retrying the same numbers was going to fix that.

The Solution

Rather than treat this as a one-time fix, we approached it as a routing and reputation problem that needed active management:

• Sourced dedicated termination routes into Zain paired with Saudi Arabia–registered Caller IDs that tested cleanly against Zain’s filtering and consistently completed calls.
• Validated each new route and CLI batch against live call-completion data before scaling volume onto it, rather than assuming a route would hold.
• Built a continuous CLI rotation process: as individual Caller IDs showed early signs of degradation, they were proactively retired and replaced with fresh, tested numbers — before performance visibly dropped.
• Put ongoing ASR monitoring in place on the Zain lane specifically, with a defined action threshold, so the route mix is adjusted before the client ever notices an issue.

The Results

The client’s Zain lane moved from largely unreachable to a stable, revenue-supporting channel:

• Answer Seizure Ratio (ASR) restored and consistently maintained above 60% on Zain — in line with healthy performance on the client’s other Iraqi carrier lanes.
• Lead outreach on Zain became reliable again, removing the dead zone that had been quietly costing the client conversions.
• A repeatable CLI rotation process is now running in the background, so performance stays durable rather than degrading again over time.

Why It Worked

Spam-filtering on networks like Zain isn’t a single switch — it’s an evolving trust score applied per Caller ID. Fixing it required routes and CLIs suited to how that specific network evaluates traffic, plus a standing process to keep replacing numbers as they age out, instead of a one-off swap that would have degraded again within weeks.

Looking Ahead

This same route-engineering and CLI-rotation approach now underpins the client’s outreach across other spam-sensitive networks in the region, giving them a repeatable playbook rather than a single fix.