Integration · Customer Service

Give Agentforce the Help Scout conversation context behind every customer

Help Scout is the customer support platform that product-led and SMB teams use for shared inbox, in-app messaging, and knowledge base — built for simplicity and collaboration without the overhead of an enterprise service platform. Salesforce holds the commercial record for the same customers: their account status, deal history, and contract details. When a customer writes into Help Scout, an agent responding in that context has limited access to what Salesforce knows about them. When Emerge Digital connects both to Agentforce, a response agent can read the customer's Salesforce account context before replying in Help Scout, escalate high-value accounts to a different resolution path, and ensure that service history from Help Scout is visible in the Salesforce relationship view.

All integrations

What this unlocks

Salesforce account context available in Help Scout conversations: before a support agent replies to a Help Scout conversation, an Agentforce agent can surface the customer's Salesforce account tier, active contracts, and open opportunities — so high-value accounts get a different response path than trial users.
Help Scout conversation history readable by Agentforce agents: when a customer reaches a Salesforce-based touchpoint — a renewal call, an upsell conversation — the agent can read their Help Scout support history to understand what has recently frustrated or pleased them.
Escalation routing based on CRM context: an Agentforce agent can identify when a Help Scout conversation belongs to a strategic account and route it to a dedicated support track or the named account rep rather than the general queue.
Service history synced to Salesforce: key Help Scout conversations — complaints, praise, churn signals — can be logged to the Salesforce account record so the commercial team sees the full relationship picture rather than only the revenue side.

In the customer journey

Strategic account gets a different path

A customer submits a support request in Help Scout. An Agentforce agent checks the Salesforce account — enterprise tier, renewal due in 30 days — and routes the conversation to the dedicated enterprise support track rather than the general queue, flagging the renewal timing to the account rep simultaneously.

Renewal call grounded in support history

A CSM is preparing for a renewal call. The Agentforce agent reads the customer's Help Scout conversation history over the past quarter — the issues they raised, how quickly they were resolved, any recurring friction — and prepares a brief that acknowledges what the customer has experienced rather than opening the call without that context.

Churn signal logged to Salesforce

A customer writes into Help Scout expressing frustration with a recurring issue and mentioning they are evaluating alternatives. The Agentforce agent tags the conversation, logs a churn-risk note to the Salesforce account, and alerts the CSM — so the commercial team is informed before the next renewal conversation rather than after a surprise non-renewal.

Why not Help Scout's Salesforce integration?

Help Scout has a Salesforce integration that can surface CRM data within Help Scout conversations and sync conversation records to Salesforce. This is useful for giving support agents CRM context within Help Scout's interface. What it does not provide is Help Scout conversation data queryable by an Agentforce agent in real time during a Salesforce-based interaction — a renewal conversation, an upsell call, or an escalation handled in Service Cloud. Emerge Digital builds the retrieval layer that makes Help Scout's conversation history and context available to agents operating in Salesforce rather than only in Help Scout.

Help Scout's Agentforce integration value sits in the Engage and Optimize stages — where the support history that Help Scout captures should be visible to the commercial team during sales and success conversations, and where the commercial context in Salesforce should shape how support agents respond to high-value customers. Grounding agents in both systems means the service-to-commercial boundary becomes permeable rather than a hard wall that resets the relationship every time a customer crosses it.

How Emerge integrates Help Scout

Emerge Digital connects Help Scout to Salesforce Agentforce as a consulting engagement. We map which Help Scout conversation data agents need to read — ticket history, conversation tags, and key interactions — configure the Salesforce account context retrieval that enriches Help Scout responses, define the routing rules that differentiate account tiers, and set up the service-to-CRM logging that keeps strategic conversation history visible to the commercial team. The integration is designed around how your support and success teams actually divide responsibility.

How we structure an engagement

Related integrations

FAQ

How is this different from the Zendesk + Agentforce integration?

The use case is very similar — surfacing CRM context in service conversations and keeping service history visible in Salesforce. Help Scout is typically the support platform for smaller and product-led teams that value simplicity; Zendesk is more common in larger support organisations with complex routing, SLA management, and deep reporting needs. Emerge connects whichever platform your support team uses.

Can the agent reply to Help Scout conversations directly?

Yes, when your workflow calls for it. An Agentforce agent can draft or send replies in Help Scout, subject to the permissions you configure. Most teams start with the agent surfacing CRM context and routing recommendations, with the actual reply authored by a human; automation of the reply step is added where quality and volume justify it.

Can the agent access Help Scout's knowledge base as a data source?

Yes. Help Scout Docs — the knowledge base — is a useful retrieval source for Agentforce agents that need to ground responses in published guidance. Emerge can configure Help Scout Docs as a retrieval source alongside conversation history.

How long does a Help Scout + Agentforce integration take?

A focused engagement typically runs three to five weeks: mapping which Help Scout data types agents need, configuring the account context retrieval and tier-based routing, setting up service-to-CRM logging, and testing support and renewal conversation workflows.

Ground your agents in Help Scout.

Tell us what your agents need to read and write in Help Scout, and we'll design the integration and the governance around it.

Talk to the practice

Prefer email? Write to the practice instead.