The offer a customer who cannot transact can still take, and the way they pay for it.
A customer's data has run out. They cannot browse, cannot reach the app, and have no credit to buy more.
A small emergency allowance repaid on next recharge
A pack purchasable without data, through the portal itself
A partner-funded option where one applies
What it does
Three things it helps you decide or do.
Detect the moment and read what is permitted
The exhausted allowance or blocked session is the trigger; balance, eligibility and consent decide what may be offered at all.
customer_id
account_type
tenure_days
active_products
recharge_30d
usage_30d
revenue_30d
last_contact
consent_status
outcome_label
Restore, offer or hold back, without a duplicate charge
Restoration, an emergency allowance and a pack purchasable without data are compared with doing nothing, and the credit, consent and charging guardrails can refuse.
No consent
ineligible product
price/catalogue mismatch
contact cap
credit/fraud block
channel unavailable
control assignment
Keep the request, the restoration and the cost apart
What was asked of the charging system, what it confirmed and what it cost are recorded separately, so a restoration is never mistaken for a sale.
Decision log
eligibility snapshot
price/order response
delivery receipt
control assignment
revenue/outcome ledger
The journey
Help a customer with no credit get back online
The value-movement surface this product decides against.
Prepaid, digital channel and commercial teams
Step
What the customer experiences
What the operator does
The momentThe moment that started it.
The network detects an exhausted allowance or blocked data session.
Reads balance and recharge pattern, repayment history on previous advances, whether the session is genuinely out of data.
The decisionThe decision to be made.
Nothing reaches the customer yet.
Ranks top-up, emergency credit, DCB service or free-safe access.
The safeguardsThe conditions that stop it.
Still nothing. No action is sent until every check has passed.
Eligibility, credit, consent, price, partner and risk checks pass.
The actionThe action that reaches the customer.
Confirm and fulfil the selected service without general data access. Reaches them on Captive portal, USSD, App, SMS, in Kiswahili, English.
Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongRefusal, failure and recovery.
The customer is not eligible for an advance and has no way to pay.
A no-cost route is offered instead of a dead end, and the refusal reason is shown rather than implied.
The resultThe change it made.
What changed for them is what is counted; nothing else is claimed.
Confirmed fulfilment by top-up, loan or direct carrier billing.
The proofThe proof anyone can check.
Can be answered for, later, from the record.
Network event, quote, confirmation, charge, fulfilment and reversal state.
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
The change
Confirmed fulfilment by top-up, loan or direct carrier billing.
Network event, quote, confirmation, charge, fulfilment and reversal state.
Technical detail
Inputs, decision logic, systems touched, records kept.
Four questions an evaluation asks in a different order every time. Every field is the workbook’s own, unedited.
What would we need from your systems, and how much history?
Attributes required
customer_id
account_type
tenure_days
active_products
recharge_30d
usage_30d
revenue_30d
last_contact
consent_status
outcome_label
Also useful, not required
Network experience
digital clickstream
complaints
location cohort
household/account links
partner purchases
8-12 weeks of customer, usage, revenue, product, contact and outcome history; stable customer key; one executable channel
How is the action chosen, and what stops it?
Actions it may choose between
Offer
service message
reward
channel change
human follow-up
suppress
do nothing
Conditions that stop execution
No consent
ineligible product
price/catalogue mismatch
contact cap
credit/fraud block
channel unavailable
control assignment
Fail closed on eligibility/consent/price; queue retryable events; do not duplicate orders; route exception to campaign operations
What does it connect to, and what stays authoritative?
Your systems involved
CRM/CDP
campaign manager
product catalogue
OCS
order management
billing
consent registry
Interfaces
Customer/profile API
catalogue/eligibility API
campaign API
charging/order API
consent API
outcome event API
Channels
SMS
USSD
app
web
WhatsApp
outbound call
agent desktop
Charging, billing, catalogue, consent and order systems remain authoritative; HeuriTel decides only within approved policy.
What is kept, and how would a claim be tested?
Evidence required
Decision log
eligibility snapshot
price/order response
delivery receipt
control assignment
revenue/outcome ledger
The measures
Eligible population
treatment rate
conversion
incremental revenue
ARPU
churn
contact rate
margin
opt-out
decision latency
Privacy and regulation
Purpose limitation
consent and suppression
data minimisation
retention
explainability for material customer effects
local marketing rules
Randomised holdout where feasible; intent-to-treat primary view; pre-declared denominator; guardrails for complaints, margin and opt-out
The 15 definitions underneath
15 in this product
HeuriTel Zero BalanceDecision definitionHT-0067
Detect the zero balance event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
/d/HT-0067
HeuriTel Low BalanceDecision definitionHT-0068
Detect the low balance event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
/d/HT-0068
HeuriTel Data ExhaustionDecision definitionHT-0069
Detect the data exhaustion event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
Detect the voice minute exhaustion event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
/d/HT-0070
HeuriTel Pack ExpiryDecision definitionHT-0071
Use customer affordability, usage, renewal and margin data to improve pack expiry while controlling cannibalisation and measuring incremental value.
Detect the failed recharge event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
/d/HT-0072
HeuriTel Failed RenewalDecision definitionHT-0073
Detect the failed renewal event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
Identify eligible records for payment recovery, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Detect the emergency credit event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
Detect the balance advance event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
/d/HT-0076
HeuriTel Top-Up PromptDecision definitionHT-0077
Identify eligible records for top-up prompt, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for renewal recovery, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0078
HeuriTel Service ContinuityDecision definitionHT-0079
Detect the service continuity event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
/d/HT-0079
HeuriTel Grace PeriodDecision definitionHT-0080
Detect the grace period event in real time and choose the safest service-restoration or monetisation action without creating duplicate charges or unaffordable credit.
Identify eligible records for real-time upsell, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Four stages, and what has to be true before the next one starts.
12-16 weeks to pilot; 2-4 additional weeks per market after reusable interfaces exist. A team of 8 roles, named in the record rather than promised.
01
Scope
One use case, one value unit and a denominator finance has agreed to. Without these there is nothing a later result can be compared against.
Confirm value unit
select use case
baseline denominator
02
Connect
The attributes mapped from your systems, and the decision and outcome interfaces working in both directions.
map attributes
integrate decision and outcome APIs
03
Validate
Eligibility agreed, a dry run with nothing sent, then a controlled pilot with a holdout that is actually respected.
build eligibility
dry run
controlled pilot
04
Operate
The live loop: decide, check, execute through your systems, capture what came back, and measure against the control.
Ingest
qualify
score
apply limits/consent
assign control
execute approved action
capture delivery and business outcome
monitor/retrain
Who does it. 1 telecom product lead · 1 CVM specialist · 1 data engineer · 1 ML engineer · 1 integration developer · 0.5 QA · 0.5 DevSecOps · 1 deployment coordinator
Four states are tracked, and each is assessed against your systems.
Readiness is assessed per client: nothing is offered as pilot-ready until your data, your integration and your authority have been checked.
Readiness
Needs client data and integration review
The client’s data and integration position.Runtime / build state
Target product definition
What exists as running software.Surface state
Not audited
Whether this product shows the entry anywhere.Client status
Not assessed
Where a named client has reached.
Next steps from here.
15 definitions sit under Real-Time Revenue Moments. The two links that matter first are the journey this page describes, and the rest of the family it belongs to.
