Approvals & Escalation

Add approval chains and escalation paths to any operation with Forest

Add approval chains and escalation paths to any operation with Forest

Add approval chains and escalation paths to any operation with Forest

Add four-eyes review to any action, inbox task, or workflow step, and keep a human in the loop. Define who approves, when escalation kicks in, and how the chain is recorded.

TL;DR

Forest adds four-eyes review and human-in-the-loop checkpoints to any action, inbox task, or workflow step.

Your team defines who approves, when a case escalates, and how the chain is recorded. Automated runs that need a person land in a fallback inbox.

Approvals can require multiple levels, and every decision is recorded against the record.

Structured review on every action, workflow step, and inbox task

Structured review on every action, workflow step, and inbox task

Approvals and escalation rules apply wherever a decision needs a second pair of eyes, and keep a human in the loop when automation runs.

Four-eyes approval on actions

Sensitive actions (refund above a threshold, account freeze, status override) can require approval before execution. The person who asks is not the person who signs, unless you allow self-approval.

Inbox escalations

Operators can escalate a case to a different inbox when they hit something outside their scope. Automated workflow runs that need a person, or fail, land in a fallback inbox, flagged as escalated.

Workflow approvals

An approval step inside a workflow blocks progress until the right reviewer signs off.

Multi-level chains

Approval can require multiple levels: first reviewer, second reviewer, manager, compliance.

Role and condition based

Who approves depends on the action, the amount, the customer segment, the jurisdiction. Configurable per step.

Audit-ready chain

Every approval, rejection, and escalation is recorded with timestamp, actor, and reason against the case record.

Built for sensitive operations

Approval chains and escalations that match how you actually work

Approval chains and escalations that match how you actually work

Role-based validation

Approval authority follows the roles you define for your team and your AI agents. Configuration, not custom code.

Granular per action and segment

Approval thresholds adapt per action, per workflow step, per customer segment, per jurisdiction.

Chains regulators can follow

Every approval, rejection, and escalation is recorded with the actor, the timestamp, and the reason. The chain is part of the case.

Whenever there's a doubt, whenever there's a suspicious case, the idea is to escalate it to a team of experts internally.

Maxime de Juniac

Chief Service Officer

Whenever there's a doubt, whenever there's a suspicious case, the idea is to escalate it to a team of experts internally.

Maxime de Juniac

Chief Service Officer

Whenever there's a doubt, whenever there's a suspicious case, the idea is to escalate it to a team of experts internally.

Maxime de Juniac

Chief Service Officer

Frequently asked questions

You still have question ?
Book a conversation with a forest expert

Where can approvals be applied?

Approvals can be applied to standalone Actions, to Inbox-dispatched record tasks, and to steps inside Workflows.

How do I set up four-eyes review?

In Project Settings, give the requesting role Require approval on the action, give reviewers Approve, and leave Self Approve off. The requester can then never sign their own request.

How does Forest keep a human in the loop?

In three places. Actions that require approval wait for a person to sign. Escalation steps hand a workflow run to an inbox. Automated runs that need a person, or fail, land in the fallback inbox. AI agents go through the same approvals as operators.

Can we build multi-level approval chains?

Yes. Chains can require multiple levels of approval, each with its own role or condition. The order is configurable.

How does escalation work?

When an operator can't complete a task, or when an approval is overdue, the record can be escalated to another inbox or to a manager. Escalation rules are configured per inbox or per workflow step.

What happens to an automated run that needs a person?

It goes to the workflow's fallback inbox, flagged as escalated. An operator picks it up and resumes the run from the step where it stopped, under the same dispatch rules as your other inboxes.

Is the approval chain auditable?

Yes. Each approval, rejection, or escalation is recorded with the actor, the timestamp, and any reason given. The chain is part of the case's audit trail.

Can we export the approval history?

Yes. Export processed requests over a period to CSV from the History list. Every approval is also in your activity log, available through the public API.

Can AI agents be approvers?

Approval authority is typically held by humans, but AI agents can be used in chains for routine pre-approvals (e.g. an AI agent flags a case as eligible before a human signs off). The AI agent's reasoning is part of the chain.

How do you ensure customer data never leaves our environment?

The Forest back-end runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record.

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Where can approvals be applied?","acceptedAnswer":{"@type":"Answer","text":"Approvals can be applied to standalone Actions, to Inbox-dispatched record tasks, and to steps inside Workflows."}},{"@type":"Question","name":"How do I set up four-eyes review?","acceptedAnswer":{"@type":"Answer","text":"In Project Settings, give the requesting role Require approval on the action, give reviewers Approve, and leave Self Approve off. The requester can then never sign their own request."}},{"@type":"Question","name":"How does Forest keep a human in the loop?","acceptedAnswer":{"@type":"Answer","text":"In three places. Actions that require approval wait for a person to sign. Escalation steps hand a workflow run to an inbox. Automated runs that need a person, or fail, land in the fallback inbox. AI agents go through the same approvals as operators."}},{"@type":"Question","name":"Can we build multi-level approval chains?","acceptedAnswer":{"@type":"Answer","text":"Yes. Chains can require multiple levels of approval, each with its own role or condition. The order is configurable."}},{"@type":"Question","name":"How does escalation work?","acceptedAnswer":{"@type":"Answer","text":"When an operator can't complete a task, or when an approval is overdue, the record can be escalated to another inbox or to a manager. Escalation rules are configured per inbox or per workflow step."}},{"@type":"Question","name":"What happens to an automated run that needs a person?","acceptedAnswer":{"@type":"Answer","text":"It goes to the workflow's fallback inbox, flagged as escalated. An operator picks it up and resumes the run from the step where it stopped, under the same dispatch rules as your other inboxes."}},{"@type":"Question","name":"Is the approval chain auditable?","acceptedAnswer":{"@type":"Answer","text":"Yes. Each approval, rejection, or escalation is recorded with the actor, the timestamp, and any reason given. The chain is part of the case's audit trail."}},{"@type":"Question","name":"Can we export the approval history?","acceptedAnswer":{"@type":"Answer","text":"Yes. Export processed requests over a period to CSV from the History list. Every approval is also in your activity log, available through the public API."}},{"@type":"Question","name":"Can AI agents be approvers?","acceptedAnswer":{"@type":"Answer","text":"Approval authority is typically held by humans, but AI agents can be used in chains for routine pre-approvals (e.g. an AI agent flags a case as eligible before a human signs off). The AI agent's reasoning is part of the chain."}},{"@type":"Question","name":"How do you ensure customer data never leaves our environment?","acceptedAnswer":{"@type":"Answer","text":"The Forest back-end runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record."}}]}

Approvals & Escalation

LEVEL UP YOUR OPS GAME

One control plane. Every action traced for human, agent, BPO, LLM, workflow.

Approvals & Escalation

LEVEL UP YOUR OPS GAME

One control plane. Every action traced for human, agent, BPO, LLM, workflow.

Approvals & Escalation

LEVEL UP YOUR OPS GAME

One control plane. Every action traced for human, agent, BPO, LLM, workflow.

The operational infrastructure regulated companies grow on

Copyright ยฉ 2026 Forest

Design by Alasta & Built by Reiya Studio