How to connect Intercom conversations to Linear issues
Linear has a native Intercom integration, and it does let a teammate link a conversation to the issue tracking the fix. Once it's connected, that issue's identifier, status, and assignee show up right in the Intercom sidebar, so a support agent can glance at a linked conversation and see roughly where engineering stands, without opening Slack to ask. Install it from Linear's settings, and any teammate working a conversation gets that panel for free.
What it doesn't do is push anything back to the agent when the status actually changes. The sidebar shows the current state if someone opens the conversation and looks, but nothing pings support when an issue moves from Backlog to In Progress, or when an engineer leaves a comment explaining a delay. By default, Linear only writes back to Intercom automatically at two terminal states, completed or canceled. Everything in between is visible on request, not delivered.
What the integration actually does
Linear's own Intercom integration docs describe a two-way link, and it's worth knowing exactly what that covers before you rely on it:
- Link in either direction. A teammate can create or link a Linear issue from inside an Intercom conversation, and the reverse works too. As the docs put it, "You can also link multiple Linear issues to a single conversation in Intercom," so a conversation that touches two separate bugs can carry both links instead of forcing a one-issue-per-ticket model.
- Many conversations, one issue. The docs also confirm "you can link multiple Intercom conversations to a single Linear issue," so five customers hitting the same bug can all attach to one tracked fix instead of spawning five.
- Status and assignee in the sidebar. Linked issues show their identifier, status, and assignee directly in Intercom, next to the conversation.
- Reopening at terminal states, by default. "When a linked issue is completed or canceled, Linear posts an internal note to the Intercom conversation and reopens it by default." You can configure this separately for completed issues, canceled issues, and new comments, but out of the box it only fires at the end.
- Internal notes sync one way. Notes written in Intercom don't sync to the Linear issue. Anything a support agent adds as color for the engineer stays on the Intercom side unless someone copies it over by hand.
- Business and Enterprise only. Linear's pricing page lists Zendesk and Intercom integrations as a Business-plan feature. Teams on Free or Basic don't have this option at all.
Setup is short. Turn it on from Settings, then Features, then Integrations, then Intercom inside Linear, and it appears as a panel in Intercom's conversation sidebar. Every teammate who wants to see or create links needs a seat on the connected Linear workspace, since Linear's docs note that only Linear users can view linked issues in Linear itself.
“we need SSO before rollout”
“any update on single sign-on?”
“SSO came up twice on this call”
Linear issue, quotes attached
insight report in NotionThe stale rollup bug at Fernhill
Fernhill builds embedded analytics dashboards that e-commerce brands drop into their own admin panels, and support runs through Intercom while engineering ships out of Linear, connected with the native integration above.
Marisol Kearney, Palmwood Goods (Intercom conversation #2214): "Our revenue-by-SKU chart has been showing last week's numbers as 'today' since Tuesday. We make pricing calls off this dashboard every morning."
Lucas Byrne, who runs support at Fernhill, reproduces the issue, confirms it's a caching bug on the aggregation job, and links the conversation to a new Linear issue, ENG-514: Stale cache key on daily revenue rollup. The sidebar now shows ENG-514 · Backlog · Unassigned right next to the conversation.
Marisol, four days later: "Any update on the dashboard fix? This is now affecting last week's numbers too."
Lucas opens the conversation. The sidebar still just says ENG-514, now In Progress, assigned to an engineer named Kwame Boykin. That's genuinely more than Lucas had before the integration existed, he doesn't have to ask in Slack to know someone picked it up. But it doesn't tell him when Kwame expects to ship, whether the fix also covers the SKU chart Marisol just mentioned, or that Kwame actually left a comment on the issue an hour ago saying the rollup job needed a schema change first. None of that reaches Intercom. Lucas has to open Linear directly to read it, then paraphrase it back to Marisol himself.
What the status badge leaves out
The link itself is solid. It breaks down as a way to actually surface engineering progress for three specific reasons:
- Nothing pushes a status change to anyone. The sidebar is pull, not push. A support agent sees the current state only at the moment they happen to open that conversation, so "support can see progress without pinging engineers" is only true if support keeps checking on its own initiative.
- The narrative stays in Linear. A status badge says
In Progress; it doesn't say why, or what the plan is, or whether a comment thread just answered the exact question the customer asked. That context exists, but it's a separate click into a tool support doesn't otherwise use. - Notes don't travel from Intercom to Linear either. The one-directional sync means the engineer working
ENG-514never automatically sees that Marisol mentioned a second symptom four days after the issue was filed, unless Lucas goes and adds it as a comment himself.
When ENG-514 is marked Done, the automation fires on its own. An internal note posts to the conversation and it reopens, and Lucas replies to confirm the fix. That part worked exactly as documented. Everything in the two weeks before that, the actual progress Marisol was asking about, only reached her because Lucas kept manually re-checking a status badge and translating it into an update.
Worth saying plainly here: we build Modem, so take what follows as an interested pitch, not neutral advice. What it would have changed for Lucas is specific, not abstract. Modem reads Intercom conversations as they come in and links them to the Linear issue tracking the fix (Intercom integration), and because it also has access to the Linear side (Linear integration), Kwame's comment about the schema change would have reached the same topic support was already watching the moment he wrote it, no separate trip into Linear required. A status change or a new assignee lands the same way, as an update where support already looks rather than a badge someone has to remember to recheck. The Zendesk half of this same gap is covered in our guide on connecting Zendesk tickets to Linear issues, and whether Linear needs a support tool at all is the question behind does Linear work without Zendesk or Intercom.
If the native integration already covers you
For a small team, the badge is probably enough. Turn on the Intercom integration, put support on Linear-connected seats, and add one habit. Whoever links a conversation checks back on it every couple of days rather than waiting for the customer to ask. That alone closes most of the gap between "the link exists" and "support actually knows what's going on," at least until the volume of linked conversations outgrows what one person can keep checking by hand.
