Back to Workflow Platform
Human Handoff

Escalate from automation to humans without losing the workflow

Automation works best when handoff is part of the design. Calypso lets workflows escalate to humans with conversation history, workflow state, and inbox-aware controls still intact.

Human handoffConversation historyWorkflow stateInbox contextRouting controls
Workflow signals
Inbox-ready
Handoff in context
Stateful
Workflow memory preserved
Hours-aware
Routing controls available

Why handoff belongs inside the workflow

The best automation systems know when to stop, who should take over, and what context must come with the handoff.

Escalate with context

Hand the conversation to a human without dropping the workflow state or the conversation history.

Use inbox-aware routing

Default flows, inbox handoff nodes, and routing policies make escalation part of the system design.

Respect hours and operations

Bot hours and post-handoff agent hours controls help the workflow behave correctly outside normal coverage.

Where handoff matters most

Human escalation is not a failure mode. It is a designed part of a high-performing workflow.

Complex support cases

Escalate only when the issue needs review, while preserving what happened in the workflow before handoff.

Sales conversations that need a closer

Let automation qualify and route, then pass the opportunity to the right human when it is ready.

Off-hours or policy-sensitive conversations

Use workflow policies to decide when to stop automation and what message should come next.

How handoff works in the product

Handoff is connected to routing, default flows, inbox visibility, and hour-based controls.

Handoff inside the policy layer

Catch-all and workflow policies can decide when to return, message, or escalate.

Default flow aware

Inbound routing and default flow decisions affect how and when a workflow can be unpublished or replaced.

Operations-aware controls

Post-handoff agent hours and bot hours gates help teams run workflows with realistic coverage rules.

Design escalation into the workflow from day one

Keep automation and human takeover in one operational system with shared context and clear routing rules.