Broadband, fibre and fixed-wireless teams
A household wants fibre. The map says the street is covered. The last three orders on that street were cancelled after the installer found no port.
A pilot's requirements are specified: the data, the authority and the consent design.
Seen by the customer · Web, Kiswahili
From the record, not a run: what would reach them, on Web, App, Retail, Call, in Kiswahili, English.
What happened
A household asks for broadband, or a mobile customer's home usage says they need it.
A household wants fibre. The map says the street is covered. The last three orders on that street were cancelled after the installer found no port.
What it reads
Checks before anything is sent
Address serviceability, installation capacity, plan eligibility, price, consent and credit checks 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
An installed service is a household kept for years; a sale that cannot be installed is a cancellation and a complaint on the same day.
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 household asks for broadband, or a mobile customer's home usage says they need it. | Reads address serviceability from the network's own records, installation capacity and appointment availability, household usage and plan eligibility, consent, credit and the services already held. |
| The decisionThe decision to be made. | Nothing reaches the customer yet. | Ranks fibre, fixed wireless, a mobile-data fallback or no offer against serviceability at the address. |
| The safeguardsThe conditions that stop it. | Still nothing. No action is sent until every check has passed. | Address serviceability, installation capacity, plan eligibility, price, consent and credit checks pass. |
| The actionThe action that reaches the customer. | Offer the service the address can take, book the installation, and confirm the plan only when the appointment exists. Reaches them on Web, App, Retail, Call, in Kiswahili, English. | Recommends. The system that holds the right confirms, charges or provisions. |
| When it goes wrongRefusal, failure and recovery. | The sale is confirmed on the map's coverage, and the installer finds no port; the customer has already cancelled their previous provider. | The plan is confirmed only when the appointment exists, a failed installation is recorded against the address rather than the customer, and the fallback is offered before the previous service is cancelled. |
| The resultThe change it made. | What changed for them is what is counted; nothing else is claimed. | Installed and active services, against sales that could not be installed. |
| The proofThe proof anyone can check. | Can be answered for, later, from the record. | Address, serviceability result, plan quote, appointment, installation record, activation and first month. |
Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.
What goes wrong
The sale is confirmed on the map's coverage, and the installer finds no port; the customer has already cancelled their previous provider.
What happens then
The plan is confirmed only when the appointment exists, a failed installation is recorded against the address rather than the customer, and the fallback is offered before the previous service is cancelled.
When a household asks for broadband, compare fibre, fixed wireless, a mobile fallback and no offer against serviceability, installation capacity and what the household needs.
where the serviceability gaps the offer keeps meeting should be built out
where a failed installation becomes a case with an owner
A pilot's requirements are specified: the data, the authority and the consent design.