Your thresholds. A person above them. Every action logged.
Each agent works within limits you set: an amount, a customer, a country, an hour of the day. Above them, it prepares the case and a person decides, on their phone, in their language. Every action is logged before anyone asks to see it.
- What is control here?
- The limits you set for each agent, the person who decides above them, and the log of everything the agent read, did and asked. It is not a dashboard to watch: it is a record you can open.
| Time | Actor | Action | Target | Approved by |
|---|---|---|---|---|
| 10:14 | Orders agent | Asked for a credit release | A contractor in Jeddah | Waiting |
| 10:14 | Orders agent | Held it: above your limit | Credit release | Waiting |
| 10:15 | Orders agent | Sent the case to the sales manager, with what it read | Credit release | Waiting |
| 10:22 | Sales manager | Approved it on their phone | Credit release | Sales manager |
| 10:22 | Orders agent | Released the credit in the ERP | Customer account | Sales manager |
Nobody hands the keys to a system they cannot stop. You hold the thresholds: above them, every agent stops and asks.
Where the line sits is yours
Six requests from one week, drawn by size. Drag the line, or use the arrow keys: what reaches above it waits for a person, what stays under it goes through. Nothing you set here is saved.
Two requests wait for a person; the rest go through.
Who may do what
Every role, the agent among them, has the same three answers for every action: alone, with approval, or never. This is an example; the matrix is yours to fill in.
| Action | The agent | Sales manager | Finance manager | Owner |
|---|---|---|---|---|
| Send a quote | Alone | Alone | Never | Alone |
| Confirm an order | Alone | Alone | Never | Alone |
| Release credit | With approval | With approval | Alone | Alone |
| Issue an invoice | With approval | Never | Alone | Alone |
| Message a customer | Alone | Alone | Alone | Alone |
| Change a price | Never | With approval | Never | Alone |
The log
What the agent read, what it did, who approved it and what happened next, written as it happens, before anyone asks to see it. It is kept in the record and sent to your own systems when you want it.
For the approver
The log protects the person who approved, because it shows what they saw when they decided: the case, what the agent read, and the rule that sent it to them.
Control is the concern, not the idea
Owners across the Gulf are not wary of what AI can do. They are wary of what it does when nobody is looking. A threshold, a person above it and a log that exists before anyone asks are the answer to that.
What owners ask about control
What can it do without asking?
Only what sits inside the thresholds you set. The matrix on this page is an example; yours is filled in with you, action by action.
Can we stop it?
Yes. Above your thresholds every agent stops and asks, and the thresholds are yours to lower until everything goes to a person.
What if it is wrong?
It cannot act above your thresholds, and every action is on the record with what the agent read. The person who approved saw what the agent saw, and the rule is fixed on site.
Can we see every action?
Yes. The log is on the record, written as each action happens, and it can be sent to your own systems.
Does it act at night?
Only if you let it. The hour of the day is a threshold like any other.
Who is accountable?
One team: the engineers who built it, on site with you, and the Qantara team behind them.
