Sell a partner's service to the customer it fits, fulfil it and settle it, on one commerce ledger.
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.
For Digital services, partnerships and consumer commercial teams running a marketplace or a super app.
Month end: a partner's statement says forty thousand activations, the operator's billing says thirty-eight, and the revenue share is due.
The amount owed, the explanation of any difference, and the statement that goes to the partner with the payment.
Settle the amount the delivery receipts supportConsidered
Settle the agreed amount and route the difference with its receiptsConsidered
Hold the settlement, where the receipts are incompleteConsidered
No adjustment, where the difference is refunds and reversals both sides agree onConsidered
Before anything reaches the customer: Delivery-receipt completeness, entitlement match, refund and reversal accounting and contract-term checks pass.
What would reach them: Settle the agreed amount through the finance system, and route the difference to the partner with the receipts behind it. On Partner portal, Finance workbench.
The amount owed, the explanation of any difference, and the statement that goes to the partner with the payment.
Month end. The partner's statement says forty thousand activations. The operator's billing says thirty-eight. The revenue share is due on Friday.
Settle the amount the delivery receipts support
Settle the agreed amount and route the difference with its receipts
Hold the settlement, where the receipts are incomplete
No adjustment, where the difference is refunds and reversals both sides agree on
What it does
Three things it helps you decide or do.
Offer the partner service that fits, or nothing
Marketplace, merchant discovery and personalisation choose an offer, a bundle or no action for each customer, within the partner catalogue and the consent held.
Offer
service message
reward
channel change
human follow-up
suppress
do nothing
Fulfil, entitle and bill through the systems of record
Digital service fulfilment, subscription lifecycle, entitlement management and carrier billing commerce execute through the order and charging systems; a price or catalogue mismatch or a channel outage stops the sale.
No consent
ineligible product
price/catalogue mismatch
contact cap
credit/fraud block
channel unavailable
control assignment
Settle with the partner from the same record
Partner settlement, ecosystem revenue share and partner performance are computed from the delivery receipt and the outcome ledger, and partner fraud management watches the same flow.
Decision log
eligibility snapshot
price/order response
delivery receipt
control assignment
revenue/outcome ledger
The journey
Settle with a partner from the record the customer was billed on
No demonstration is configured for this product yet.
Partnerships, digital services and finance teams
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.
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
The change
Settlements paid without dispute, against the differences reconciled.
Delivery receipts, entitlement records, refunds and reversals, contract terms, settlement computation, partner statement and dispute record.
Technical detail
Inputs, decision logic, systems touched, records kept.
Four questions an evaluation asks in a different order every time. Every field is the workbook’s own, unedited.
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
How is the action chosen, and what stops it?
Actions it may choose between
Offer
service message
reward
channel change
human follow-up
suppress
do nothing
Conditions that stop execution
No consent
ineligible product
price/catalogue mismatch
contact cap
credit/fraud block
channel unavailable
control assignment
Fail closed on eligibility/consent/price; queue retryable events; do not duplicate orders; route exception to campaign operations
What does it connect to, and what stays authoritative?
Your systems involved
CRM/CDP
campaign manager
product catalogue
OCS
order management
billing
consent registry
Interfaces
Customer/profile API
catalogue/eligibility API
campaign API
charging/order API
consent API
outcome event API
Channels
SMS
USSD
app
web
WhatsApp
outbound call
agent desktop
Charging, billing, catalogue, consent and order systems remain authoritative; HeuriTel decides only within approved policy.
What is kept, and how would a claim be tested?
Evidence required
Decision log
eligibility snapshot
price/order response
delivery receipt
control assignment
revenue/outcome ledger
The measures
Eligible population
treatment rate
conversion
incremental revenue
ARPU
churn
contact rate
margin
opt-out
decision latency
Privacy and regulation
Purpose limitation
consent and suppression
data minimisation
retention
explainability for material customer effects
local marketing rules
Randomised holdout where feasible; intent-to-treat primary view; pre-declared denominator; guardrails for complaints, margin and opt-out
The 18 definitions underneath
18 in this product
HeuriTel Digital CommerceDecision definitionHT-0507
Identify eligible records for digital commerce, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0507
HeuriTel MarketplaceDecision definitionHT-0508
Identify eligible records for marketplace, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for partner catalogue, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for partner onboarding, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for partner offer management, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for partner bundle management, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for partner settlement, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for partner performance, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for merchant discovery, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for merchant personalisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0516
HeuriTel Digital Service FulfilmentDecision definitionHT-0517
Identify eligible records for digital service fulfilment, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Select, bundle, sell and retain the right subscription lifecycle proposition using eligibility, partner cost, entitlement and incremental margin controls.
Identify eligible records for entitlement management, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for affiliate sales, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0521
HeuriTel Super App PersonalisationDecision definitionHT-0522
Identify eligible records for super app personalisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for ecosystem revenue share, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Detect and prioritise partner fraud management risk using bounded rules and models, then pass the signal to the authorised fraud or transaction-control system.
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. A team of 8 roles, named in the record rather than promised.
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
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
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
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
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
Four states are tracked, and each is assessed against your systems.
Readiness is assessed per client: nothing is offered as pilot-ready until your data, your integration and your authority have been checked.
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.
18 definitions sit under Digital Commerce & Partner Ecosystem. The two links that matter first are the journey this page describes, and the rest of the family it belongs to.
