Roaming, eSIM and travel product teams
A customer has a flight tomorrow. Their phone supports eSIM. Last trip, they turned data off at the border and bought a local SIM at the airport.
A pilot's requirements are specified: the data, the authority and the consent design.
Seen by the customer · App, Kiswahili
From the record, not a run: what would reach them, on App, SMS, USSD, Web, in Kiswahili, English.
What happened
A customer's booking, search or first foreign network attach says where they are going.
A customer has a flight tomorrow. Their phone supports eSIM. Last trip, they turned data off at the border and bought a local SIM at the airport.
What it reads
Checks before anything is sent
Destination coverage, device eSIM support, entitlement, price, consent and fraud checks pass.
Every option considered, including doing nothing
No action is a valid outcome, and it is recorded with its reason. Nothing is computed on this page: the options are the record's own, and no run has decided anything.
The shape of the record, with no values. A reference appears only after a run is saved.
Hypothesis
A traveller who lands with working data spends on the operator's plan; one who lands without it buys a local SIM and remembers why.
Desired result: Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails
Modelled not observed
No figure is modelled for this journey. The mechanism that could produce the result is stated instead.
Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain
Observed
Nothing yet. Measurement begins in a pilot’s validate stage, on your systems, against a comparison agreed first.
Randomised holdout where feasible; intent-to-treat primary view; pre-declared denominator; guardrails for complaints, margin and opt-out
Measured on: Eligible population; treatment rate; conversion; incremental revenue; ARPU; churn; contact rate; margin; opt-out; decision latency
The result wanted.
Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails
The mechanism that could produce it.
Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain
The records kept to show it.
Decision log; eligibility snapshot; price/order response; delivery receipt; control assignment; revenue/outcome ledger
The cost, and the ways it can go wrong.
Costs: Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline
If it fails: Fail closed on eligibility/consent/price; queue retryable events; do not duplicate orders; route exception to campaign operations
The measure that shows it helped.
Randomised holdout where feasible; intent-to-treat primary view; pre-declared denominator; guardrails for complaints, margin and opt-out
Measured on: Eligible population; treatment rate; conversion; incremental revenue; ARPU; churn; contact rate; margin; opt-out; decision latency
Nothing has been observed for this product. Every line above is the record's own design intent; measurement begins in a pilot's validate stage, on your systems, with the comparison agreed first.
The business side
| Step | What the customer experiences | What the operator does |
|---|---|---|
| The momentThe moment that started it. | A customer's booking, search or first foreign network attach says where they are going. | Reads destination and dates, from the booking, the search or the first attach, device esim support and network compatibility, entitlements and packs already held, consent, credit and fraud state. |
| The decisionThe decision to be made. | Nothing reaches the customer yet. | Ranks a roaming pack, a day pass, an eSIM plan or pay-as-you-go against the destination, the device and the entitlements held. |
| The safeguardsThe conditions that stop it. | Still nothing. No action is sent until every check has passed. | Destination coverage, device eSIM support, entitlement, price, consent and fraud checks pass. |
| The actionThe action that reaches the customer. | Confirm one plan and activate it before or at first attach, with the price shown in the customer's own currency. Reaches them on App, SMS, USSD, Web, in Kiswahili, English. | Recommends. The system that holds the right confirms, charges or provisions. |
| When it goes wrongRefusal, failure and recovery. | The plan is sold and paid for, and the partner network at the destination does not attach the device. | Activation is confirmed against the partner network before the charge settles, a failed attach reverses the charge with the reason, and the customer is told the pay-as-you-go position rather than left offline. |
| The resultThe change it made. | What changed for them is what is counted; nothing else is claimed. | Activated plans used at the destination, against bill shock and pay-as-you-go complaints. |
| The proofThe proof anyone can check. | Can be answered for, later, from the record. | Destination signal, device capability, coverage, quote, confirmation, activation and first-use record. |
Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.
What goes wrong
The plan is sold and paid for, and the partner network at the destination does not attach the device.
What happens then
Activation is confirmed against the partner network before the charge settles, a failed attach reverses the charge with the reason, and the customer is told the pay-as-you-go position rather than left offline.
When a booking, a search or a first foreign attach says where a customer is going, compare a pack, a day pass, an eSIM plan and pay-as-you-go against the destination, the device and what they already hold.
the packs and day passes a roaming offer is sized from
whether this device can take the eSIM plan at all
A pilot's requirements are specified: the data, the authority and the consent design.