Where to reply: Salesforce vs your sales engagement platform
When to use this guide: Use this guide when your team is deciding where sales reps should send follow-up replies after outbound activity syncs into Salesforce — regardless of which sales engagement platform (SEP) you use.
What appears on the Lead or Contact
Section titled “What appears on the Lead or Contact”OutboundSync writes outbound engagement onto a Lead or a Contact (and related Account when applicable). You choose that person object on the webhook. Unlike HubSpot, Salesforce has no OutboundSync timeline/app-event surface — activity history is the Task or EmailMessage you configure, plus field updates on the person record.
Pick one activity object per webhook: Task Object or EmailMessage Object. Do not expect both for the same events.
| What OutboundSync writes | Typical shape | Replyable inside Salesforce? | Primary purpose |
|---|---|---|---|
| Task | Default Task Type Email for email SEPs (or a configured default/custom Type); social platforms use Task only | No — history and reporting, not a send UI | Activity Timeline, reports, queues, Flows |
| EmailMessage | Enhanced Email record with Status Sent | No — stored email history, not a composer thread | Email-shaped timeline visibility |
| Lead / Contact field updates | Campaign, category, last-activity style fields | No | Flow entry criteria and reporting |
Task logging is the recommended default for most orgs. OutboundSync creates a completed Task with a configurable subject line and a Type such as Email (or another value your org allows). That Type is a Salesforce activity picklist value — it is not Einstein Activity Capture and it does not open a reply composer on the record. See Writing to the Task Object.
EmailMessage logging stores a more email-shaped record (Enhanced Email). Reps can read it on the Activity Timeline, but OutboundSync writes Status Sent for API-created messages — still not a place to hit Reply inside Salesforce. See Writing to the EmailMessage Object.
Automation usually reacts to a Task create (or update) and/or Lead/Contact field changes via Salesforce Flows. There is no HubSpot-style App Timeline Event enrollment trigger for OutboundSync events — but Task-based Flows are a normal Salesforce pattern when you log to the Task Object.
Because logged Tasks and EmailMessages are not a reply path, where the rep sends from is always outside that Salesforce activity card. The prospect replied to the sequencer mailbox, so the live thread is in the SEP until you hand it off with a reply relay or a manual CC.
Email replies
Section titled “Email replies”| Path | From address | Availability | Best when |
|---|---|---|---|
| Reply relay | Sequencer mailbox on the handoff, then rep primary inbox | Smartlead / EmailBison with Destinations | Place of work + deliverability edge + CRM sync |
| Reply in the SEP inbox | Campaign secondary sending domains | Any email SEP | Every follow-up must keep the original outbound identity |
| Manual SEP reply + CC | Campaign secondary domains, with the rep CC’d | Any email SEP | Same handoff into the primary inbox when a reply relay is unavailable |
Reply relay is a Destinations capability for Smartlead and EmailBison (setup guide). Instantly and other platforms are not supported yet. OutboundSync syncs the prospect reply to Salesforce immediately, then after the delay sends a short reply from the sequencer mailbox that CCs the sales-rep address. That is what puts the thread in the rep’s primary inbox — without the CC, there is nothing there to Reply-All on. Warmup and Unibox operations stay in the SEP; CRM sync is not replaced by the handoff.
After the handoff, later primary-inbox sends can optionally land back on the Lead/Contact through Salesforce’s official Outlook and Gmail integrations (often with Enhanced Email), Einstein Activity Capture / Sync Email as Salesforce Activity, or a third-party logger. Those tools are separate from OutboundSync’s Task/EmailMessage writes.
Reply in the SEP inbox keeps every follow-up on campaign secondary domains. Those sends appear in Salesforce only if the platform emits a manual-send webhook. See Which platforms sync manual outbound replies.
Manual SEP reply + CC is the agency pattern when a reply relay is unavailable: reply in the SEP and CC the rep’s primary address so the next Reply-All can continue in the primary inbox. Prefer the automated reply relay on Smartlead/EmailBison when Destinations is enabled.
Social replies
Section titled “Social replies”Social SEP events sync as Tasks (plus Lead/Contact field updates). Salesforce has no native “reply from this social Task” path for sequencer threads.
Reps send social follow-ups in the SEP Unibox (for example HeyReach) or in the native social selling platform. Manual outbound messages sync back only when the platform webhooks them — see the HeyReach webhook guide.
Which platforms sync manual outbound replies
Section titled “Which platforms sync manual outbound replies”Email manual sends from the SEP only. Social follows Social replies.
If the platform does not webhook the send, Salesforce will not show it unless another logger captures the mailbox. Prefer a reply relay when Destinations is enabled on Smartlead or EmailBison, the SEP Unibox for forever-secondary sends, or a manual SEP + CC handoff when you need the primary inbox without Destinations.
| Platform | Manual outbound replies sync? | Notes |
|---|---|---|
| Smartlead | Yes | Enable Manual Reply Sent — webhook guide |
| EmailBison | Yes | Manual sends — EmailBison integration |
| HeyReach | Yes (social) | Message Sent — HeyReach webhook guide |
| Instantly | No | Inbound replies sync; manual Unibox outbound replies do not webhook back |
| Other SEPs | Varies | See Engagement integrations |
Choosing a path
Section titled “Choosing a path”
Prefer a reply relay on Smartlead or EmailBison
Section titled “Prefer a reply relay on Smartlead or EmailBison”When Destinations is enabled, a reply relay is usually the best default:
- Place of work — After the handoff, Reply-All lands in the rep’s primary inbox.
- Deliverability edge — The loop-in still sends from the sequencer mailbox.
- SEP inbox management stays intact — Warmup and rotation stay in Smartlead or EmailBison.
- CRM sync stays immediate — The prospect reply is already a Task or EmailMessage on the Lead or Contact before the CC fires.
Manual CC when Destinations is off
Section titled “Manual CC when Destinations is off”Without a reply relay, reading the Lead/Contact in Salesforce does not put the email thread in Gmail or Outlook. Use a manual SEP reply + CC if you still want the rep to continue from their primary inbox, or stay in the SEP Unibox for every follow-up.
Deliverability-strict / secondary-address continuity
Section titled “Deliverability-strict / secondary-address continuity”If every follow-up must keep the campaign secondary address, stay in the SEP Unibox or a unified inbox such as HotHawk or Masterinbox. A reply relay (or manual CC) is a handoff into the primary inbox — not a forever-secondary path.
Flows are not send-address routing
Section titled “Flows are not send-address routing”Salesforce Flows can fire on Task create, Lead/Contact field changes, and related automation after a reply syncs. They assign owners, create follow-up Tasks, and branch logic — they do not choose which mailbox the rep sends from. Decide the send path above, then build Flows.
