Documentation
DelegateZero (DZ) is a system for delegating decisions.
It sits between incoming requests (messages, approvals, questions, events) and the actions that would normally require human intervention. Instead of hard-coding workflows or rules, DelegateZero evaluates each situation using context you provide and returns a decision outcome so that it can handle decisions the same way that you would.
Those decisions are always one of the following:
- Execute — take action automatically
- Draft — prepare a response for review
- Escalate — defer to a human with explanation
DelegateZero does not replace your judgement, it simply acts as a representative for your decisions.
What DelegateZero is not
- It is not a workflow engine. You do not set up workflows, steps and integrations through DZ. Intead, you add DZ to your existing workflows whenever human intervention is normally required.
- It is not a chatbot that replies without guardrails. DZ, acting as your representative, responds how you would based on the context provided.
- It is not a rules-only automation system. It is not reliant on a set of conditions. DZ makes decisions based on it's knowledge of you, your roles, how you think, and what you would do based on the information you provide.
DelegateZero is designed for situations where context matters, rules are incomplete, and decisions are repetitive but not identical.
How DelegateZero fits into your systems
DelegateZero is typically added to a workflow when a decision may not be clear - or to join automations that were previously disconnected due to relying on human interaction. A few examples include:
- When an employee asks for approval in Slack or email
- When a customer requests an exception
- When a system flags an operation that needs review
- When an internal service needs a go/no-go decision
- When an email needs to be sent but needs a review first
Instead of routing these directly to a human, you send them to DZ. DZ evaluates the request and returns the decision, a confidence score, and the reasoning behind the outcome for your review whenever desired.
How DelegateZero makes decisions
DelegateZero does not reason in isolation or based on generic knowledge. It uses context you provide, including:
- Specific rules and boundaries: Based on your experience, there are certain times when you'd always respond to a request in the same way.
- Examples of past decisions: For similar requests, answer with similar responses, all other things being equal.
- Information about people or accounts: The kind of information they want or need, or the specific services being offered.
- Guidelines for ambiguous situations: Based on various circumstances, here is what the solutions look like.
- References such as emails, documents, live feeds: For this type of decision, first pull the live data from this other platform, then take that information into account.
Context can be added or updated at any time, and should be updated regularly.
Safety by default
DelegateZero is conservative by default. If it does not have enough context or confidence to act safely, it escalates. It will never silently guess.
You control when it can act, when it should draft, when it should respond but act as your assistant, and when it must escalate directly to you.
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.