Hypothesis
A bundle that is used is renewed and earns its partner share; one that is not is a cancellation, a refund and a partner dispute.

Digital services, content and partnerships teams
A customer streams football every weekend on mobile data. A sports pass would save them money. Their plan does not include the partner app, and the pass cannot be cancelled from the app.
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, Web, SMS, USSD.
What happened
A customer's viewing, gaming or data pattern says a partner service would be used, or they ask for one.
A customer streams football every weekend on mobile data. A sports pass would save them money. Their plan does not include the partner app, and the pass cannot be cancelled from the app.
What it reads
Checks before anything is sent
Partner availability, rights, entitlement, device support, price, consent and cancellation terms 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 bundle that is used is renewed and earns its partner share; one that is not is a cancellation, a refund and a partner dispute.
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 viewing, gaming or data pattern says a partner service would be used, or they ask for one. | Reads viewing, gaming and data patterns, partner availability, rights and device support, entitlements already held, and price, consent and cancellation terms. |
| The decisionThe decision to be made. | The customer's screen is unchanged. | Ranks a content, sports or gaming bundle, a time-bound pass, the partner service alone, or no offer against entitlement, partner availability and price. |
| The safeguardsThe conditions that stop it. | Still unchanged: the action waits until every check has passed. | Partner availability, rights, entitlement, device support, price, consent and cancellation terms pass. |
| The actionThe action that reaches the customer. | Confirm one bundle or pass, activate the entitlement with the partner, and show how to cancel. Reaches them on App, Web, SMS, USSD. | Recommends. The system that holds the right confirms, charges or provisions. |
| When it goes wrongThe failure, and the recovery. | The bundle is charged and the partner's entitlement never activates, so the customer pays for a service they cannot open. | The charge settles only on the partner's activation confirmation, a failed activation reverses the charge with the reason, and the customer is told rather than left to find out. |
| The resultThe change it made. | What changed for them is what is counted; nothing else is claimed. | Activated bundles used in their first period, against cancellations and margin after the partner share. |
| The proofThe proof anyone can check. | Can be answered for, later, from the record. | Usage signal, partner availability, rights, quote, confirmation, activation, first use, cancellation and margin. |
Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.
What goes wrong
The bundle is charged and the partner's entitlement never activates, so the customer pays for a service they cannot open.
What happens then
The charge settles only on the partner's activation confirmation, a failed activation reverses the charge with the reason, and the customer is told rather than left to find out.
When viewing, gaming or data patterns say a partner service would be used, compare a bundle, a time-bound pass, the partner service alone and no offer, against entitlement, partner availability and price.
the partner terms, rights and settlement a bundle depends on
the data the bundle is used over
Available to see today
A pilot's requirements are specified: the data, the authority and the consent design.