Sell everyday AI access on the phone bill, in the customer's own language.
A package, a price, a confirmation and a receipt, with the operator's charging system deciding and the assistant opening only when the entitlement exists.
For Operator AI-service owners, and the subscribers they serve.
The package that fits, its cost, and whether this customer may be charged for it at all.
A customer wants useful AI in Kiswahili or Sheng, has no card, and will not create an account with a foreign provider.
A short trial the customer confirms before any charge
A weekly or monthly package with a clear allowance
A shared household package
What it does
Three things it helps you decide or do.
Quote in the local brand and language
The package, its price and its allowance are shown in an evaluated language before anything is charged.
customer_id
account_type
tenure_days
active_products
recharge_30d
usage_30d
revenue_30d
last_contact
consent_status
outcome_label
Charge only after an explicit confirmation
Age, price, allowance, provider scope and consent can each stop the sale, and the charging system confirms or declines.
No consent
ineligible product
price/catalogue mismatch
contact cap
credit/fraud block
channel unavailable
control assignment
Meter what was used and recover what went wrong
Credits, the provider route and the receipt are kept; an unmatched debit is reversed rather than explained away.
Decision log
eligibility snapshot
price/order response
delivery receipt
control assignment
revenue/outcome ledger
The journey
Sell everyday AI access on the phone bill, in the customer's own language
The operator-branded subscriber experience.
Digital services, product and partnerships teams
Step
What the customer experiences
What the operator does
The momentThe moment that started it.
A subscriber needs affordable everyday AI in a familiar language.
Reads age and identity checks, balance and charging eligibility, language preference, existing entitlements.
The decisionThe decision to be made.
Nothing reaches the customer yet.
Selects the suitable AI package, language and governed inference route.
The safeguardsThe conditions that stop it.
Still nothing. No action is sent until every check has passed.
Identity, age, price, allowance, provider scope and consent pass.
The actionThe action that reaches the customer.
Quote, confirm, charge, entitle and open the operator-branded assistant. Reaches them on App, Web, WhatsApp, USSD-assisted, in Kiswahili, English, Sheng.
Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongRefusal, failure and recovery.
The charge is declined at the billing system after the customer has confirmed.
No entitlement is granted, the customer is told plainly what happened, and the assistant does not open until charging confirms.
The resultThe change it made.
What changed for them is what is counted; nothing else is claimed.
Subscription, tier upgrade and consumed retail credits.
The proofThe proof anyone can check.
Can be answered for, later, from the record.
Quote, consent, OCS charge, entitlement, provider route and usage receipt.
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
Subscription, tier upgrade and consumed retail credits.
Quote, consent, OCS charge, entitlement, provider route and usage receipt.
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 16 definitions underneath
16 in this product
HeuriTel AI AssistantDecision definitionHT-0186
Identify eligible records for ai assistant, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0186
HeuriTel Local Language AIDecision definitionHT-0187
Identify eligible records for local language ai, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0187
HeuriTel Voice AIDecision definitionHT-0188
Identify eligible records for voice ai, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0188
HeuriTel AI TranslationDecision definitionHT-0189
Identify eligible records for ai translation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0189
HeuriTel AI LearningDecision definitionHT-0190
Identify eligible records for ai learning, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0190
HeuriTel AI Work AssistantDecision definitionHT-0191
Identify eligible records for ai work assistant, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0191
HeuriTel AI for SMEsDecision definitionHT-0192
Identify eligible records for ai for smes, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0192
HeuriTel AI Travel AssistantDecision definitionHT-0193
Identify eligible records for ai travel assistant, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0193
HeuriTel AI Agriculture AssistantDecision definitionHT-0194
Identify eligible records for ai agriculture assistant, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0194
HeuriTel AI Health Information AssistantDecision definitionHT-0195
Identify eligible records for ai health information assistant, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0195
HeuriTel AI PacksDecision definitionHT-0196
Use customer affordability, usage, renewal and margin data to improve ai packs while controlling cannibalisation and measuring incremental value.
/d/HT-0196
HeuriTel AI CreditsDecision definitionHT-0197
Support ai credits with approved, purpose-limited data, documented policy, human/credit-engine authority, reason codes and outcome monitoring.
/d/HT-0197
HeuriTel AI SubscriptionDecision definitionHT-0198
Select, bundle, sell and retain the right ai subscription proposition using eligibility, partner cost, entitlement and incremental margin controls.
/d/HT-0198
HeuriTel AI Family PlanDecision definitionHT-0199
Identify eligible records for ai family plan, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0199
HeuriTel AI PremiumDecision definitionHT-0200
Identify eligible records for ai premium, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0200
HeuriTel AI Call AssistantDecision definitionHT-0201
Identify eligible records for ai call assistant, 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.
16 definitions sit under Subscriber AI Services. The two links that matter first are the journey this page describes, and the rest of the family it belongs to.
