Partnerships, digital services and finance teams
Month end. The partner's statement says forty thousand activations. The operator's billing says thirty-eight. The revenue share is due on Friday.
No demonstration is configured for this journey yet.
Seen by the customer · Partner portal, English
From the record, not a run: what would reach them, on Partner portal, Finance workbench, in English.
What happened
Month end: a partner's statement says forty thousand activations, the operator's billing says thirty-eight, and the revenue share is due.
Month end. The partner's statement says forty thousand activations. The operator's billing says thirty-eight. The revenue share is due on Friday.
What it reads
Checks before anything is sent
Delivery-receipt completeness, entitlement match, refund and reversal accounting and contract-term checks pass.
Every option considered, including doing nothing
No action is a valid outcome, and it is recorded with its reason. Nothing is computed on this page: the options are the record's own, and no run has decided anything.
The shape of the record, with no values. A reference appears only after a run is saved.
Hypothesis
A settlement computed from the delivery receipts is paid once and agreed; one computed from two statements is negotiated every month.
Desired result: Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails
Modelled not observed
No figure is modelled for this journey. The mechanism that could produce the result is stated instead.
Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain
Observed
Nothing yet. Measurement begins in a pilot’s validate stage, on your systems, against a comparison agreed first.
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
The result wanted.
Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails
The mechanism that could produce it.
Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain
The records kept to show it.
Decision log; eligibility snapshot; price/order response; delivery receipt; control assignment; revenue/outcome ledger
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
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
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
| Step | What the customer experiences | What the operator does |
|---|---|---|
| The momentThe moment that started it. | Month end: a partner's statement says forty thousand activations, the operator's billing says thirty-eight, and the revenue share is due. | Reads delivery receipts and entitlement records, refunds and reversals in the period, the contract's revenue-share terms, the partner's statement. |
| The decisionThe decision to be made. | Nothing reaches the customer yet. | Computes the settlement from the delivery receipts and the outcome ledger, quantifies the difference and assigns it an owner. |
| The safeguardsThe conditions that stop it. | Still nothing. No action is sent until every check has passed. | Delivery-receipt completeness, entitlement match, refund and reversal accounting and contract-term checks pass. |
| The actionThe action that reaches the customer. | Settle the agreed amount through the finance system, and route the difference to the partner with the receipts behind it. Reaches them on Partner portal, Finance workbench, in English. | Recommends. The system that holds the right confirms, charges or provisions. |
| When it goes wrongRefusal, failure and recovery. | The partner counts activations at request and the operator counts them at confirmation, and the two thousand missing are customers whose activation failed after the charge. | The reconciliation shows the failed activations by receipt, the charges are reversed to the customers, and the contract's counting rule is written down so the next month starts from one definition. |
| The resultThe change it made. | What changed for them is what is counted; nothing else is claimed. | Settlements paid without dispute, against the differences reconciled. |
| The proofThe proof anyone can check. | Can be answered for, later, from the record. | Delivery receipts, entitlement records, refunds and reversals, contract terms, settlement computation, partner statement and dispute record. |
Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.
What goes wrong
The partner counts activations at request and the operator counts them at confirmation, and the two thousand missing are customers whose activation failed after the charge.
What happens then
The reconciliation shows the failed activations by receipt, the charges are reversed to the customers, and the contract's counting rule is written down so the next month starts from one definition.
A partner catalogue, a marketplace and super-app personalisation choose what to offer from approved actions including none; fulfilment, subscription lifecycle, entitlements, carrier billing, revenue share and settlement keep partner and operator in agreement.
the content and gaming partners sold through the same commerce
where the operator's own ledgers are reconciled on the same footing
No demonstration is configured for this journey yet.