Approvals are the difference between a demo and a system finance will sign off on. Here is how we design them at Ozmio — and the mistakes we made first.
Start with the expensive action
List every tool that moves money, deletes data or emails a customer. Those are the only places approvals should appear by default. Everything else should run, log and be easy to undo.
Put the decision where people already are
We tried a dedicated inbox. Nobody checked it. Approvals now land in Slack and email with the same payload: what the agent wants to do, why, and three buttons — Approve, Edit, Kill.
Refund $186.00 on INV-2044?
Cap is $150. Customer tenure 14 months. Similar refunds approved 11/12 times.
ApproveEditKill
Measure time-to-decision, not just accuracy
A correct approval that takes four hours is still a bad experience. We page the on-call owner after fifteen minutes and auto-escalate after an hour for money-moving tools.
Keep a paper trail you can replay
Every decision stores the human, the payload and the agent state. When something goes wrong, you replay — you do not argue from memory.
Want the deeper API shape? See the docs quickstart and the approvals cookbook linked there.
Related
Engineering
Eval suites that catch refund bugs
Security
EU residency without a second product
Design
Shipping ten AI homepages