Hypothesis
A device the customer can afford keeps them on the plan for the term; one they cannot is a return, a default or both.

Device, retail and channel teams
A customer's handset drops the network on 4G. The flagship on the shelf would sell, on instalments they cannot carry. A cheaper device would keep them on the plan they have.
A pilot's requirements are specified: the data, the authority and the consent design.
Seen by the customer · Retail
From the record, not a run: what would reach them, on Retail, App, Web, Dealer.
What happened
A customer's device is failing, cannot use the services they pay for, or they have asked about an upgrade.
A customer's handset drops the network on 4G. The flagship on the shelf would sell, on instalments they cannot carry. A cheaper device would keep them on the plan they have.
What it reads
Checks before anything is sent
Credit eligibility, stock, plan compatibility, price, consent and fraud checks pass.
Every option considered, including doing nothing
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.
The shape of the record, with no values. A reference appears only after a run is saved.
Hypothesis
A device the customer can afford keeps them on the plan for the term; one they cannot is a return, a default or both.
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.
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
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
| Step | What the customer experiences | What the operator does |
|---|---|---|
| The momentThe moment that started it. | A customer's device is failing, cannot use the services they pay for, or they have asked about an upgrade. | Reads device model, age and the network features it cannot use, credit eligibility from the credit system, not an inferred score, stock and delivery position from the order system, plan compatibility, consent and fraud state. |
| The decisionThe decision to be made. | The customer's screen is unchanged. | Ranks a device and plan pairing, an instalment offer, a certified pre-owned option or no offer against eligibility, stock and total cost. |
| The safeguardsThe conditions that stop it. | Still unchanged: the action waits until every check has passed. | Credit eligibility, stock, plan compatibility, price, consent and fraud checks pass. |
| The actionThe action that reaches the customer. | Present one device and plan with its total cost over the term, and place the order through the order and credit systems on acceptance. Reaches them on Retail, App, Web, Dealer. | Recommends. The system that holds the right confirms, charges or provisions. |
| When it goes wrongThe failure, and the recovery. | The instalment is approved and the device is out of stock in the customer's region, so the order sits open with a credit line committed. | Stock is confirmed before the credit line is committed, an order that cannot be fulfilled is released with the reason, and the customer is offered the device that can be delivered. |
| The resultThe change it made. | What changed for them is what is counted; nothing else is claimed. | Delivered devices on plans still active after ninety days, against total cost and returns. |
| The proofThe proof anyone can check. | Can be answered for, later, from the record. | Device signal, eligibility, stock, quote with total cost, credit decision, order, delivery and ninety-day status. |
Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.
What goes wrong
The instalment is approved and the device is out of stock in the customer's region, so the order sits open with a credit line committed.
What happens then
Stock is confirmed before the credit line is committed, an order that cannot be fulfilled is released with the reason, and the customer is offered the device that can be delivered.
When a handset fails or an upgrade is asked for, compare a device and plan pairing, an instalment offer, a certified pre-owned option and no offer, against credit eligibility, stock and total cost.
the credit decision an instalment offer depends on
the plan the device is paired with
Available to see today
A pilot's requirements are specified: the data, the authority and the consent design.