Agentforce Agent Handoff Patterns

Agentforce Agent Handoff Patterns

Most agent failures are handoff failures. The agent knew it was stuck, did not have a clean way to transfer the conversation, and either looped, hallucinated, or dumped the user into a cold queue without context. Good handoff design treats the transfer as a first-class capability with its own triggers, its own context schema, and its own messaging — not as "throw an error and let Omni-Channel figure it out."

Three kinds of handoff matter: agent-to-human (Omni-Channel), agent-to-agent (swap persona, specialization, or domain), and agent-to-workflow (spawn a case, route to a Flow, schedule a callback). Each has different mechanics but shares the same design skeleton: trigger → context package → user message → receiver acknowledgment → (optional) hand-back.

Terminology. Subagent is the April 2026 rename of topic. Functionality did not change and the API surface did not rename — the metadata type is still GenAiPlugin, and the skill slug agentforce/agent-topic-design keeps the older word.

Before Starting

• List the handoff triggers expected for this agent (policy, confidence, scope, authorization, user request).
• List destinations and what each needs to take the conversation from here.
• Confirm Omni-Channel queue structure and presence model.
• Confirm whether hand-back (returning to the agent after human resolution) is a requirement.

Core Concepts

Handoff Trigger Types

1. User-initiated — "I want to speak to a person."
2. Confidence-based — agent is unsure after N attempts.
3. Scope-based — user crossed into a topic this agent does not cover.
4. Policy-based — refund > threshold, fraud flag, VIP customer.
5. Authorization-based — action requires manager or regulated approval.
6. Technical — system unavailable, data missing.

Context Package

The handoff receiver needs:

• Original user intent and paraphrased summary.
• Data the agent gathered (account, policy, case numbers).
• Actions attempted and their outcomes.
• Why the handoff fired.
• A conversation transcript link, not the raw transcript in the payload.

Destinations

User Messaging

Every handoff needs an explicit user message that says what is happening and what to expect. "Let me connect you with an agent" is better than silence. Predicted wait time (if known) is better than vague.

Hand-Back

If the agent will resume after human resolution (common in hybrid service models), the hand-back protocol must preserve or summarize what the human did.

Common Patterns

Pattern 1: Structured Escalation To Omni-Channel

On trigger: create a case with a structured description, route to the queue, deliver a friendly transfer message, end the agent session. The case captures the context package in a standard format.

Pattern 2: Warm Agent-To-Agent Handoff

One agent hands to another without losing conversation continuity. The receiving agent reads a summary (not the verbatim history) to avoid token bloat and topic confusion.

Pattern 3: Confidence-Triggered Escalation

After 2 unsuccessful resolution attempts on the same intent, fire escalation. Avoids infinite loops where the agent keeps retrying the same failing path.

Pattern 4: Authorization Gate Handoff

For actions beyond the agent's authority (e.g. refund > limit), pause, hand to an approver (human or approval process), resume on approval.

Pattern 5: Deflection-With-Recommendation

If no suitable human is available or the query is out-of-scope with no sensible destination, do not queue indefinitely. Provide a clear next-best-action (support link, callback scheduler).

Decision Guidance

Review Checklist

• Each handoff trigger has a destination.
• Context package schema is documented.
• User message per handoff type is written.
• Confidence-based escalation is configured.
• Deflection path exists when no human is available.
• Hand-back protocol is designed if applicable.

Recommended Workflow

1. List handoff triggers relevant to this agent.
2. Map each to a destination.
3. Design the context package (fields, format, size).
4. Write user messaging per handoff type.
5. Implement the transfer mechanism (case creation, queue route, workflow spawn).
6. Verify hand-back works if required.

Salesforce-Specific Gotchas

1. Omni-Channel routing honors agent presence; if no one is available, the conversation can sit indefinitely unless you add fallbacks.
2. Case routing by owner vs queue has different audit trails.
3. Context dumped as raw text into a case description is unsearchable and bloats storage.
4. Agent-to-agent handoff resets subagent context — the new agent does not see the previous subagent's instructions.
5. Hand-back requires the original agent session to still be alive, or you need an explicit resumption mechanism.

Proactive Triggers

• No confidence-based escalation configured → Flag High. Loops likely.
• Context package is raw transcript dump → Flag Medium. Human agents drown in it.
• No deflection path when queues are empty → Flag High. Users stuck.
• Authorization-gated actions with no handoff → Flag Critical. Agent may act outside authority.
• Hand-back not designed when needed → Flag Medium.

Output Artifacts

Related Skills

• agentforce/agent-topic-design — subagent scope that informs scope-based handoffs.
• agentforce/agentforce-guardrails — guardrails that fire authorization handoffs.
• admin/omni-channel-routing-setup — destination queue design.
• agentforce/agentforce-service-ai-setup — service-agent integration.