Faayez MohammadFounder and CEO, Nexvix
Published September 20269 min read
- Default
- Every customer-facing message held
- Always on
- Low-confidence escalation
- Never removable
- Destructive and financial actions
Approval has a cost, and it is the point
Every approval converts machine time into human time. That is the trade you are making deliberately: a system that asks about everything has saved nobody anything, and one that asks about nothing will eventually do something you have to apologise for.
The design question is not how many approvals, but which ones. Place them where the cost of being wrong is high and the volume is low.
The three Nexvix designs in by default
- Before a customer sees it: anything the system writes outward can be held for review. Most clients start with everything held and relax it as trust builds.
- When the system is unsure: below a confidence threshold you control, the work routes to a named person with full context.
- Before anything is deleted or paid: destructive and financial actions always require a human action. No score unlocks them.
The first is a dial, the second is always on, the third cannot be removed by us or by you. That last one is deliberate: it is the approval that protects the client from their own future enthusiasm.
Setting the confidence threshold
A threshold is a business decision dressed as a technical one. Set it high and the system escalates constantly, which feels safe and costs the saving. Set it low and it acts on weak evidence.
Nexvix starts deliberately high, measures the escalation rate for two weeks against real traffic, and then lowers it with the client watching. Tuning after launch, with data, beats guessing before it.
A threshold is a business decision wearing a technical costume.
Naming the person, not the team
An escalation to “the sales team” is an escalation to nobody. Every approval point names a role and a fallback, with a time limit and an action when the time limit passes.
This is the part clients most often want to leave vague, and the part that decides whether approvals actually happen in week eight.
Recording the decision
Every approval, override and escalation is written to the record with who, when and what changed. It costs almost nothing at build time and is the only thing that answers “why did our system do that?” six months later.
If a supplier cannot show you what the audit record contains, assume there is not one.