Show the next offer the customer can buy in one confirmation, or show nothing.
When a customer opens the app, compare the offer they are eligible for, a reminder of what they started and the screen they came for, and fulfil through the order system or not at all.
The offer, if any, the app shows this customer now — bought and fulfilled in one confirmation.
A customer opens the app to check their balance. Three banners compete for the space. Last month's banner was for a pack they had already bought.
The offer the customer is eligible for and most likely to buy, with its price
A reminder of something they started and did not finish
No offer, and the screen they came for
What it does
Three things it helps you decide or do.
Read what the customer came to do
The session, the entitlements already held, price and stock from the catalogue and the order system, and the offers already shown are what an in-app offer is judged on.
customer_id
account_type
tenure_days
active_products
recharge_30d
usage_30d
revenue_30d
last_contact
consent_status
outcome_label
Offer, remind or step aside
One purchasable offer, a reminder and no offer are compared, and the eligibility, price, consent, stock and order-system checks can refuse any of them.
No consent
ineligible product
price/catalogue mismatch
contact cap
credit/fraud block
channel unavailable
control assignment
Count fulfilled orders, not offers shown
Quote, confirmation, order reference and fulfilment are recorded separately from impressions, so a banner is never counted as a sale.
Decision log
eligibility snapshot
price/order response
delivery receipt
control assignment
revenue/outcome ledger
The journey
Make the next in-app offer one the customer can actually buy
No demonstration is configured for this product yet.
Digital channel, app and e-commerce teams
Step
What the customer experiences
What the operator does
The momentThe moment that started it.
A customer opens the app with a need the catalogue can meet and a history that says what they will not buy.
Reads what the customer came to do, from the session, eligibility and the entitlements already held, price, stock and fulfilment state from the catalogue and the order system, consent and the offers already shown.
The decisionThe decision to be made.
Nothing reaches the customer yet.
Ranks the next offer the customer can buy in one confirmation, or none.
The safeguardsThe conditions that stop it.
Still nothing. No action is sent until every check has passed.
Eligibility, price, consent, stock or entitlement and order-system checks pass.
The actionThe action that reaches the customer.
Show one offer with its price, take one confirmation and fulfil through the order system. Reaches them on App, Web, USSD, in Kiswahili, English.
Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongRefusal, failure and recovery.
The offer is confirmed, and the order system rejects it, leaving the customer with a charge pending and nothing delivered.
The confirmation is held until the order system accepts, the customer sees the state rather than a spinner, and a rejected order is reversed with the reason recorded.
The resultThe change it made.
What changed for them is what is counted; nothing else is claimed.
Confirmed, fulfilled in-app orders against abandonment, not offers shown.
The proofThe proof anyone can check.
Can be answered for, later, from the record.
Session, eligibility, offer rationale, quote, confirmation, order reference and fulfilment.
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, fulfilled in-app orders against abandonment, not offers shown.
Identify eligible records for app personalisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0100
HeuriTel App Home PersonalisationDecision definitionHT-0101
Identify eligible records for app home personalisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0101
HeuriTel Digital SalesDecision definitionHT-0102
Identify eligible records for digital sales, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0102
HeuriTel Digital StoreDecision definitionHT-0103
Identify eligible records for digital store, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0103
HeuriTel Digital Product DiscoveryDecision definitionHT-0104
Identify eligible records for digital product discovery, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0104
HeuriTel Digital Pack SalesDecision definitionHT-0105
Use customer affordability, usage, renewal and margin data to improve digital pack sales while controlling cannibalisation and measuring incremental value.
/d/HT-0105
HeuriTel Digital RechargeDecision definitionHT-0106
Use customer affordability, usage, renewal and margin data to improve digital recharge while controlling cannibalisation and measuring incremental value.
/d/HT-0106
HeuriTel Digital Cross-SellDecision definitionHT-0107
Identify eligible records for digital cross-sell, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0107
HeuriTel Digital UpsellDecision definitionHT-0108
Identify eligible records for digital upsell, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0108
HeuriTel Digital OnboardingDecision definitionHT-0109
Identify eligible records for digital onboarding, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0109
HeuriTel Digital ConversionDecision definitionHT-0110
Identify eligible records for digital conversion, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0110
HeuriTel Digital RetentionDecision definitionHT-0111
Identify eligible records for digital retention, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0111
HeuriTel Digital NotificationsDecision definitionHT-0112
Identify eligible records for digital notifications, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0112
HeuriTel App EngagementDecision definitionHT-0113
Identify eligible records for app engagement, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for app recommendations, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0114
HeuriTel App SearchDecision definitionHT-0115
Identify eligible records for app search, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0115
HeuriTel Digital Self-CareDecision definitionHT-0116
Identify eligible records for digital self-care, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0116
HeuriTel Digital Journey RecoveryDecision definitionHT-0117
Identify eligible records for digital journey recovery, 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.
18 definitions sit under App & Digital Sales. The two links that matter first are the journey this page describes, and the rest of the family it belongs to.
