Between customer moments and operator authority. HeuriTel reads what your BSS, OCS, CRM and consent systems already know, proposes one permitted action — or none — and writes the evidence. Your systems stay the record. Your people keep the authority.
Every recommendation walks the same seven steps. Four of them can stop it. The one that executes is always yours.
Subscriber movement, recharge, care, channel, product or service state — read from the system that owns it, in place.
Opportunity, price, journey, partner route, AI route — or an explicit no-action recommendation, with the reason.
Consent, spend, entitlement, service state, human approval and commercial thresholds.
Stops when a limit is reached, consent is missing, or the service state says otherwise. A stop produces a reason, not silence.
The permitted choice and its exact consequence, accepted deliberately — or declined.
Stops when the customer does not confirm.
The declared outcome unit, its cost, and the held-out comparator it is measured against.
Assignment, execution, receipt, cost, exception, remedy and incrementality — reopenable as stored.
Stops when the source system has not confirmed. Then there is no receipt, and the gap is on the record.
Find value movement across recharge, product, care and service context without turning every observation into an action.
| Customer | Decision | Because |
|---|---|---|
| SUB-NBA-0001 | Loyalty call with tailored plan | 35 % × 900 − 150 = 165 |
| SUB-NBA-0002 | Bonus data on recharge | 22 % × 300 − 40 = 26 |
| SUB-NBA-0003 | Recharge reminder | 6 % × 60 − 2 = 2 |
Sample records from Next-best-action and Retention Decisioning, as its engine decides them. Every row carries its reason; nothing here was sent.
Route each moment through policy, consent, entitlement, commercial and human authority gates before activation — the seven steps above, as code.
Keep assignment, execution, receipts, exceptions and remedies attached to the outcome trace, so an approval can be replayed a year later.
From the data-processing agreement
The rows are held in a hosted libSQL database in Mumbai, India (ap-south-1); the uploaded files in an S3 bucket in Mumbai, India (ap-south-1); the model calls go to Amazon Bedrock in Mumbai, India (ap-south-1); the text of a turn is sent there and not stored by the processor; the email goes through Resend, for the sign-in codes and invitations. Requests are served by the processor’s edge, which holds no row of the controller’s data.
In the evaluation workspace the model calls go to no model: the assistant answers from a scripted rehearsal inside the Worker and no text leaves it. In operation they go to Amazon Bedrock in Mumbai, India (ap-south-1); the text of a turn is sent there and not stored by the processor.
The platform’s design, in the agreement’s words; an organisation’s own agreement is composed from its profile and its deployment and read on its Settings.