Trailblazer Community
Feed

Getting Started

  • What is Trailhead
  • myTrailhead
  • Trailblazer Community
  • Career Growth

Learn

  • Trails
  • Trailmixes
  • Modules
  • Projects

Credentials

  • Superbadges
  • Certifications
  • Maintain Certifications

Salesforce

  • Salesforce.com
  • AppExchange
  • Developers
  • Help Portal
© 2026 Salesforce, Inc. All rights reserved. Privacy Terms of Use Trust Accessibility Cookie Preferences
  1. Feed
  2. Post
AS
Akash Sharma
Salesforce Administrator · 2 hrs ago
Asked in Agentforce Builders

Best pattern for handing off from Agentforce to a human agent mid-conversation?

Specifically: when my agent identifies a deal over $100K or detects a "let me talk to someone" intent, I want it to drop into a watchful state and assign the conversation to the right AE based on territory rules. The agent should still see what the human types, but stop generating replies.

Two questions: (1) what's the right Omni-Channel routing config for this — capacity model, presence, or a custom skill? (2) has anyone solved the "agent silently watching" UX so the customer isn't confused by the handoff?

Discuss this in Slack for faster answers and real-time help.

14 replies · preview from Slack

Accepted answer
MI
Mia Iyer
Senior Architect · Salesforce MVP · 1 hr ago

Capacity model + a custom skill for 'AE-routable-deal' is what's worked for us. We don't keep the agent in the conversation mid-stream — it posts a structured handoff summary as the first message in the new conversation, and the AE picks it up cold with the full context attached. Cleaner than 'silent watching'.

JY
Jasmine Young
Senior Salesforce Administrator · 2 hrs ago

+1 to the structured handoff summary. The 'silent watching' pattern confused customers in our pilot — they kept asking 'are you still there?' when the agent went quiet. A clean explicit handoff with a one-line acknowledgement from the AE worked much better.

EO
Emeka Okonkwo
Salesforce Administrator · 2 hrs ago

If you want the handoff to feel instant, pre-warm the Omni-Channel queue by routing the deal evaluation as a Lead first. The agent qualifies, the AE inherits a routed Lead with the full transcript attached. Saves you the routing latency on the conversation itself.

Active in Slack

Conversation lives in #agentforce-builders. Open Slack to post, reply, and react.

About the asker

AS
Akash Sharma
Salesforce Administrator
Adventurer

Related learning

  • Trail
    Build an Agentforce Sales Agent
  • Badge
    Agent Handoff Patterns
  • Trail
    Omni-Channel Routing Foundations

Related threads

  • How are you grounding Agentforce responses without leaking PII into the prompt?
    19 replies
  • Identity resolution rulesets — when to use deterministic vs. probabilistic?
    27 replies
  • Service Cloud Voice transcripts as Agentforce prompts — anyone tried it?
    6 replies