Digital services, product and partnerships teams
A customer wants useful AI in Kiswahili or Sheng, has no card, and will not create an account with a foreign provider.
The subscriber's own screen. The operator-side decision journey is not yet runnable.
Seen by the customer · App, Kiswahili
From the record, not a run: what would reach them, on App, Web, WhatsApp, USSD-assisted, in Kiswahili, English, Sheng.
What happened
A subscriber needs affordable everyday AI in a familiar language.
A customer wants useful AI in Kiswahili or Sheng, has no card, and will not create an account with a foreign provider.
What it reads
Checks before anything is sent
Identity, age, price, allowance, provider scope and consent 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
Operator billing reaches customers no card-based service can, and the operator keeps the customer relationship rather than renting it out.
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 subscriber needs affordable everyday AI in a familiar language. | Reads age and identity checks, balance and charging eligibility, language preference, existing entitlements. |
| The decisionThe decision to be made. | Nothing reaches the customer yet. | Selects the suitable AI package, language and governed inference route. |
| The safeguardsThe conditions that stop it. | Still nothing. No action is sent until every check has passed. | Identity, age, price, allowance, provider scope and consent pass. |
| The actionThe action that reaches the customer. | Quote, confirm, charge, entitle and open the operator-branded assistant. Reaches them on App, Web, WhatsApp, USSD-assisted, in Kiswahili, English, Sheng. | Recommends. The system that holds the right confirms, charges or provisions. |
| When it goes wrongRefusal, failure and recovery. | The charge is declined at the billing system after the customer has confirmed. | No entitlement is granted, the customer is told plainly what happened, and the assistant does not open until charging confirms. |
| The resultThe change it made. | What changed for them is what is counted; nothing else is claimed. | Subscription, tier upgrade and consumed retail credits. |
| The proofThe proof anyone can check. | Can be answered for, later, from the record. | Quote, consent, OCS charge, entitlement, provider route and usage receipt. |
Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.
What goes wrong
The charge is declined at the billing system after the customer has confirmed.
What happens then
No entitlement is granted, the customer is told plainly what happened, and the assistant does not open until charging confirms.
A package, a price, a confirmation and a receipt, with the operator's charging system deciding and the assistant opening only when the entitlement exists.
the provider routing and the controls behind the assistant
what happens when the credits run out mid-use
The subscriber's own screen. The operator-side decision journey is not yet runnable.