Approvals and escalations

Set the boundaries.
Stay in control.

Choose when agents can act and when they need approval. Spending and deletion actions still require a decision.

Start on watch onlyMove to ask me firstLet it run

Business context

Specialist agent

Per seat, not per account

Your researcher can run while your outbound seat stays on ask me first. One setting for everything is not a control.

Money always asks

Any paid action, refund, charge or spend goes to a person regardless of mode. There is no setting that turns this off.

Escalation with context

When something is escalated the person gets the work so far, not a notification saying an agent needs you.

Undo after the fact

Approving something and changing your mind is one click, not a support ticket.

How it works.

The seat does the work and changes nothing. You read a fortnight of runs and decide whether you agree with them.

It proposes, you approve. Approvals arrive where you already are, with what it wants to do and why.

For the parts you trust. The trace and the undo are still there, and money and deletion still ask.

Scope and boundaries

Approvals slow things down. That is the point, and it is the trade you are making.
We cannot undo an action a third party tool treats as final. Where that is true, the seat asks first no matter the mode.
An approval is a person accepting responsibility. We log who approved what, and that log is append only.