Control and approvals

# Confidence is not permission.

An agent can be sure of itself and still not be allowed to act. Every action declares its risk, you set how far each agent may go alone, and anything beyond that waits for a person.

Autonomy

## Every action carries a weight. You set the line.

Drag the line to change this example agent's autonomy and see which actions it may take alone.

Autonomy

Cautious

Read a ticket, email or record

Automatic

Send a routine reply

Automatic

Update a customer record

Asks an approver

Issue a credit note

Asks an approver

Illustrative weights. In the product each action's risk is declared by its connector.

Safeguards

## People stay in charge.

### Approvals

Proposals above an agent's autonomy go to an approver group, with the agent's reasoning attached. Some actions can need two approvers.

### Kill switches

Stop an agent at once. Nothing more runs until someone switches it back on.

### Run inspector and audit log

Open any run and see what triggered it, what the agent read and decided, and who approved what.

### Tested before go-live

Every template ships with evals, and every agent can be simulated and tried in a sandbox first.

### Kept apart

Each organisation's agents work only within its own data, tools and knowledge base.

### Run by Netavo

A UK telecoms and cloud provider. Records are held in the UK; agent processing and live calls run in Germany.

## Questions aboutsecurity?

Talk to us about how agents are controlled, where data is held and how approvals work.

[Talk to us](https://intelligence.netavo.com/contact)

Source: https://intelligence.netavo.com/control
