Skip to content
HeuriTel
Sign in

Commercial, CVM and retention teams

Recover a customer who has quietly stopped buying data packs

A customer who bought a data pack every month for a year has bought nothing for six weeks. Nothing has broken and nobody has complained.

Runs end to end, configured for your organisation and market.

Seen by the customer · App, Kiswahili

Sample message. Channel, language and wording come from the market's records.

The case

Ready to decide

What happened

Recharge, pack or usage value deteriorates beyond a personal baseline.

A customer who bought a data pack every month for a year has bought nothing for six weeks. Nothing has broken and nobody has complained.

What it reads

  • Recharge and pack history
  • Recent usage against the pack they were buying
  • Service quality in their area
  • Contact permission and recent contact

Checks before anything is sent

Marketing consent: permitsConsent and preference system
Contact frequency: permitsCampaign management system
Fair value: permitsProduct catalogue and pricing
Margin floor: permitsCommercial finance
Open service case: permitsCare and service management

Every option, and where the ranking landed

  1. Offer a pack that matches how they actually use dataChosen Small weekly pack · 190
  2. Discount the pack they were already buyingPermitted Monthly pack · 900
  3. Check for a service or coverage problem firstPermitted
  4. Take no action, and record whyPermitted

No action is a valid outcome, and it is recorded with its reason. Sample records, computed in your browser. Every check permits it, so the ranking chose the option worth the most to both sides.

Evidence record

Preview
Reference
Issued when a run is saved. An evaluation that was never saved has none.
Decision
Offer a pack that matches how they actually use data, with the reason.
Checks
Consent, pressure, care, affordability, margin and holdout checks pass.
Evidence kept
  • Cohort definition
  • model version
  • policy decision
  • assignment
  • outcome
The measures
Accepted, provisioned save and incremental contribution.
Connection
Stated on every record. In the demonstration no operator system is connected, and each record carries that state.

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

A customer who is drifting away is cheaper to keep than to replace, and an offer sent over an unresolved fault costs more than it earns.

Desired result: Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails

Modelled not observed

A run on the sample records shows the decision, the checks it passed and the receipt the responsible system would return. No incremental value is modelled on this page.

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

Assumptions, costs and the record’s five answers
  1. 01
    Desired result

    The result wanted.

    Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails

  2. 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

  3. 03
    Evidence required

    The records kept to show it.

    Decision log; eligibility snapshot; price/order response; delivery receipt; control assignment; revenue/outcome ledger

  4. 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

  5. 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

A saved run keeps the decision and its receipt: what was decided, which checks refused, and what the responsible system returned. It does not show incremental value. That needs the comparison above, over an agreed period, against a baseline finance has accepted.

The business side

The change
Accepted, provisioned save and incremental contribution.
Running cost
Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline
What evidence supports it
Cohort definition, model version, policy decision, assignment and outcome.

The journey in detail

Step by step, from both sides
StepWhat the customer experiencesWhat the operator does
The momentThe moment that started it.Recharge, pack or usage value deteriorates beyond a personal baseline.Reads recharge and pack history, recent usage against the pack they were buying, service quality in their area, contact permission and recent contact.
The decisionThe decision to be made.Nothing reaches the customer yet.Ranks a fair-value treatment, care-first action or no-action alternative.
The safeguardsThe conditions that stop it.Still nothing. No action is sent until every check has passed.Consent, pressure, care, affordability, margin and holdout checks pass.
The actionThe action that reaches the customer.Present a controlled offer and provision only after confirmation. Reaches them on App, SMS, WhatsApp, USSD, in Kiswahili, English.Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongRefusal, failure and recovery.The customer has an open service fault, so a commercial offer would arrive while their service is still broken.The care gate stops the offer, routes the case to service recovery, and the commercial decision waits until the fault is closed.
The resultThe change it made.What changed for them is what is counted; nothing else is claimed.Accepted, provisioned save and incremental contribution.
The proofThe proof anyone can check.Can be answered for, later, from the record.Cohort definition, model version, policy decision, assignment and outcome.

Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.

Refusal, failure and recovery

What goes wrong

The customer has an open service fault, so a commercial offer would arrive while their service is still broken.

What happens then

The care gate stops the offer, routes the case to service recovery, and the commercial decision waits until the fault is closed.

The products in this journey

See it run

The demonstration follows the same journey end to end: what the customer sees, what the operator decided, and the evidence behind it.

Open simulation

Verified work email required.

Request a working session

See HeuriTel configured for your organisation

Verify your work email to open a demonstration configured for your organisation.