HubSpot Zendesk and Intercom integration.
Support signal reaching the account team. Keeping Zendesk or Intercom is a perfectly good decision. What is not defensible is an account manager walking into a renewal without knowing the customer raised eleven tickets last month.
The churn signal was in the help desk.
Support volume, sentiment and escalation history are the best leading indicators of churn most companies have, and they sit in a system the revenue team does not open. The data exists. It is just in the wrong room.
Eleven tickets. One renewal meeting.
Support — the unread signalWhat crosses the boundary, and what does not.
Aggregate, do not flood
Sales does not need every ticket on the timeline. Ticket count, open escalations, time since last issue and sentiment trend on the company record is the useful shape.
Company matching that holds
Support identifies people by email, the CRM by company. Multiple domains, personal addresses and resellers all break naive matching, so the identity rule is explicit.
Escalation reaches the owner
A critical ticket from a strategic account creates a task for the account owner rather than waiting to be noticed in a weekly report.
Health as a property, not a feeling
A composite score from support volume, severity, response time and CSAT, stored on the company so it can drive workflows and appear in a renewal pipeline.
Support sees the commercial context
Contract tier, renewal date and account owner pushed into the support tool, so an agent knows whether they are talking to a strategic account before they answer.
One system owns the ticket
Tickets are not mirrored. The help desk owns them; HubSpot holds the summary. Mirroring guarantees two versions of a conversation.
Built to a contract, not to a connector.
Draw the boundary
Which system owns which field, in writing, before a line of code. Most broken integrations are two systems both believing they are the source of truth.
Model the join
The key that matches a record on one side to a record on the other, and the rule for what happens when it does not match — because it will not match.
Build and instrument
Sync built with retries, idempotency and a dead letter path, plus logging you can read without opening a console.
Reconcile
Counts compared on both sides on a schedule, with a report that names the drift rather than a green tick that hides it.
Hand over
A runbook covering the three failures that actually happen, so the next person does not have to reverse-engineer the design from the logs.
Every ticket lands on the timeline.
The default integration pushes every ticket onto the contact record. Within a month the timeline is unreadable and the account manager has stopped looking at it, which is the exact opposite of the intent. Aggregate and alert. Do not mirror.
What people ask before they commit.
Should we just move support into HubSpot?
Sometimes. If the support operation is mid-sized and the shared record is the main goal, Service Hub is a strong answer. For high-volume operations with complex routing, keeping the help desk and integrating is usually better.
Will sales see every ticket?
Deliberately not. They see counts, open escalations and health. Detail stays one click away in the help desk, which is where it belongs.
Can we build a churn risk score from this?
Yes, and support data is the most predictive input most companies have. It works best combined with product usage and payment history rather than on its own.
Does this work with Freshdesk or Help Scout?
Yes. Any help desk with a reasonable API fits the same pattern. Zendesk and Intercom are simply the two we are asked about most.
How long does it take?
Two to four weeks. The health score definition takes longer to agree than the integration takes to build.
Where people go from here.
Know before the renewal.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.