- Challenge
- An account could use SIM call tracking or Airtel IQ cloud calling, never both. Switching meant reconfiguring the account.
- Approach
- One SIM / Cloud / Hybrid setting, an orchestrator that keeps both calling drivers live in one session, and a per-call choice of path.
- Impact
- Accounts run both calling paths at once with no reconfiguration, and every call records the path it used, so reports agree.
1One mode per account
Before: an account was set up for SIM call tracking or for cloud calling over Airtel IQ, never both.
2One setting
A single SIM / Cloud / Hybrid setting replaced the account-level either-or flag.
3Both drivers live
A session-preserving orchestrator keeps both calling drivers running without resetting the user session.
4Pick per call
A selector holds a default path, or overrides it for a single call.
5Reports match reality
Each call records which path it actually used, so logs, exports and dashboards agree.
Before
SIM tracking or cloud (Airtel IQ), never both, per account
After
Both simultaneously, one account, one session
- Attribution
- callMedium on activity and reports
Situation
Runo’s app already shipped two calling paths before this work started: native SIM-based call tracking, and cloud virtual numbers over Airtel IQ. The limitation wasn’t that these didn’t exist; it’s that an account could only run one of them:
Moving an account between modes, or adding a virtual number, meant reconfiguring the account, not a setting an operator could flip. Reporting also forked into parallel mode branches that didn’t agree on which medium a given call actually used.
Constraint
- Both calling paths must be usable on the same account at once, not just switchable
- Same behavior required on Android, iOS, and admin web
- Availability gated by role permissions and virtual-number allocations
- Workflow layer must not assume low-level transport details of each driver
Decision
Replace the account-level either/or flag with runtime state that lets both drivers be active on one session. A session-preserving orchestrator manages both channel drivers at once instead of gating one behind the other.
Primitives
- Enum model:
SIM/Cloud/Hybrid, replacing the account-level either/or flag - Driver orchestrator: keeps both channel drivers live on one session instead of one gating the other
CallMediumSelector: default or per-interaction override once both paths are availablecallMediumattribution: events, activity logs, exports, dashboards tagged with which path a call actually used
Tradeoff
Rejected alternative: keep the account-level either/or model and just make switching between them faster/lighter-weight. Simpler state model, but it doesn’t fix the actual limitation: accounts still couldn’t use both capabilities they already had.
The enum/orchestrator approach takes on real in-session concurrent-state handling complexity (two drivers genuinely live at once now, not one swapped for another), plus a one-time cleanup of legacy accounts sitting in inconsistent either/or states. Both real costs, taken deliberately in exchange for actually removing the exclusivity rather than making it more convenient to switch.
Evidence
- Accounts run SIM tracking and cloud telephony simultaneously, no account-level reconfiguration required
- Reporting uses one attribution field per call instead of parallel mode branches that could disagree
- Adding a virtual number or changing allocation no longer requires taking the other calling path away
The change is structural: the either/or is gone from the account model, so there is no mode switch left to make faster.




