Integration guide

Help Scout and HubSpot: CRM Context in the Support Sidebar

A sidebar app that shows the HubSpot record beside the conversation. Read-oriented, quick to install, and it answers the question agents most often get wrong: who is this?

Connector
Native — HubSpot app from the Help Scout apps directory
Sync direction
Primarily HubSpot → Help Scout; conversation activity can flow back
Setup time
15 minutes
Availability
Available across Help Scout plans; HubSpot side works from most tiers
What moves between Help Scout and HubSpot
What Direction Detail
Contact lookup HubSpot → Help Scout Matched by email address. The sidebar shows the HubSpot contact with the properties you would want mid-conversation.
Company context HubSpot → Help Scout The associated company and its properties, which is usually more decision-relevant than the individual contact.
Lifecycle stage HubSpot → Help Scout Whether this is a lead, a trial, a customer or a churned account — the single most useful field to have visible.
Open deals HubSpot → Help Scout Deal name, stage and owner. An agent seeing an open opportunity handles the conversation differently, correctly.
Contact owner HubSpot → Help Scout Tells the agent who internally owns this relationship, which is who to loop in rather than guessing.
Conversation activity Help Scout → HubSpot Support conversations can register on the HubSpot timeline so sales sees that support contact is happening.

Setting it up

  1. Install the HubSpot app from Help Scout's apps directory and authorise it against the HubSpot portal your sales team actually uses.
  2. Choose the properties to display deliberately — lifecycle stage, company, open deal, contact owner. Resist adding more.
  3. Check for duplicate HubSpot contacts on your most common domains before rollout, since duplicates make the sidebar unreliable in exactly the accounts that matter.
  4. Decide whether conversation activity should flow to HubSpot, and if so keep it to a summary-level signal rather than every message.
  5. Brief agents on what the fields mean. Lifecycle stage is meaningless to someone who has never used HubSpot, and an unexplained panel gets ignored.
  6. Agree an escalation convention: when the sidebar shows an open deal, the deal owner gets notified rather than the agent improvising.

Where the integration stops

  • Email matching only. A customer writing from a second address shows nothing, and the agent is back to searching HubSpot manually.
  • Read-oriented. This is a context panel, not a way to update HubSpot from Help Scout. Property changes happen in HubSpot.
  • Sidebar space is finite. Surfacing twenty properties means an agent reads none of them; three or four is the practical limit.
  • No deep conversation sync. Support history does not become a rich record inside HubSpot — expect activity signals rather than full threads.
  • Duplicate HubSpot contacts confuse the panel, since matching returns what it finds and a messy CRM produces a misleading sidebar.

The problem it solves in one sentence

Support agents answer people without knowing whether they are a trial user, a major customer, or a prospect with an open deal — and those should not receive identical replies.

Why the sidebar is the right shape

Help Scout is built around the idea that support should feel like email. A full CRM interface embedded in the conversation view would contradict that, and agents would not read it anyway.

A narrow panel with four facts is something an agent can absorb in the two seconds between opening a conversation and starting to type. That is the window this integration has, and designing for it is why it works.

The field that matters most

Open deal. An agent who can see there is an opportunity in progress, with a named owner, does two things differently: they respond faster, and they tell the deal owner.

The second is the one with commercial consequence. A support conversation during an active sales cycle is information the rep needs, and without the sidebar it is information that never reaches them.

Set the escalation convention explicitly

The sidebar creates awareness; it does not create a process. Agents who notice an open deal will do something inconsistent unless told what to do — loop in the owner, tag the conversation, or nothing at all.

Pick one, make it a habit, and the integration goes from informative to operational. Skip it and you have a nicer-looking inbox.

The duplicate problem

The panel is only as good as the HubSpot data behind it. Duplicate contacts mean the sidebar might match the wrong record and show a lifecycle stage or deal that belongs to a different version of the same person.

Larger accounts tend to have the most duplicates, which means the sidebar is least reliable exactly where accuracy matters most. A deduplication pass before rollout is worth more here than any amount of configuration.

Related

Visit Help Scout →

Frequently asked questions

Can agents update HubSpot from Help Scout?
Not meaningfully — the app is built to display CRM context rather than to act as a HubSpot interface. That is a reasonable design choice, because a support agent mid-conversation should not be changing lifecycle stages or deal properties, and giving them the ability to do so casually tends to produce CRM data that sales does not trust. Where support genuinely needs to record something, the better pattern is a note or a tag in Help Scout, with the significant signals flowing to HubSpot as activity.
What should I put in the sidebar?
Four fields at most, chosen for whether they change the agent's behaviour. Lifecycle stage tells them whether this is a customer or a prospect. Company tells them the account. Open deal tells them there is money in play. Contact owner tells them who to loop in. Everything beyond that — original source, last marketing email, lead score — is interesting to marketing and irrelevant to someone writing a reply in the next ninety seconds. Sidebars fail by being too full far more often than by being too sparse.
Why does the sidebar show nothing for some customers?
Because matching is by email address and the customer is writing from an address HubSpot has never seen — a personal account, an alias, or a colleague of the contact you actually have. This is the same limitation every email-matched sidebar has. The workable response is agent habit rather than configuration: if the panel is empty and the conversation seems commercially significant, search HubSpot on the domain rather than the address. Most of the time the account is there under someone else's name.