SYS OPERATIONAL Log in Get started
Start here Overview Quickstart Chat
Context Adding context Policies Precedents Memory Entities Playbooks Templates Sources Context freshness Best practices
Decisions Request structure Response structure API reference Authentication Request object Response object Context via API Webhooks Audit logs
Integrations Overview Slack Gmail Linear Proactive queue
Advanced settings Confidence & escalation Policies & safety Risk levels Assistant attribution Confidence Autopsy Context-Building Notifications Judgement Coaching Decision Simulation Judgment Benchmarking Profiles Judgment Profiles Delegation Chains
Support & reference FAQs Debugging decisions Why something escalated Improving confidence Security & privacy Changelog LLMs.txt

Why something escalated

Escalation occurs when DelegateZero cannot safely act on your behalf. Common reasons include:

  • Confidence below the required threshold
  • Missing required context
  • A policy or hard stop was triggered
  • Conflicting signals from prior precedents
  • High-risk or irreversible actions

Escalation is a feature, not a failure. It protects you from unintended actions.

There are no results for that search on this page, however, if you press the enter key then our entire documentation will be searched and you will receive the results. If you need assistance, please contact us.