By KYN AI Advisory Team — AI implementation specialists, Singapore
Require a named person for any agent action that is outbound, financial, regulatory or irreversible. Let the agent run unattended on actions that are internal, reversible and logged. To decide the cases in between, ask two questions: can the action be undone, and who outside the company sees it. If it cannot be undone or someone outside sees it, a person approves it first.
This article is a sorting method. For how to build the gate itself, see how to set approval gates for high-risk AI agent actions.
What is an approval gate?
An approval gate is a point where the agent stops, shows a person what it intends to do, and waits. The person approves, edits or rejects. Only then does the action run. The record of who approved, when and what changed is kept.
A gate is different from a notification. A notification says "I did this". A gate says "I will do this unless you stop me, and I will not proceed until you answer". Only the second protects you.
How do you decide which actions need a gate?
Score each action on four questions.
| Question | If yes, lean toward a gate | |---|---| | Can it be undone in one step? | If no | | Does anyone outside the company see it? | If yes | | Does it move or commit money? | If yes | | Does it file with or report to a regulator or tax authority? | If yes |
One "yes" is enough. Where none apply, the agent can act and log.
Add a fifth, softer question: how wrong could the agent be? A label on an internal ticket can be wrong at low cost. A price on a quote cannot.
Which actions need a person in each department?
Sales and marketing
| Action | Gate? | |---|---| | Research an account and cite the source | No | | Draft a first-touch email into a review queue | No | | Send a first-touch email or message to a new contact | Yes | | Label an inbound reply | No | | Reply with a price, a term or a date | Yes | | Move a deal to won or lost | Yes | | Publish an article or post | Yes | | Merge or delete a contact | Yes |
Outbound messages carry your name and fall under rules such as Singapore's Spam Control Act. A gate gives a person the chance to check consent and the unsubscribe line before sending.
Finance
| Action | Gate? | |---|---| | Read a bill from the mailbox and extract fields | No | | Post a draft journal entry | No | | Post to the ledger as final | Yes | | Suggest a bank match | No | | Confirm a bank match above a threshold you set | Yes | | Send a payment reminder to a customer | Yes | | Release a payment | Yes | | Submit a GST return or any filing | Yes |
Anything that touches a tax filing needs a named person. The filing is in the company's name, and the director is responsible for it.
Operations and HR
| Action | Gate? | |---|---| | Compile a daily report | No | | Send the report to a fixed internal list | No, once the list is approved | | Change stock records | Depends on reversibility and audit trail | | Change an employee's pay or CPF data | Yes | | Delete a record | Yes |
What are the levels of autonomy?
Think of autonomy as a ladder with four rungs. Product teams and vendors use similar ladders.
- Suggest. The agent proposes. A person does the action.
- Draft. The agent prepares the action. A person approves each one.
- Act with sampling. The agent acts on low-risk cases. A person reviews a sample and all exceptions.
- Act and report. The agent acts and reports after the fact.
Place each action on a rung. Start low. Move an action up only after you have measured its error rate on real cases and the cost of a wrong action is small.
Most business agents should spend a long time on rung 2 for outbound and money actions, and may sit on rung 4 for research and logging from day one.
How do you keep approval from becoming a bottleneck?
A gate that takes a day gets bypassed. Design for speed.
- Show what the reviewer needs on one screen: the draft, the source, the action, the account affected.
- Batch. Ten drafts reviewed together take far less than ten separate interruptions.
- Offer three buttons: approve, edit, reject. Capture the reason on reject.
- Set an owner and a backup. If the named person is away, the item goes to the backup. It does not auto-approve.
- Time out safely. An unanswered item expires into "not sent", never into "sent".
That last rule matters. A retry loop that resends after a timeout can turn a stalled approval into a duplicate action. Our note on approval chain timeouts covers the failure.
How do you decide when to remove a gate?
Gates are not permanent. Remove one when the evidence supports it.
- Log every approval and every edit for at least a month.
- Count how often reviewers changed the draft or rejected it.
- Review the changes. Are they about wording or substance?
- If edits are rare and cosmetic, and the action is reversible, move to sampling.
- Keep the gate on anything that is irreversible or external at any volume.
For a payment or a filing, the gate stays, because the cost of one error exceeds the cost of every review.
What must be recorded at each gate?
- The action proposed, in full.
- The data and source it was based on.
- The agent account that proposed it.
- The person who approved, edited or rejected, and the time.
- The final action as executed.
If these five items are in the log, an audit can answer "who decided" for any outcome. If any is missing, the gate is decorative.
Where KYN fits
KYN designs every system with the same rule: outbound messages, money, filings and deletions wait for a named person. Research, drafting into a review queue, labelling and logging run alone. Agents have their own restricted accounts, so an agent cannot approve its own work, and every action is logged with the actor.
For an insurance brokerage, outreach with one checkable first line goes into a queue for approval, and the reply desk sorts replies for a person to act on. The first 14 days are a review of your stack and interviews with your team, where we list your actions and place each on the ladder. A full build ships in under 90 days. See operations and security.
Frequently asked questions
Does every agent action need approval?
No. Approval on everything makes the agent slower than the person it was meant to help, and reviewers start approving without reading. Gate the actions that are outbound, financial, regulatory or irreversible, and let the rest run with logs.
Who should be the approver?
The person who would be accountable if the action went wrong. For a quote, that is the salesperson or sales lead. For a payment, a finance lead or director. Name a backup for absences.
Can an agent approve another agent's work?
Not for gated actions. A second agent can check format and flag issues, which helps the reviewer. The approval itself needs a named person, because accountability cannot sit with software.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
