Configuring autonomy levels
Decide which AI actions are only suggested, approved with one click or executed automatically – with limits and customer-specific rules.
Nesta página
The four levels
- L0 – Observe: log only.
- L1 – Suggest: a person reviews and corrects.
- L2 – Approve: one-click confirmation. Functionally identical to L1, but signals “just confirm”.
- L3 – Automatic: executed immediately, owners/administrators/dispatchers are notified, undo via rollback.
Rule matrix and default levels
The rule matrix card shows, per action type (27), the agent, action, level, minimum confidence (0–1), default and customer-specific overrides. Changed rows are highlighted (“n unsaved changes”) and finished with save changes or discard.
| Default | Actions |
|---|---|
| L3 | thread.classify, document.classify, document.link, eta.update, control.escalate |
| L2 | order.create, thread.request_info, quote.create, invoice.create, invoice.approve_incoming, customs.assess, customer.notify_delay |
| L1 | All others, incl. order.update, order.cancel, thread.reply, tour.assign, assignment.request, assignment.confirm, invoice.send, customs.classify_hs |
Limits (constraints)
Limits only apply when the level is L2 or L3. If one is violated, the proposal falls back to L1 (risk policy: … on the card). They are checked in the order confidence → price → margin deviation → countries.
| Limit | Where to set | Checked against |
|---|---|---|
minConfidence | Minimum confidence field | Proposal confidence |
maxPriceCents | API only | Price or sum of lines in the proposal |
maxMarginDeviationPct | API only | Currently has no effect (value not populated) |
allowedCountries | API only | All stop countries must be included |
Nota: API example: PUT /autonomy-policies with { "agent": "MAIL", "actionType": "order.create", "level": "L3_AUTO", "constraints": { "minConfidence": 0.85, "maxPriceCents": 150000, "allowedCountries": ["AT","DE","CH"] } }.
Customer-specific overrides
Add override: partner (required), action, level, minimum confidence. Precedence: partner rule over tenant-wide rule over default. The partner of a proposal is the customer or carrier of the order concerned. Remove deletes the override.
Recommendations
| Phase | Recommendation |
|---|---|
| Weeks 1–2 | Keep the defaults – the L3 actions are fully reversible or purely informational. |
| From week 3 | Check per action: approval rate ≥ 95 %, rollback rate < 2 %, ≥ 50 decisions → raise by one level. Start with partner-specific rules for regular customers with clean order emails. |
| Guide values for minimum confidence | order.create 0.85 · quote.create 0.8 · invoice.approve_incoming 0.9 · customer.notify_delay 0.75 |
| Warning signs | Rollback rate > 5 % → lower the level; more than 20 % expired proposals → check relevance; “auto-execution failed” > 2 % → check preconditions |
Nota: Never set to L3: order.cancel, invoice.send, assignment.confirm, quote.send, customs.prepare, invoice.dispute – they cannot or can only partly be rolled back (emails, external effects). Proposals expire after 72 h.
Artigos relacionados
- AI proposals and autonomy levelsWhy agents and the Copilot only make proposals, what levels L0–L3 mean and how to accept, reject or undo proposals.
- Setting up your company (tenant)Maintain master data, number ranges, bank details, AI instructions, defaults and branding – plus the recommended setup order.
- Troubleshooting for administratorsTypical symptoms – from mock mode and missing emails to webhook and sign-in problems – with cause and fix.