Digital services, product and partnerships teams

Sell everyday AI access on the phone bill, in the customer's own language

A customer wants useful AI in Kiswahili or Sheng, has no card, and will not create an account with a foreign provider.

Open preview

Verified work email required.

The product that runs it: Subscriber AI Services

The subscriber's own screen. The operator-side decision journey is not yet runnable.

Seen by the customer · App

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

The case

Annotated from the record

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

Age and identity checks
Balance and charging eligibility
Language preference
Existing entitlements

Checks before anything is sent

Identity, age, price, allowance, provider scope and consent pass.

Every option considered, including doing nothing

A short trial the customer confirms before any chargeConsidered
A weekly or monthly package with a clear allowanceConsidered
A shared household packageConsidered
Take no action, and record whyConsidered A valid outcome

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: Identity, age, price, allowance, provider scope and consent pass.
Evidence kept: Quote
consent
OCS charge
entitlement
provider route
usage receipt
The measures: Subscription, tier upgrade and consumed retail credits.
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

Operator billing reaches customers no card-based service can, and the operator keeps the customer relationship rather than renting it out.

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: Subscription, tier upgrade and consumed retail credits.
Running cost: Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline
What evidence supports it: Quote, consent, OCS charge, entitlement, provider route and usage receipt.

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 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.	The customer's screen is unchanged.	Selects the suitable AI package, language and governed inference route.
The safeguardsThe conditions that stop it.	Still unchanged: the action waits 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.	Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongThe failure, and the 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.

The failure, and the recovery

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.

The products in this journey

Runs the decision
Subscriber AI Services
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.
Contributes
AI Operations & Governance
the provider routing and the controls behind the assistant
Contributes
Real-Time Revenue Moments
what happens when the credits run out mid-use
The definition it demonstratesHeuriTel AI Subscription
Results it movesLaunch and monetise digital services · Grow customer revenue

Available to see today

The subscriber's own screen. The operator-side decision journey is not yet runnable.

Open preview Request a working session