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 availableA journey runs end to end on sample data, including its refusal and failure states. Built for telecom operators, and bought by VAS and Digital Services. A pilot connects your provider and your charging system.
Sample. Choose your market to see this page and its workbook in your currency and language.
Open the subscriber journey7 of 10 confirmations charged for 1058 units; margin 733 units (69.3 %) after provider cost.
7 of 10 confirmations charged for 1058 units; margin 733 units (69.3 %) after provider cost.
Decision Sell the 3 packs whose margin holds at full use; hold AI Try until repriced or the allowance is reduced. If nobody acts: 1058 units of confirmed demand goes to foreign providers, unbilled by the operator.
The customer’s screen, running on the sample. Sample records.
Nine steps, and what stands behind each one.
12 of the 17 subscriber states render today on sample data.
- 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, and only an explicit 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
The three marks, and what each one means
- 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.
The proof this has to earn.
The figures a pilot reports are its own; these are its measures.
- 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
The workspace, screen by screen.
1 of 8 · Overview The workbench: the tiles, the run, the ladder, the last run and the next step. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
2 of 8 · Sample The result on the sample: the headline and the tiles, each with its basis. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
3 of 8 · Sample The decision the engine proposes, and what happens if nobody acts. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
4 of 8 · Sample The offer ladder, and the choices exactly as the customer sees them. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
5 of 8 · Sample The checks the engine refused, each with its reason and its owner. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
6 of 8 · Your data Your data: the sheets, the template to download, and the review of what comes back. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
7 of 8 · Runs Every run, as it was computed, with the version it ran on. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
8 of 8 · Decide The proposal to an approver, and what the approver sees. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows.
See it on your own numbers.
Operator-branded Consumer AI Packs. Sell subscribers an AI allowance the way you sell a data bundle — your brand, your currency, your payment methods, your safety policy. 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.
Open the demonstration on the sample · Download the sample workbook
The states, the products, the authority, the pilot and the detail beneath.
Every subscriber state, including the ones that are missing
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; the cancellation flow is built in a pilot.
- 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.
- Refusal, or doing nothingRequired for pilotThe assistant declines a task on safety or policy grounds. It currently always answers.
Seven governed products, and what each one does here
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
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
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
Three things you can open now.