Running Intercom?

Intercom Messenger or workflows acting up? We unstick it.

An Intercom install can look fine in the dashboard and still be invisible on half your pages, routing conversations to a team that left, or firing a bot that answers the wrong question. We trace it from the Messenger snippet through Workflows, Fin, and the webhook handlers until the actual breakage is on screen.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

intercom-messenger.log

still broken

What it is

Intercom at a glance

Intercom is a customer messaging and support platform built around a JavaScript Messenger that sits on your product and marketing pages, plus an admin workspace where human agents and AI agents handle the conversations. It covers live chat, email follow ups, in-product tours, help center articles, and an AI resolution bot called Fin.

The company launched in 2011 and has steadily moved from a simple chat widget into a full support suite with ticketing, SLAs, workflows and reporting. The API surface is broad, covering contacts, conversations, data events, custom attributes and webhooks, and most larger deployments end up with a mix of client side Messenger code and server side sync jobs talking to the REST API.

Type
Customer messaging and AI support platform
First released
2011
License
Proprietary SaaS, seat and resolution based pricing
Maintained by
Intercom, Inc.
Typically used for
Live chat, help center, in-app tours, AI agent resolution, support ticketing

The honest version

Intercom pros and cons

No technology is all upside. This is where Intercom earns its place and where it tends to cause trouble.

Where Intercom is strong

  • The Messenger is still the benchmarkQuick to drop in, mobile friendly, and able to carry article suggestions, bots and live humans without a jarring handover between them.
  • Fin ships useful AI out of the boxPointed at your help center and past conversations, Fin resolves a measurable share of inbound without the long prompt engineering project some rivals demand.
  • Workflows are genuinely visualRouting, business hours, assignments and macros can be built by support ops without filing a ticket with engineering for every change.
  • Strong CRM-style contact modelCustom attributes, events, companies and tags make it easy to segment conversations and target in-app messages at the right accounts.
  • Decent reporting and SLA toolingFirst response time, resolution time and conversation ratings are built in rather than bolted on, which matters when support leadership is being measured on those numbers.

Where Intercom bites

  • Pricing is unpredictable at scaleSeats, Fin resolutions, people-reached pricing and add-ons combine into a bill that can jump significantly between quarters as usage grows.
  • Identity verification is easy to misconfigureThe user_hash HMAC flow is strict, and a mismatch silently degrades the Messenger to anonymous mode in production while still looking normal in staging.
  • Webhooks need your own reliability layerIntercom retries three times then gives up. If your endpoint is flaky you will lose events, and there is no replay button for most webhook topics.
  • Custom attribute drift is realOnce an attribute is created with the wrong type or name, renaming or re-typing it is painful, and old values stay behind in exports and reports.
  • Fin can resolve the wrong thingWithout careful content pruning and guardrails, the AI agent happily answers from stale help articles and closes tickets that should have reached a human.
  • Data export is clunkyBulk export jobs are rate limited, the conversation export format is awkward, and migrating off Intercom is a project rather than a weekend.

Sound familiar?

Common Intercom problems we fix

The Intercom problems that bring people to us, and what you have once each one is fixed.

identity_verification_failed

The Messenger silently falls back to anonymous

The server sends the user hash, the client boots with a different user_id, and the Messenger appears but stops recognizing the logged-in customer, so the conversation history vanishes.

Identity verified, history restored

WebhookDeliveryFailed after 3 retries

Webhook events are being dropped

A slow endpoint, a 5xx during a deploy, or a signature check that rejects half the traffic. Intercom retries a few times and then the event is gone for good.

Deliveries acknowledged and queued

Rate limit reached 83/83

Sync jobs trip the API rate limit

A nightly contact backfill or a reporting script hammering the search endpoints, starving the live Messenger traffic of API capacity during business hours.

Traffic paced, limits respected

Workflow paused: no admin in team

Conversations stall in a workflow

A routing step points at a team with nobody available, a condition never evaluates true, or office hours blocks the path with no fallback branch.

Routes that always reach somebody

custom_attribute type mismatch

Custom attributes are wrong across the data model

An attribute created as a string holding what should be a boolean, duplicate attributes from different integrations, and reports that quietly exclude half the accounts.

Attributes rationalized and typed

Fin resolved 12% (target 40%)

Fin is under-resolving or hallucinating

Help center content that is stale, contradictory, or pitched at the wrong audience, and no guardrails on which topics Fin is allowed to handle end to end.

Fin tuned against real content

contacts.search nested OR clauses

Contact segments will not save

A segment built in the UI that generates a search payload past the API's nesting limit, usually after years of accumulated filter logic nobody has pruned.

Segments rebuilt within limits

shutdown called but never booted

The Messenger leaks between pages in a SPA

A single page app that forgets to shutdown and reboot on route changes, leaving the previous user's conversation visible to the next one.

Lifecycle hooks in the router

What we do

Intercom help, from install to tuning

Hire us for one broken workflow, or let us run the whole Intercom surface.

Rescue
Messenger invisible, Fin answering wrong, or webhooks dropping on the floor. We stabilize the install and then report back on what caused it.
Identity and Messenger install
User hash verification, SPA lifecycle handling, and a Messenger that loads correctly for logged-in and anonymous visitors alike.
Workflows and routing
Business hours, teams, SLAs and AI handover rebuilt so conversations reach the right human within the time your SLA promises.
Fin tuning
Content audit, topic guardrails, and the metrics to prove Fin is actually resolving the tickets it closes.
Migrations
Moving onto Intercom from Zendesk, HubSpot or legacy chat without losing conversation history or customer profiles.
Managed Tech
A standing team that watches webhooks, seat usage, Fin accuracy and SLA numbers so surprises show up in a weekly report rather than a Monday fire.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Intercom alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Intercom questions

Something else? Call+1 737 727 7327

Why does our Intercom Messenger not recognize logged-in users?

Nine times out of ten the user_hash HMAC is being computed against a different user_id than the one passed to the client, or the secret rotated and one side of the stack kept the old value. The Messenger does not throw a hard error for this, it quietly treats the visitor as anonymous, so the symptom is a conversation history that vanishes rather than a log line.

Can you migrate us from Zendesk or HubSpot to Intercom?

Yes. We export contacts, companies, tickets and macros from the source platform, map them to Intercom's contact and conversation model, and run the import with the Messenger still disabled on production so the old tool keeps working until cutover. Conversation attachments and internal notes need a little extra care because the field shapes differ.

How do we stop Fin from giving wrong answers?

Start with the source content. Fin can only resolve correctly if the help center and past conversations it learns from are current and consistent. After that, add explicit topic guardrails, require a human handover for anything about billing or account security, and watch the resolution quality scores rather than just the resolution rate.

Why are our Intercom webhooks missing events?

Intercom retries three times and then abandons the delivery. If your endpoint 502s during a deploy or times out under load, those events are gone. The fix is a thin queue in front of your handler that acknowledges fast and processes async, plus alerting on the Intercom delivery failure report.

How do we reduce our Intercom bill?

Usually by auditing seats, pruning unused Fin topics, and cleaning up people-reached counts that have ballooned from stale contacts. We go through the invoice line by line with you and identify what each line is actually buying before renewal talks start.

How much does Intercom help cost?

The estimate is free. Tell us which part of the Messenger, workflow or API is misbehaving and we send back a price before any work starts.

Free estimate

Intercom giving you trouble?

Tell us what the Messenger or the workflows are doing wrong and we come back with a fixed-price plan.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.