Skip to content
HeuriTel
Sign in
AI and Governance

Subscriber AI Services

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.

Open preview

Verified work email required.

More in AI and Governance
The decision, annotated from the record

A subscriber needs affordable everyday AI in a familiar language.

The package that fits, its cost, and whether this customer may be charged for it at all.

  1. A short trial the customer confirms before any chargeConsidered
  2. A weekly or monthly package with a clear allowanceConsidered
  3. A shared household packageConsidered
  4. Take no action, and record whyA valid outcome
The safeguards, the action and the channels

Before anything reaches the customer: Identity, age, price, allowance, provider scope and consent pass.

What would reach them: Quote, confirm, charge, entitle and open the operator-branded assistant. On App, Web, WhatsApp, USSD-assisted.

The subscriber's own screen. The operator-side decision journey is not yet runnable.

The journey, step by step. Read the journey in full

The journey below is written for a generic operator. Tell us your market and it will be presented in it.

Configure a demonstration
The decision

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
The decision, step by step
  1. 01Eligibility rules
  2. 02propensity/uplift or value score
  3. 03treatment constraints
  4. 04ranked action including no-action
  5. 05decision log

The price, the allowance, the renewal and the customer relationship stay the operator's.

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.

    In the record’s words
    • 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.

    In the record’s words
    • 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.

    In the record’s words
    • 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.

Subscriber AI Services: the situation this product is about
Step by step, from both sides

Digital services, product and partnerships teams

What the customer experiencesWhat 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.The customer's screen is unchanged.Selects the suitable AI package, language and governed inference route.
The safeguardsThe conditions that stop it.Still unchanged: the action waits 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.Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongThe failure, and the 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.
Open previewRead the journey in full

Hypothesis

Operator billing reaches customers no card-based service can, and the operator keeps the customer relationship rather than renting it out.

Modelled

The mechanism that could produce the result, stated; the figure is measured in the pilot.

Observed

Measured in a pilot’s validate stage, on your systems, against a comparison agreed first.

The result, the mechanism, the measurement, and the record’s five answers
Desired result
Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails
Mechanism
Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain
Measurement

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

  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

Measured in the pilot's validate stage, on your systems, with the comparison agreed first. Every line above is the record's own design intent.

The business side

The change
Subscription, tier upgrade and consumed retail credits.
Running cost
Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline
What evidence supports it
Quote, consent, OCS charge, entitlement, provider route and usage receipt.
Technical detail

Inputs, decision logic, systems touched, records kept.

The four questions, field by field

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

The 16 definitions underneath

16 in this product

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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.

    /d/HT-0201

Search definitions across every product

Implementing it

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.

  1. 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
  2. 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
  3. 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
  4. 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
The team, and the four states each assessed against your systems

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

Readiness is assessed on your data, your integration and your authority.

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.

Open the whole journey Read the scenario in full The rest of AI and Governance Ask a question first
Related products, and why

In the same area: Partner and subscriber services

What can we offer beyond connectivity, and with whom?