Before
SIM tracking and cloud (Airtel IQ): one or the other, per account
After
Both simultaneously, one account, one session
- Attribution
- callMedium threaded through activity and reports
Milestone Timeline
Exclusivity audit
Confirmed SIM tracking and cloud (Airtel IQ) telephony were mutually exclusive per account: switching or adding a virtual number meant reconfiguring the account, not a toggle.
Unified state model
Replaced the either-or account flag with a single SIM / Cloud / Hybrid enum so both paths can be active on one account.
In-app selector and attribution
Shipped CallMediumSelector and threaded callMedium through logs and analytics so reporting reflects which path an actual call used.
What it does
Before this work, Runo’s app already had both calling paths built: native SIM-based call tracking, and cloud virtual numbers over Airtel IQ. They just couldn’t be used together. An account was configured for one or the other: a customer on SIM tracking had no access to cloud calling features, and vice versa. Switching which mode an account used, or adding a virtual number, meant reconfiguring the account itself, not flipping a setting in the app.
The fix unifies both into one account-level capability: a single account can use SIM tracking and cloud telephony simultaneously, in the same session, rather than being locked into whichever one it was set up with. “Hybrid” now describes what actually happens (both paths available together) instead of a runtime switch between two modes that were still, underneath, exclusive.
The constraints, design decisions and outcomes are in the full case study.
What it demonstrates
- Correcting a product limitation that had been built into the account model, not just the UI
- State-machine modeling for a capability moving from mutually-exclusive to simultaneous
- End-to-end attribution so reporting matches how calls actually happened, not which mode the account was nominally in


