Where to reply: HubSpot 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 HubSpot — regardless of which sales engagement platform (SEP) you use.

What appears on the contact record

A HubSpot contact record can show several activity types related to outbound engagement. They look similar on the timeline but serve different purposes — and only native email activities are a reply path for sequencer email.

Activity type	Typical source	Replyable from contact record?	Primary purpose
Native email activities	HubSpot one-to-one email logging; OutboundSync writes sequencer email here	Yes — sends from the rep’s primary connected inbox	Pick up email threads in the CRM
Native LinkedIn communications	OutboundSync writes HubSpot Communications (`LINKEDIN_MESSAGE`) for social events that include message text	No — not a sequencer reply path	Message history on the timeline alongside OutboundSync app events
Native social interactions	HubSpot Marketing Social inbox (brand account DMs, comments, mentions)	No — not for outbound-sequencer prospecting threads	Inbound brand social on the timeline
OutboundSync timeline/app events	OutboundSync integration webhooks	No — metadata and workflow triggers only	Campaign history, reporting, automation

Native email activities are HubSpot’s replyable one-to-one email cards. OutboundSync logs sequencer sends and replies here for email platforms. Reps can send and reply from the contact record, but the message goes out from the rep’s primary HubSpot-connected inbox — not the sequencer’s secondary sending address. See the HubSpot tier guide for how sends and replies are logged as native email activities.

Native LinkedIn communications are HubSpot Communications objects with channel type LinkedIn. When OutboundSync syncs social SEP activity that includes message body (sends, replies, connection notes), it can create these cards in addition to OutboundSync timeline/app events. Each HubSpot user must enable LinkedIn under Filter activity to see them — see Contact timeline events in HubSpot. They are not a reply path for sequencer threads.

Native social interactions are HubSpot’s own Marketing Social activity type. When you associate a contact with an interaction from your connected brand accounts, HubSpot logs comments, mentions, and DMs on the contact timeline (Associate contacts with social interactions). That workflow serves inbound brand social — not outbound-sequencer prospecting threads. You cannot pick up a sequencer social thread from the CRM record the way you can with a native email activity.

OutboundSync timeline/app events are integration events HubSpot surfaces on CRM timelines (App events overview). OutboundSync writes campaign, step, and message metadata here and powers workflow enrollment (Integration event occurs). They are for history, reporting, and automation — not for sending replies. See Contact timeline events in HubSpot.

The right reply path depends on whether the engagement was email or social, whether your team prioritizes the rep’s primary inbox or secondary-address continuity, and whether your SEP emits webhooks for manual outbound sends.

Email replies

For email platforms, OutboundSync logs sequencer messages as native email activities on the contact timeline. Most teams pick one of the paths below — start with HubSpot or the SEP inbox, then consider a reply relay only if Destinations is enabled and your SEP supports it.

Path	From address	Availability	Best when
Reply in HubSpot	Rep’s primary HubSpot-connected inbox	Any email SEP	HubSpot-first teams; default for most customers
Reply in the SEP inbox	Campaign secondary sending domains	Any email SEP	Every follow-up must keep the original outbound identity
Reply relay	Sequencer mailbox on the handoff, then rep primary inbox	Smartlead / EmailBison with Destinations	Place of work + deliverability edge + CRM sync without living in the Unibox
Manual SEP reply + CC	Campaign secondary domains, with the rep CC’d	Any email SEP	Same outcome as a reply relay when Destinations or the SEP is unsupported

Reply in HubSpot means the rep answers from the logged email activity on the contact record. The message sends from their primary HubSpot-connected inbox (for example, company Gmail or Microsoft 365). HubSpot technically starts a new thread, but the subject line and recent messages carry over so the prospect experience stays coherent. See HubSpot’s guide on sending and replying to one-to-one emails.

Reply in the SEP inbox means the rep works in the platform’s unified inbox — for example, Smartlead’s master inbox or Instantly Unibox — so every follow-up keeps the secondary sending domains tied to the campaign. Those sends appear in HubSpot only if the platform emits a manual-send webhook. See Which platforms sync manual outbound replies below. For Smartlead, enable Manual Reply Sent on your webhook — it is one of the four core events in the Smartlead webhook guide. See Manual email replies available for Smartlead for setup details.

Reply relay is a Destinations capability for Smartlead and EmailBison only (setup guide). Instantly and other platforms are not supported yet. When a prospect replies, OutboundSync syncs to HubSpot immediately, then after the configured delay sends a short reply from the sequencer mailbox that CCs the sales-rep address. The prospect’s next Reply-All lands in the rep’s primary inbox (and typically in HubSpot via the connected inbox). Optional category/tag allowlists can limit which leads get the handoff. If Destinations is off or your SEP is unsupported, use Reply in HubSpot or Manual SEP reply + CC instead.

Manual SEP reply + CC is the agency pattern when a reply relay is unavailable: send from the SEP inbox and CC the rep’s primary address. HubSpot logs the CC’d message through the rep’s connected inbox, so the thread shows up in both places. It is especially useful on platforms that do not webhook manual outbound sends. For inbound Cc mapping on EmailBison payloads, see Handling Cc’ed email addresses. On Smartlead and EmailBison with Destinations enabled, prefer the automated reply relay over doing this manually.

HubSpot does log native social interactions on contact records when you associate a prospect with activity from your connected brand accounts. Those entries are not the same as OutboundSync social timeline events — and neither is a send path for outbound-sequencer follow-ups.

OutboundSync can also write native LinkedIn communications (HubSpot Communications with channel type LinkedIn) when social SEP events include message text. Enable LinkedIn under Filter activity to see them; they still are not a reply path for sequencer threads. See Contact timeline events in HubSpot.

Native social interactions cover inbound brand social managed in Marketing > Social (comments, mentions, and DMs to your brand accounts). Reps reply from the HubSpot social inbox for that channel — not from the contact record for a sequencer-initiated prospecting thread.

OutboundSync social timeline/app events capture sequencer activity (sends, replies, connection requests, and more) with campaign and lead-category metadata. They power workflow triggers the same way email timeline events do, but there is no reply UI on the contact record for these events.

Reps must send social follow-ups in one of two places:

In the sales engagement platform — for example, HeyReach’s Unibox. Outbound manual messages sync back to HubSpot when the platform sends a Message Sent (or equivalent) webhook. See the HeyReach webhook guide.
In the native social platform — when the rep works directly in the social selling platform rather than through the SEP UI.

Workflow routing from social replies still works via Routing replies with a workflow (for example, on Social Message Reply triggers), but the send happens outside HubSpot.

Which platforms sync manual outbound replies

This table covers email manual sends from the SEP only. Social manual sends follow the paths in Social replies above.

If the rep sends from the SEP and the platform does not webhook that send, HubSpot will not show it. Teams on platforms without manual-send webhooks should default to the HubSpot email-activity path, a reply relay when Destinations is enabled on Smartlead or EmailBison, or the manual CC pattern.

Coverage confirmed today — check your platform’s integration page or confirm during onboarding if yours is not listed.

Platform	Manual outbound replies sync?	Notes
Smartlead	Yes	Enable Manual Reply Sent — webhook guide, blog post
EmailBison	Yes	Manual sends — EmailBison integration
HeyReach	Yes (social)	Message Sent webhook — HeyReach webhook guide
Instantly	No	Inbound replies sync; manual Unibox outbound replies do not webhook back. For secondary-address replies, work in Instantly Unibox — Diagnosing missing Instantly replies, Choosing a path
Other SEPs	Varies	See Engagement integrations

Clay’s native email sequencer routes through the Smartlead source, so Smartlead rules apply there too.

Choosing a path

How to choose where the rep sends the follow-up — separate from workflow routing in HubSpot.

Pick a reply path based on where the rep should send from, not just where activity is logged. The usual tension is primary-inbox convenience versus campaign-mailbox deliverability — a reply relay is how Smartlead and EmailBison teams get both.

Prefer a reply relay on Smartlead or EmailBison

If Destinations is enabled on the connection, start with a reply relay. It is the path that keeps reps in their place of work without giving up the sequencer’s deliverability edge:

Place of work — After the handoff, the prospect’s Reply-All lands in the rep’s primary inbox (and typically in HubSpot via the connected inbox). Reps do not have to live in a pool of sequencer mailboxes for every follow-up.
Deliverability edge — The automated loop-in still sends from the sequencer mailbox, so the first handoff keeps campaign-domain identity instead of jumping straight to the rep’s company address.
SEP inbox management stays intact — Warmup, rotation, and Unibox operations continue in Smartlead or EmailBison. The relay does not replace how you run sending infrastructure.
CRM sync stays immediate — OutboundSync still writes the prospect reply to HubSpot right away; the delayed CC handoff is additive, not a substitute for sync.

Optional category/tag allowlists can limit which leads get the handoff. Instantly and other SEPs are not supported for reply relays yet — use the paths below.

Do not connect secondary sequencer inboxes to HubSpot just to fake this outcome — see Connecting secondary sequencer inboxes to HubSpot.

HubSpot-first without a reply relay

When Destinations is off, or you are on Instantly or another unsupported SEP, reply from the native email activity on the contact record in HubSpot. The send goes from the rep’s primary HubSpot-connected inbox. HubSpot technically starts a new thread, but subject and recent context carry over. See HubSpot’s guide on sending and replying to one-to-one emails.

This is still the right default for HubSpot-first teams that cannot use a reply relay. You keep place-of-work convenience and CRM context; you do not get the sequencer From on the handoff.

Deliverability-strict / secondary-address continuity

If every follow-up must come from the same secondary sending address the prospect originally engaged with — not only the first handoff — stay in the SEP (or a unified inbox) for ongoing replies. A reply relay is a handoff into the primary inbox; it is not a forever-secondary path.

Preferred paths for ongoing secondary-address sends:

SEP unified inbox — for example, Instantly Unibox. Use the deep link on the synced reply event to jump from HubSpot to the thread in the SEP.
Unified inbox platforms — HotHawk or Masterinbox when consolidating multi-channel reply queues across teams or channels.

Do not default to connecting secondary sequencer inboxes directly to HubSpot — that path is possible but creates logging, maintenance, and thread-continuity problems at scale.

On Instantly, inbound replies sync to HubSpot, but manual Unibox outbound replies do not webhook back — so HubSpot will not reflect those sends unless Instantly captures them. See Diagnosing missing Instantly replies.

Connecting secondary sequencer inboxes to HubSpot (not recommended)

Some teams connect sequencer secondary sending addresses to HubSpot so reps can reply from the campaign mailbox without leaving the CRM.

HubSpot supports this in principle — each user can connect multiple personal inboxes, and reps can choose a From address when composing or replying. OutboundSync still does not recommend it for scaled outbound programs:

Operational overhead — Every connection is a live OAuth or IMAP session. Sequencer mailboxes rotate often (new domains, password resets, provider migrations). Disconnected inboxes stop logging replies until someone re-authenticates. Duplicate Office 365 connections can also hit provider rate limits. RevOps ends up babysitting dozens of fragile connections instead of one primary rep inbox.
Unwanted CRM logging — Connected inboxes give HubSpot access to message metadata. Depending on your contact email logging rules, HubSpot may log mail to contact records — by default, Log all emails (from known contacts) applies to every connected personal inbox (FAQ). Warmup and sequencer noise in those mailboxes can land in HubSpot unless you add safeguards (Log replies only, never-log domains, inbox filters). On the OutboundSync side, see How to exclude warmup emails.
Lost threads and wrong senders — You can set a default From address for new emails, but that default does not apply to replies. Reps pick (or inherit) a From address per message. A connected secondary inbox may appear in the composer, but reps can still switch senders or start a new email from the wrong mailbox. HubSpot notes that unrelated emails can thread together when users repurpose forwarded messages — the same mistake that breaks continuity for prospects.
Not what personal inboxes are for — HubSpot documents personal email as the address unique to your user that you typically use with contacts — not a rotating pool of sequencer mailboxes (connect your personal email).

For deliverability-strict teams that need ongoing secondary-address sends, use the SEP unified inbox paths above. For Smartlead and EmailBison teams that want a one-time campaign-mailbox handoff into the primary inbox, prefer a reply relay instead. Both preserve campaign identity without turning HubSpot into an inbox-management layer.

Workflow routing is not send-address routing

Routing replies with a workflow handles CRM assignment — owners, tasks, lead-category branching — after a reply lands. It does not choose which mailbox the rep sends from. Set up workflows after you decide the send path above.

For background on why this question is harder than it looks, see the GTM Crossroads discussion of where reps are supposed to reply from.