Dry-run a new agent policy against past activity before it goes live. See how it works

Skip to content
Gaten

Platform · Human approvals

A person decides when it matters.

Some actions shouldn't run on an agent's word alone. Your policy holds them and asks the right person — with everything they need to decide in seconds.

Approval needed · 28 min leftSample

support-agent wants to

Refund $500 to order #A-2210

Customer
#88412 · Gold tier
Reason given
Delayed delivery, 9 days
Held by
refunds v2.4 · rule 2
Refunds today
3 · $210 total

Routing

The right approver for each action.

Your policy names who approves what, and how long they have. Examples:

ActionHeld whenApproverTime to answer
Refund$100 – $1,000Finance lead30 min
Supplier paymentAbove daily limitTwo finance approvers4 hours
Customer emailMentions pricing or legal termsSupport lead1 hour
Production changeConfig in productionOn-call engineer15 min
Role grantAdmin roleSecurity1 hour

Timeouts & escalation

Silence never means yes.

Decide in advance what happens when nobody answers. Held actions escalate, and if they still aren't approved, they don't run.

  1. 0 min

    Request sent to the finance lead, with full context.

  2. 30 min

    No answer — escalated to the finance manager.

  3. 2 hours

    Still no answer — the refund is denied and the agent tells the customer it's being reviewed.

Context, not a ticket

Approvers see the agent, the action, its arguments and the rule that held it — no investigation needed.

In the tools they use

Requests reach approvers where they already work, so answers come in minutes, not days.

Every answer recorded

Approve or reject, the decision, the person and the time are written to the audit trail.

Conceptual architecture of connected white, black and blue arches
A person, when it mattersConceptual illustration

Decide which actions need a person.

An expert can help you map your agents' actions to the right approvers.