n-Help Scout's Salesforce Integration Pulls Data In. It Doesn't Push Anything Back Out.
Help Scout's native Salesforce integration shows Salesforce contact and account data right in the conversation sidebar, which saves agents a tab switch. The catch is direction: data flows from Salesforce into Help Scout, not the other way, and turning it on requires a higher Help Scout plan plus a paid Salesforce API add-on.
How the native integration works
Two apps, two directions, one of them active. Help Scout's Salesforce app pulls Salesforce fields, standard and custom, into the conversation sidebar. A separate Salesforce-side app can show Help Scout data inside Salesforce through a Visualforce component, but it's a much thinner view than the actual conversation.
It's gated behind cost on both sides. The integration is only available on Help Scout's Plus and Pro plans, and Salesforce requires its own paid API add-on before the connection can pull data at all. For a smaller team on a lower tier of either product, the integration simply isn't reachable yet.
What actually syncs is read-only, into Help Scout. Account details, contact fields, and whatever custom fields you've mapped show up for an agent to see. None of it is a Help Scout conversation turning into a Salesforce activity automatically.
Where the one-way sync leaves sales in the dark
A sales rep working a Salesforce account has no native way to see that the same customer opened three support tickets last week, unless someone manually logs a note. Account health, churn risk, and renewal conversations all suffer from that blind spot, because the integration was built to help agents, not to help sales see the support side at all.
And the plan-and-add-on gating means plenty of businesses running both tools never get the native connection working in the first place, even the one-directional version.
What we've built on top of Help Scout and Salesforce
A subscription business ran Help Scout for support and Salesforce for its account management team, with renewal conversations happening with zero visibility into recent support history, because the native integration wasn't worth the upgrade cost for a team that size. Account managers found out about trouble accounts the hard way, usually at the renewal call itself.
We built a direct sync off Help Scout's conversation and tag webhooks that logs a Salesforce activity every time a ticket closes, tagged with the conversation's resolution and any escalation flags. No Help Scout plan upgrade, no Salesforce API add-on. Account managers now see support activity sitting right in the Salesforce timeline before a renewal call, not after.
Paying to not see your support history in Salesforce, or not paying and seeing none of it?
Tell us what your sales or account team actually needs to see from support, ticket volume, resolution notes, an escalation flag, and we'll build the sync directly against each system's own API. Help Scout and Salesforce happen to be the two tools here; we do this same kind of connecting work for any pair of systems that aren't talking to each other.
Let's talk