Acquisition, dealer and digital-channel teams
A prospect has been qualified through a dealer. The incentive would win the sale. Half the connections won that way last quarter were inactive within ninety days.
A pilot's requirements are specified: the data, the authority and the consent design.
Seen by the customer · Retail, Kiswahili
From the record, not a run: what would reach them, on Retail, Dealer, Web, USSD, in Kiswahili, English.
What happened
A prospect is qualified through a dealer, a port-in request or a digital lead.
A prospect has been qualified through a dealer. The incentive would win the sale. Half the connections won that way last quarter were inactive within ninety days.
What it reads
Checks before anything is sent
Consent to contact, duplicate identity, eligibility, incentive budget and dealer terms 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
A connection that leaves within a quarter cost the incentive and the dealer commission and earned nothing; acquisition is measured on who stays, not on who signed.
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 prospect is qualified through a dealer, a port-in request or a digital lead. | Reads prospect source and how it was qualified, consent to contact and duplicate identity checks, likely value from comparable customers, incentive budget and dealer terms. |
| The decisionThe decision to be made. | Nothing reaches the customer yet. | Ranks a first offer, a channel and an incentive against the prospect's likely value and the cost of acquiring them. |
| The safeguardsThe conditions that stop it. | Still nothing. No action is sent until every check has passed. | Consent to contact, duplicate identity, eligibility, incentive budget and dealer terms pass. |
| The actionThe action that reaches the customer. | Present one first offer through the permitted channel and activate the connection on acceptance. Reaches them on Retail, Dealer, Web, USSD, in Kiswahili, English. | Recommends. The system that holds the right confirms, charges or provisions. |
| When it goes wrongRefusal, failure and recovery. | The prospect is an existing customer under a second identity, and the incentive would pay for a connection the operator already has. | The duplicate check stops the incentive, the dealer sees the reason, and the prospect is offered a legitimate second-line product instead. |
| The resultThe change it made. | What changed for them is what is counted; nothing else is claimed. | Activated connection still active and spending after ninety days, against acquisition cost. |
| The proofThe proof anyone can check. | Can be answered for, later, from the record. | Prospect source, consent, duplicate check, offer rationale, incentive, activation 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 prospect is an existing customer under a second identity, and the incentive would pay for a connection the operator already has.
What happens then
The duplicate check stops the incentive, the dealer sees the reason, and the prospect is offered a legitimate second-line product instead.
When a prospect is qualified, compare the standard offer, a smaller incentive, a cheaper channel and no incentive, against likely value and the cost of the acquisition.
the first pack a new customer is offered
the duplicate-identity and dealer checks an incentive depends on
A pilot's requirements are specified: the data, the authority and the consent design.