An AI allowance your subscribers buy like any other pack.
Operator-branded, priced in local currency, paid through a method you already approve, and metered against an allowance the subscriber can see.
Demonstration availableLevel 2 of 5. Built for telecom operators, and bought by VAS and Digital Services. Not integrated with any provider or charging system, and not running anywhere.
Open the subscriber journeyHow a pack would work
Nine steps, and what stands behind each one.
12 of the 17 subscriber states render today on sample data. The rest are named here rather than drawn as though they existed.
- Discover a packIn the operator's app, on the web, by USSD or in a shop.Demonstrated
- Receive a quotePriced in local currency, before any commitment.Demonstrated
- Confirm the purchaseOne explicit confirmation, never an inferred one.Demonstrated
- Operator-approved paymentAirtime, mobile money, or the postpaid bill.Required for pilot
- Entitlement issuedThe allowance becomes usable, or the delay is stated.Intended
- Governed AI usageWithin the operator's safety and content policy.Required for pilot
- Allowance meteredEach task decrements a stated balance.Demonstrated
- Expiry or renewalEnds, or renews with the subscriber's consent.Intended
- Receipt, support or refundA record to keep, and a way to dispute it.Demonstrated
- Demonstrated
- A screen renders this today, on sample data.
- Intended
- The journey describes it, but no screen renders it yet.
- Required for pilot
- Neither shown nor described. It has to exist before a pilot.
A pilot’s measure
The proof this has to earn.
No figures are given because none exist: nothing has been sold, so a number on this page would be invented. These are the measures a pilot would report against.
- Packs soldConfirmed purchases, by pack and channel
- Activation ratePacks bought that became usable
- Allowance consumedShare of a pack used before it expired
- Repeat purchase and renewalSubscribers who bought a second time
- Refund and failure rateRefunds, declines and delayed entitlements
- Support demandContacts per thousand packs sold
- RevenueCharged and collected, by payment method
- Inference costProvider cost per task and per pack
- Charging and partner feesWhat the payment rail and partners take
- Margin after inference and feesWhat the operator keeps
Public nowAnyone can do this from this page, without signing in, and the page keeps no record of it. This page, its sample workbook and the sample's review need no sign-in; the steps below say which need more.
From this page to live operation
10 steps: 4 public now, 3 in an entitled workspace, 1 a request form, 1 needing an authorised sandbox, 1 not implemented.
Each step says who can take it today. A route existing is not the same as an action being available: the state beside each step is decided by the same rules that refuse a request.
- 01 · What you can buyPublic nowSell subscribers an AI allowance the way you sell a data bundle — your brand, your currency, your payment methods, your safety policy.All ten offers
- 02 · A working demonstrationPublic nowThe offer's journey on sample data.Open the demonstration
- 03 · The sample, as a workbookPublic now4 data sheets, a manifest and the generated guide, dictionary, validation lists and expected outputs — downloadable without signing in, in the sample's market and currency.Download the sample workbook
- 04 · Validation, on the samplePublic nowpackages, markets, providers and confirmations as four sheets: every package priced in the market currency with an allowance and a provider cost; every confirmation names a package and a market the package is available in; no phone number or name in any cell. The public review checks a returned workbook against the sample it was issued from, answers with the result before and after, and stores nothing.
POST /api/sample/ai-pack-economics/review - 05 · Acceptance and the stored simulationEntitled workspaceYour organisation's own workbook, reviewed, accepted as an immutable version with its original retained, and the engine's result stored whole — never recomputed on reopening.Open the workbench
- 06 · Decision and approvalEntitled workspaceA second person decides the recommendation; the maker cannot. Approval applies to a simulated recommendation.The approvals queue
- 07 · EvidenceEntitled workspaceeligibility decision per confirmation; simulated charge and entitlement; usage and margin statement; run register export. The register export, the retained original, the run history, the dry-run plan and the pilot package are downloadable from the workbench.Evidence on the workbench
- 08 · A controlled pilotPilot request availableThe request form is available here; the pilot is scoped in writing before anything runs on your systems: signed pack economics with a real inference price; a charging integration test against an operator sandbox; a safety policy accepted by operator Legal; refund and dispute paths exercised on operator systems. No pilot has been requested or agreed, and none is demonstrated.Request a controlled pilot
- 09 · Execution against your sandboxRequires an authorised sandboxThe dry-run plan names every connector call an approved decision would make across charging or billing (airtime, mobile money, postpaid), subscriber identity, notification channels, an inference provider; nothing is called and no receipt exists, because no authorised sandbox is registered.
- 10 · Live operationNot implementedUnder a separate production authorisation, with outcomes reconciled against your own records: packs charged against the charging system's own records; entitlements active against the entitlement store; provider cost against the provider's invoice. Not built; no connector exists.
- Public now
- Anyone can do this from this page, without signing in, and the page keeps no record of it.
- Available after sign-in
- A verified sign-in sees it on sample data; it reads nothing private and stores nothing.
- Entitled workspace
- A member of an organisation that holds the owning product and has the journey configured; the role decides which actions.
- Pilot request available
- The request form is available. A pilot is scoped in writing afterwards; the pilot itself is not demonstrated.
- Requires an authorised sandbox
- Needs an authorised operator sandbox, which no organisation has registered. The permission that would reach one is refused to everyone.
- Requires production authorisation
- Needs a production authorisation from the operator and a connected operator system. No such authorisation exists.
- Not implemented
- No code performs this.
The offer, in twelve lines
The offer in the same terms as the other nine.
Read from the offer contract and the engine's own run; the same twelve fields on every offer page.
- Commercial offer
- Operator-branded Consumer AI Packs
- Buyer
- VAS and Digital Services
- Problem
- Subscribers buy AI from foreign providers in foreign currency with a card the operator does not issue; the operator carries the traffic, captures none of the value and has no policy control over what its brand is associated with.
- Outcome a pilot would count
- Packs sold and consumed, and margin after inference cost.
- Current availability
- Demonstration available — level 2 of 5: A journey runs end to end on sample data, including its refusal and failure states. Of 10 steps, 4 are public now, 3 need an entitled workspace, 2 need what does not exist yet. Public now Entitled workspace Not implemented
- Public sample
- HeuriTel default synthetic sample: Kenya, in KES and Kiswahili (sample ai-pack-economics-sample v1). Download the workbook. Synthetic rows invented by HeuriTel, sized for Kenya in KES. Not an operator's figures; nobody here is real. Configure a market to see the same sample recomputed for it.
- Data requirements
- Packages (package_id, name, price, allowance_tasks, validity_days, provider_cost_per_task); Markets (market, languages, payment_methods); Availability (availability_id, package_id, market, languages, available); Confirmations (confirmation_id, subscriber_ref, package_id, market, language, payment_method, confirmed, tasks_used). packages, markets, providers and confirmations as four sheets: every package priced in the market currency with an allowance and a provider cost; every confirmation names a package and a market the package is available in; no phone number or name in any cell. A subject column holds your own pseudonymous reference; a phone number, IMSI, IMEI or account number in it is refused and never echoed back.
- Executable result
- Engine eligibility-and-economics v1, on the public sample: 7 measures with their basis, 2 sections and the exceptions it could not settle, each with an owner, and a decision against the explicit no-action alternative. The figures are the sample's and are on the workbench and in the workbook, not on this page. Simulated; nothing ran against an operator system.
- Approval model
- Maker-checker: the person who accepted the data or requested the run cannot decide its recommendation; a client administrator does. Approval applies to a simulated recommendation.
- Evidence
- eligibility decision per confirmation; simulated charge and entitlement; usage and margin statement; run register export; the retained original with its inspection verdict; the run history; the per-record dry-run plan; the pilot package.
- Pilot requirements
- signed pack economics with a real inference price; a charging integration test against an operator sandbox; a safety policy accepted by operator Legal; refund and dispute paths exercised on operator systems. None is evidenced; no pilot is requested or agreed.
- Live requirements
- Connected under a separate authorisation: charging or billing (airtime, mobile money, postpaid), subscriber identity, notification channels, an inference provider — none connected; reconciled before any outcome is claimed: packs charged against the charging system's own records; entitlements active against the entitlement store; provider cost against the provider's invoice. Not built.
Beneath the offer: Offer, Pack and Pricing Intelligence, Journey Activation, Experimentation and Value, Revenue, Risk and Assurance, Partner and Delivery Operations, AI and Governance, Telecom AI Martech and Campaign Studio, Subscriber AI Services.
On demand
The states, the products, the authority, the pilot and the detail beneath.
Every subscriber state, including the ones that are missing
The subscriber journey
Every state, including the ones that are missing.
12 render on a route you can open. 3 are described in the journey with no screen behind them. 2 exist in neither, and both are states a pilot needs first.
- EligibleDemonstratedThe subscriber opens the service and sees the allowance and the days left on it.Open this screen
- QuotedDemonstratedA pack is priced in local currency before anything is confirmed.Open this screen
- ConfirmedDemonstratedOne confirmation step, with the price and the payment method shown.Open this screen
- Payment successfulDemonstratedA receipt the subscriber can keep, naming what was bought and what it cost.Open this screen
- Payment declinedDemonstratedThe cause, what it means for the money, and what happens next.Open this screen
- Insufficient balanceDemonstratedNamed as its own case rather than folded into a generic failure.Open this screen
- Entitlement delayedDemonstratedPaid, not yet usable: the wait is stated instead of the screen going quiet.Open this screen
- ExpiredDemonstratedThe pack has run out of days, and the subscriber is told before they try to use it.Open this screen
- Refund requestedDemonstratedA route into a refund, with the money position stated.Open this screen
- Allowance meteredDemonstratedWhat has been used, on what, and what is left.Open this screen
- Support requiredDemonstratedPayment, credits, answer quality, or a person — four routes, not one form.Open this screen
- Renewal controlDemonstratedAutomatic renewal can be turned off. The control renders; the renewal event does not.Open this screen
- RenewedIntendedThe renewal itself — charged again, extended, and evidenced.
- CancelledIntendedThe settings screen says a subscriber may cancel. No cancellation flow exists behind that.
- Allowance exhaustedIntendedUsage shows a pack part-used. The zero state, and what the subscriber can still do, is not built.
- Provider unavailableRequired for pilotThe inference provider does not answer. There is no fallback, no queue and no message.
- No action, or refusalRequired for pilotThe assistant declines a task on safety or policy grounds. It currently always answers.
Seven governed products, and what each one does here
What composes it
Seven governed products, and what each one does here.
Consumer AI Packs is a way of buying. It holds no entitlement of its own and adds nothing to the 16 governed products.
- Journey ActivationTakes the subscriber through purchase, entitlement and renewal as one governed journey.
- Experimentation and ValueMeasures whether a pack earned its place, against a held-out group.
- Offer, Pack and Pricing IntelligenceDefines the pack ladder, its prices and the margin floor beneath them.
- Revenue, Risk and AssuranceOwns refunds, disputes and the rule that no subscriber is charged unintentionally.
- Partner and Delivery OperationsCarries the provider and payment relationships, and what each is contracted to do.
- AI and GovernanceRoutes inference, applies the safety policy, meters usage and records the evidence.
- Telecom AI Martech and Campaign StudioReaches subscribers in their own languages, on the channels they use.
Your systems stay authoritative — who holds what
Twelve things that would have to be true before a pilot
From demonstration to pilot
Twelve things that would have to be true.
None of these is done. They are the gate between Demonstration available and Controlled pilot ready.
- Operator-approved pack definition and economics
- Target market and eligible subscriber cohort
- Signed data and authority boundaries
- A charging sandbox to exercise against
- A selected inference provider and an approved regional architecture
- An operator-accepted safety and content policy
- Metering and cost limits
- A refund and reversal exercise, run end to end
- A customer-support runbook
- A security and privacy review
- A bounded pilot cohort
- Agreed success, stop and rollback criteria
Not started. Reaching a controlled pilot is a decision an operator and HeuriTel would take together, not a queue this page is working through.
The detail underneath
Deeper
If you need the detail underneath.
The inference provider, and why it is not named as integrated
A provider has been assessed against regional model availability and data-boundary requirements. None has been selected, contracted or called: the application makes no inference request of any kind.
Until an endpoint is called and that call is evidenced, this page will not describe a provider relationship it does not have. Choosing the provider and approving its regional architecture is one of the twelve gates above.
The subscriber data’s location
Subscriber prompts and operator data stay inside the deployment boundary agreed with the operator. That boundary is a signed artefact of the pilot gate, not a default this page can assert.
The catalogue definitions beneath this proposition
The detailed definitions sit under the governed products that compose it, in the streams for subscriber AI services, pack and pricing, and AI operations and governance.
Subscriber AI servicesPack, pricing and rechargeAI operations and governance
What you can inspect