Skip to content
HeuriTel
Sign in
A market trader completing a payment on a handset.

Sell partner content as operator bundles, with rights, entitlement, cancellation and partner margin handled.

Content deals fail on operational detail: rights by market, entitlement activation, cancellation, refunds and partner settlement.

Demonstration availableLevel 2 of 5 — A journey runs end to end on sample data, including its refusal and failure states. Bought by Digital Services and content partnerships. Nothing here has run against an operator system.

Open the demonstration

A payment completed on a handset. The bundles and the partner shares here are the sample's; no entitlement, charge or settlement is real.

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.

The sample, computed

2000 KES charged (simulated) and 500 refunded across 6 subscriptions; 805 KES due to 3 partners; 6 exceptions worth 1300 KES held out of settlement.

HeuriTel default synthetic sample — Kenya, in KES, Kiswahili; sample bundle-entitlement-settlement-sample v1. 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. Configure a market and this page, the workbook and the review recompute for it.

  • 2,000 KES — Charged (simulated)activations and renewals with rights on the date, in lifecycle order
  • 500 KES — Refundedrefunds that followed a recognised charge
  • 1,500 KES — Net revenuecharged minus refunded
  • 805 KES — Due to partnerseach partner's share of its net
  • 695 KES — Operator keepsnet minus partner share
  • 1,300 KES — Held out of settlementamounts on events the lifecycle refused

Settle 805 KES across 3 partners on the recognised events; hold the 6 exceptions (1300 KES) for partner operations before any statement is issued. If nobody acts: No statement is issued: partners are paid on whatever the billing feed says, including charges without rights and refunds nobody charged. No entitlement was activated or cancelled. No subscriber was charged or refunded. No partner statement was sent.

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.

  1. 01 · What you can buyPublic nowSell partner content as operator bundles, with rights, entitlement, cancellation and partner margin handled.All ten offers
  2. 02 · A working demonstrationPublic nowThe offer's journey on sample data.Open the demonstration
  3. 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
  4. 04 · Validation, on the samplePublic nowbundles, rights, subscriptions and events as four sheets: every subscription names a bundle with rights in its market; every event belongs to a subscription and follows its lifecycle; partner share between 0 and 100. 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/bundle-entitlement-settlement/review
  5. 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
  6. 06 · Decision and approvalEntitled workspaceA second person decides the recommendation; the maker cannot. Approval applies to a simulated recommendation.The approvals queue
  7. 07 · EvidenceEntitled workspaceeligibility per subscription; entitlement lifecycle state; settlement statement per partner; 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
  8. 08 · A controlled pilotPilot request availableThe request form is available here; the pilot is scoped in writing before anything runs on your systems: a partner rights and availability contract; a settlement reconciliation run against partner statements. No pilot has been requested or agreed, and none is demonstrated.Request a controlled pilot
  9. 09 · Execution against your sandboxRequires an authorised sandboxThe dry-run plan names every connector call an approved decision would make across entitlement store, billing, partner settlement feed; nothing is called and no receipt exists, because no authorised sandbox is registered.
  10. 10 · Live operationNot implementedUnder a separate production authorisation, with outcomes reconciled against your own records: settlement statement against the partner's own statement; entitlements against the entitlement store. 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.
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.
On demand

The contract, the data, the pilot and the products beneath.

Four things a technical or commercial evaluation asks for, each in the same terms as the other nine offers.

The offer in twelve lines
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
OTT, Content, Sports and Gaming Bundles
Buyer
Digital Services and content partnerships
Problem
Content deals fail on operational detail: rights by market, entitlement activation, cancellation, refunds and partner settlement.
Outcome a pilot would count
Bundles sold, and margin after partner share.
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 bundle-entitlement-settlement-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
Bundles (bundle_id, name, partner, price, partner_share_pct); Rights (rights_id, bundle_id, market, valid_from, valid_to); Subscriptions (subscription_id, subscriber_ref, bundle_id, market, started_on, status); Events (event_id, subscription_id, event, on, amount). bundles, rights, subscriptions and events as four sheets: every subscription names a bundle with rights in its market; every event belongs to a subscription and follows its lifecycle; partner share between 0 and 100. 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 entitlement-lifecycle v1, on the public sample: 2000 KES charged (simulated) and 500 refunded across 6 subscriptions; 805 KES due to 3 partners; 6 exceptions worth 1300 KES held out of settlement. 7 measures with their basis, 2 sections, 6 exceptions with owners. Recommendation: Settle 805 KES across 3 partners on the recognised events; hold the 6 exceptions (1300 KES) for partner operations before any statement is issued. If nobody acts: No statement is issued: partners are paid on whatever the billing feed says, including charges without rights and refunds nobody charged. 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 per subscription; entitlement lifecycle state; settlement statement per partner; run register export; the retained original with its inspection verdict; the run history; the per-record dry-run plan; the pilot package.
Pilot requirements
a partner rights and availability contract; a settlement reconciliation run against partner statements. None is evidenced; no pilot is requested or agreed.
Live requirements
Connected under a separate authorisation: entitlement store, billing, partner settlement feed — none connected; reconciled before any outcome is claimed: settlement statement against the partner's own statement; entitlements against the entitlement store. Not built.

Beneath the offer: Offer, Pack and Pricing Intelligence, Journey Activation, Revenue, Risk and Assurance, Partner and Delivery Operations, Telecom AI Martech and Campaign Studio, OTT, Content, Sports, Gaming & Adjacent Services.

Your data — 4 sheets, checked before anything is read
Your data

4 sheets, checked before anything is read from them.

bundles, rights, subscriptions and events as four sheets: every subscription names a bundle with rights in its market; every event belongs to a subscription and follows its lifecycle; partner share between 0 and 100. A subject column holds your own pseudonymous reference; a phone number, IMSI, IMEI or account number in it is refused and never echoed back.

  • Bundlesthe bundles on sale: partner, monthly price and the partner's share of net revenue. Columns: bundle_id, name, partner, price, partner_share_pct.
  • Rightswhere and when each bundle may be sold. Columns: rights_id, bundle_id, market, valid_from, valid_to.
  • Subscriptionssubscribers' bundles: which bundle, where, since when, and the status your systems hold. Columns: subscription_id, subscriber_ref, bundle_id, market, started_on, status.
  • Eventswhat happened to each subscription, with the amount charged or refunded. Columns: event_id, subscription_id, event, on, amount.
A pilot’s measure and prerequisites — 5 things that would have to be true
What a pilot would count, and needs

Bundles sold, and margin after partner share.

Nothing is counted until it is reconciled against your own records: settlement statement against the partner's own statement; entitlements against the entitlement store.

  • a partner rights and availability contract
  • a settlement reconciliation run against partner statements
  • Connected under authorisation: entitlement store. Not connected today.
  • Connected under authorisation: billing. Not connected today.
  • Connected under authorisation: partner settlement feed. Not connected today.
Built on 5 governed products and 2 catalogue streams
What it draws on

5 governed products and 2 catalogue streams.

The offer is a commercial view onto the same platform every other offer runs on. Its workbench opens with Offer, Pack and Pricing Intelligence.