Handoff
Handoff in the Salesforce context refers to the structured transition of a record (a Lead, an Opportunity, a Case, or an Order) from one team or role to another, with the receiving team picking up the work where the previous team left off.
Definition
Handoff in the Salesforce context refers to the structured transition of a record (a Lead, an Opportunity, a Case, or an Order) from one team or role to another, with the receiving team picking up the work where the previous team left off. The concept is generic across the platform: SDR-to-AE lead handoffs in sales, sales-to-service post-sale handoffs, tier-1-to-tier-2 case escalations, and presales-to-implementation engineering handoffs all share the same pattern. Salesforce does not ship a single Handoff feature; it provides a set of building blocks (Queues, Assignment Rules, Approval Processes, Flow Orchestration, Path, Chatter, and the Conversation Insights features in Service Cloud) that admins assemble into a handoff workflow.
A typical handoff combines four ingredients: a record-level signal that triggers the handoff (a Stage change, an SLA breach, a custom button), a reassignment action that updates the OwnerId or the Owner field to the receiving team or queue, a notification to the receiving team via email, Chatter, mobile push, or Slack, and a context-capture mechanism that documents what the previous team did so the receiving team can pick up cold. The Handoff term is also used heavily inside Salesforce Industries (Health Cloud patient handoffs, Financial Services Cloud advisor handoffs) where the receiving team needs more structured context than a simple owner change provides.
The four ingredients of any well-designed Salesforce handoff
The trigger
Every handoff starts with a trigger. In sales, the trigger is usually a Lead Status change (Qualified, MQL-to-SQL) or an Opportunity Stage change (Discovery to Proposal). In service, it is a Case escalation rule firing or an SLA timer expiring. The trigger is the moment the record stops being owned by Team A and needs to be owned by Team B. Capture the trigger as a precise condition (Stage = ''Negotiation/Review'' AND Amount > 100000) so the handoff fires consistently.
The reassignment
Reassignment changes the OwnerId on the record. Salesforce offers several mechanisms: an Assignment Rule (Leads, Cases), a Queue, a flow Assignment element, or a manual change. The receiving owner can be a user, a queue, or a role member. Queues are the right answer when any member of a team can pick up the work; specific users when a single individual is accountable. Reassignment fires Apex triggers and flow rules on the record, so design downstream automation accordingly.
The notification
The receiving team needs to know the handoff happened. The notification ranges from a simple Email Alert (built into Assignment Rules) to a Slack message (via the Salesforce-Slack integration) to a Chatter @-mention on the record. Mobile push notifications can also fire when ownership changes. Pick a notification channel that matches where the receiving team works; sending a service team a Chatter post when they live in Slack guarantees the notification is missed.
The context capture
Reassigning a record without context is the most common handoff failure. The receiving team needs a brief, recent, structured summary of what happened. Use a custom field (Handoff Notes), a Chatter post template, or a Conversation Insights summary to capture the context. Service teams often use a Quick Action with required fields. Sales teams put the summary in a dedicated rich-text field on the Opportunity. The discipline is universal: no handoff without context.
Flow Orchestration for multi-step handoffs
When the handoff involves multiple steps across multiple teams (Lead routed to SDR, qualified Lead handed to AE, closed Opportunity handed to CSM, signed Contract handed to Implementation), Flow Orchestration is the right tool. Each stage is a team, each step a flow, and the orchestration enforces the sequence and the context capture. Without orchestration, multi-team handoffs become a tangle of point-to-point automations.
Industry handoffs and structured context
Salesforce Industries (Health Cloud, Financial Services Cloud, Public Sector) ship structured handoff patterns. Health Cloud has a Care Plan template that travels with the patient between care teams. Financial Services Cloud has an Action Plan that documents an advisor''s next steps for the client. These industry-specific tools encode the context capture into the data model so the receiving team gets a structured, repeatable picture rather than free-form notes.
SLA and accountability after handoff
The receiving team needs an SLA: a defined window within which they should take action. Without an SLA, handoffs go to a queue and sit. Combine the reassignment with a time-triggered flow that escalates back to a manager if no action is taken within (for example) 24 hours. This pattern is universal in well-functioning service teams and increasingly common in sales workflows.
Design a Lead-to-Opportunity handoff
The SDR-to-AE handoff is the canonical example. Build it once well, then reuse the pattern across other handoffs in the org.
- Define the trigger condition
Decide what makes a Lead handoff-ready. Common criteria: Lead Status = MQL, BANT fields complete, Custom Qualified Date populated. Document the condition in writing before building anything.
- Build the receiving queue or assignment
Create a Public Group of AEs, set up a Queue or Round Robin Assignment Rule, or use a flow Assignment element to pick the right AE based on territory.
- Add a Handoff Notes field
Create a rich-text Handoff Notes field on Lead. Make it required when Status changes to MQL. This is the context-capture layer; without it the AE gets a Lead and no context.
- Configure the notification
Email Alert is the baseline. Add a Slack alert via the Salesforce-Slack integration if the team works in Slack. Include the Handoff Notes in the message body.
- Build the SLA timer
Schedule-triggered flow that checks every two hours for Leads in MQL status owned by an AE for more than the SLA. If no Activity has been logged, escalate to the AE manager.
- Pilot, measure, iterate
Roll the handoff out to one territory first. Measure SLA compliance, AE feedback on context quality, and conversion rate from MQL to opportunity. Adjust based on what surfaces.
- Handoffs without context capture are the single most common reason receiving teams complain about the SDR-AE or sales-service handoff. Build the context field before building the automation.
- Reassignment fires triggers and flows on the record. Cascade effects (Owner-based sharing rules, email alerts, follow-up tasks) need to be designed in alongside the handoff.
- Queue-based handoffs work only if someone is incentivized to take from the queue. Without an SLA or an assignment rule, records sit in the queue until a manager intervenes.
- Notification channel mismatch kills handoff adoption. A service team in Slack will miss every Chatter notification; match the channel to the team.
Trust & references
Cross-checked against the following references.
- Queues OverviewSalesforce Help
- Flow OrchestrationSalesforce Help
Straight from the source - Salesforce's reference material on Handoff.
- Lead Assignment RulesSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Handoff in Service Cloud bots?
Q2. What should be passed during a handoff?
Q3. Why is handoff design important?
Discussion
Loading discussion…