Skip to content
HeuriTel
Sign in
Offer, Pack and Pricing Intelligence

Roaming & Travel

Sell the traveller the coverage that works where they land, before they leave.

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.

For Roaming, eSIM and travel product teams.

The decision, annotated from the record

A customer's booking, search or first foreign network attach says where they are going.

The roaming option that fits this destination, device and customer — pay-as-you-go included when it is the right answer.

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

Before anything reaches the customer: Destination coverage, device eSIM support, entitlement, price, consent and fraud checks pass.

What would reach them: Confirm one plan and activate it before or at first attach, with the price shown in the customer's own currency. On App, SMS, USSD, Web.

Annotated, not computed. No engine runs on this page. Read the journey in full

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

The journey below is written for a generic operator. Tell us your market and it will be presented in it.

Configure a demonstration
The decision

The roaming option that fits this destination, device and customer — pay-as-you-go included when it is the right answer.

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 roaming pack sized to the trip, activated before departure
  • A day pass that starts at first attach
  • An eSIM plan, where the device and the destination support it
  • No plan, with the pay-as-you-go rates shown before the border
What it does

Three things it helps you decide or do.

  • Read the trip, the device and the entitlement

    Destination, dates, eSIM support and the packs already held are what a roaming offer is judged on, before any price is quoted.

    • customer_id
    • account_type
    • tenure_days
    • active_products
    • recharge_30d
    • usage_30d
    • revenue_30d
    • last_contact
    • consent_status
    • outcome_label
  • Compare packs, passes, eSIM and pay-as-you-go

    Four ways to be connected abroad are ranked together, and the coverage, device, entitlement, price, consent and fraud checks can refuse any of them.

    • No consent
    • ineligible product
    • price/catalogue mismatch
    • contact cap
    • credit/fraud block
    • channel unavailable
    • control assignment
  • Confirm activation before the charge settles

    Quote, confirmation, activation and first use at the destination are recorded separately, so a plan sold is never counted as a traveller connected.

    • Decision log
    • eligibility snapshot
    • price/order response
    • delivery receipt
    • control assignment
    • revenue/outcome ledger
The journey

Help a traveller choose coverage that works where they land

No demonstration is configured for this product yet.

Roaming & Travel: the situation this product is about

Roaming, eSIM and travel product teams

StepWhat the customer experiencesWhat 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.

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

Assumptions, costs and the record’s five answers
  1. 01
    Desired result

    The result wanted.

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

  2. 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

  3. 03
    Evidence required

    The records kept to show it.

    Decision log; eligibility snapshot; price/order response; delivery receipt; control assignment; revenue/outcome ledger

  4. 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

  5. 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

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

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.
Technical detail

Inputs, decision logic, systems touched, records kept.

Four questions an evaluation asks in a different order every time. Every field is the workbook’s own, unedited.

What would we need from your systems, and how much history?

Attributes required

  • customer_id
  • account_type
  • tenure_days
  • active_products
  • recharge_30d
  • usage_30d
  • revenue_30d
  • last_contact
  • consent_status
  • outcome_label

Also useful, not required

  • Network experience
  • digital clickstream
  • complaints
  • location cohort
  • household/account links
  • partner purchases

8-12 weeks of customer, usage, revenue, product, contact and outcome history; stable customer key; one executable channel

The 12 definitions underneath

12 in this product

  1. HeuriTel RoamingDecision definitionHT-0304

    Identify eligible records for roaming, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0304
  2. HeuriTel Roaming PacksDecision definitionHT-0305

    Use customer affordability, usage, renewal and margin data to improve roaming packs while controlling cannibalisation and measuring incremental value.

    /d/HT-0305
  3. HeuriTel Roaming PersonalisationDecision definitionHT-0306

    Identify eligible records for roaming personalisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0306
  4. HeuriTel Roaming ActivationDecision definitionHT-0307

    Identify eligible records for roaming activation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0307
  5. HeuriTel Roaming UpsellDecision definitionHT-0308

    Identify eligible records for roaming upsell, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0308
  6. HeuriTel Roaming CareDecision definitionHT-0309

    Identify eligible records for roaming care, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0309
  7. HeuriTel Traveller DetectionDecision definitionHT-0310

    Identify eligible records for traveller detection, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0310
  8. HeuriTel Travel MarketplaceDecision definitionHT-0311

    Identify eligible records for travel marketplace, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0311
  9. HeuriTel eSIM TravelDecision definitionHT-0312

    Identify eligible records for esim travel, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0312
  10. HeuriTel Travel InsuranceDecision definitionHT-0313

    Identify eligible records for travel insurance, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0313
  11. HeuriTel Bill Shock Roaming PreventionDecision definitionHT-0314

    Identify eligible records for bill shock roaming prevention, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0314
  12. HeuriTel Inbound Roamer MonetisationDecision definitionHT-0315

    Identify eligible records for inbound roamer monetisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0315

Search definitions across every product

Implementing it

Four stages, and what has to be true before the next one starts.

12-16 weeks to pilot; 2-4 additional weeks per market after reusable interfaces exist. A team of 8 roles, named in the record rather than promised.

  1. 01

    Scope

    One use case, one value unit and a denominator finance has agreed to. Without these there is nothing a later result can be compared against.

    • Confirm value unit
    • select use case
    • baseline denominator
  2. 02

    Connect

    The attributes mapped from your systems, and the decision and outcome interfaces working in both directions.

    • map attributes
    • integrate decision and outcome APIs
  3. 03

    Validate

    Eligibility agreed, a dry run with nothing sent, then a controlled pilot with a holdout that is actually respected.

    • build eligibility
    • dry run
    • controlled pilot
  4. 04

    Operate

    The live loop: decide, check, execute through your systems, capture what came back, and measure against the control.

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

Who does it. 1 telecom product lead · 1 CVM specialist · 1 data engineer · 1 ML engineer · 1 integration developer · 0.5 QA · 0.5 DevSecOps · 1 deployment coordinator

Four states are tracked, and each is assessed against your systems.

Readiness is assessed per client: nothing is offered as pilot-ready until your data, your integration and your authority have been checked.

Readiness

Needs client data and integration review

The client’s data and integration position.
Runtime / build state

Target product definition

What exists as running software.
Surface state

Not audited

Whether this product shows the entry anywhere.
Client status

Not assessed

Where a named client has reached.

Next steps from here.

12 definitions sit under Roaming & Travel. The two links that matter first are the journey this page describes, and the rest of the family it belongs to.

See HeuriTel configured for your organisation

Verify your work email to open a demonstration configured for your organisation.