Roaming, eSIM and travel product teams

Help a traveller choose coverage that works where they land

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.

View requirements The product that runs it: Roaming & Travel

A pilot's requirements are specified: the data, the authority and the consent design.

Seen by the customer · App

From the record, not a run: what would reach them, on App, SMS, USSD, Web.

The case

Annotated from the record

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

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

Checks before anything is sent

Destination coverage, device eSIM support, entitlement, price, consent and fraud checks pass.

Every option considered, including doing nothing

A roaming pack sized to the trip, activated before departureConsidered
A day pass that starts at first attachConsidered
An eSIM plan, where the device and the destination support itConsidered
No plan, with the pay-as-you-go rates shown before the borderConsidered

Doing nothing is one of the outcomes, and it is recorded with its reason. The options are the record's own; a run decides between them.

Evidence record

Preview

Reference: The reference of the saved run.
Decision: One of the options, including no action, with the reason.
Checks: Destination coverage, device eSIM support, entitlement, price, consent and fraud checks pass.
Evidence kept: Destination signal
device capability
coverage
quote
confirmation
activation
first-use record
The measures: Activated plans used at the destination, against bill shock and pay-as-you-go complaints.
Connection: Written on every record: the systems the run read, and the sample it ran on.

The shape of the record, with no values. A reference appears only after a run is saved.

The improvement, and how it is measured

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.

Modelled

The mechanism that could produce the result, stated; the figure is measured in the pilot.

Observed

Measured in a pilot’s validate stage, on your systems, against a comparison agreed first.

The result, the mechanism, the measurement, and the record’s five answers

Desired result

Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails

Mechanism

Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain

Measurement

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

01
Desired result
The result wanted.
Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails
02
Mechanism
The mechanism that could produce it.
Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain
03
Evidence required
The records kept to show it.
Decision log; eligibility snapshot; price/order response; delivery receipt; control assignment; revenue/outcome ledger
04
Costs and risks
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
05
Measurement approach
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

Measured in the pilot's validate stage, on your systems, with the comparison agreed first. Every line above is the record's own design intent.

The business side

The change: Activated plans used at the destination, against bill shock and pay-as-you-go complaints.
Running cost: Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline
What evidence supports it: Destination signal, device capability, coverage, quote, confirmation, activation and first-use record.

The journey in detail

Step by step, from both sides

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.	The customer's screen is unchanged.	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 unchanged: the action waits 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.	Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongThe failure, and the 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.

The failure, and the recovery

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.

The products in this journey

Runs the decision
Roaming & Travel
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.
Contributes
Pack, Pricing & Recharge
the packs and day passes a roaming offer is sized from
Contributes
Devices & Handsets
whether this device can take the eSIM plan at all
The definition it demonstratesHeuriTel Roaming
Results it movesLaunch and monetise digital services · Grow customer revenue

Available to see today

A pilot's requirements are specified: the data, the authority and the consent design.

Request a working session