Platform

Delegation is a dial, and there's a kill switch.

Trust is earned in steps. A new coworker starts by watching. When its drafts hold up, it suggests — a person approves every send. When the record is proven, it executes inside policy, and exceptions still route to review. You move the dial per agent and per workflow, and you can halt any agent instantly, without a ticket.

Support Reply · Autonomy

Monthly budget

$763 of $1,200

Access

Zendesk · Docs · Slack

Least privilege · read + draft only

Suggesting: every output waits for a named person — the default for anything customer-facing.

Three levels, one record

  • Watch — observes and reports. Touches nothing. The right start for every new role.
  • Suggest — drafts the work; a named person approves every output before it moves.
  • Execute — acts inside policy, with budgets and least-privilege access; anything unusual comes back to a human.

Every level writes the same audit record, so moving the dial never costs you the trail.

Policy is written down, then enforced

Budgets, access scopes, approval requirements, and autonomy thresholds live as policy code (Cedar — the same policy language AWS uses), versioned next to the agent it governs. The platform enforces it on every run; nobody has to remember it.

The kill switch is an operations control, not an engineering task

Any operations lead can pause a single agent or halt it entirely from the registry. In-flight work stops at the next checkpoint, pending approvals stay in the inbox, and the record shows who pulled the switch and when.

enforcedearn itearn itPolicybudget · access · kill switchWatchobserves, touches nothingSuggestdrafts, person approvesExecuteacts inside policySame audit recordat every level
One policy rail governs all three levels — trust moves the dial, the record never changes.✦ hover a step

Keep exploring

Get a demoRead the docsView source