Intercom

What Is Intercom?

Intercom is a customer-messaging and support platform best known for the chat "Messenger" bubble you see in the bottom corner of many SaaS and web-app websites. In one sentence: Intercom lets companies talk to their customers, through live chat, AI-powered bots, proactive messages, product tours, and a help center, directly inside their website or app. Founded in 2011 and headquartered in San Francisco and Dublin, Intercom has positioned itself in recent years around AI-first customer service, including its "Fin" AI agent, while continuing to serve as a combined live-chat, help-desk, and customer-engagement tool.

For technology detection, Intercom is a gift: it is one of the most consistently identifiable front-end tools on the web. Because the Messenger is a JavaScript widget that must load in the browser, an Intercom-powered site reliably loads scripts from Intercom's CDN, exposes a global Intercom object, sets recognizable cookies, and injects a distinctive iframe into the DOM. Anyone inspecting the page can confirm Intercom in seconds, and can usually extract the customer's workspace identifier (the app_id) as well.

It is worth being clear about what Intercom is not. It is not a browser extension or a self-hosted package; it is a hosted SaaS product. When a website "uses Intercom," it has embedded Intercom's Messenger snippet and connected it to an Intercom workspace identified by a short app_id. The conversations, contact data, and automation live in Intercom's cloud.

Intercom occupies an interesting position in the market. It started as a tool for product companies to message their users in-app, then expanded outward into customer support, marketing, and onboarding, which is why the same Messenger bubble can be doing very different jobs on two different sites. On a developer-tools homepage it might be a pre-sales chat staffed by a solutions engineer; on a logged-in SaaS dashboard it might be the primary support channel plus a feed of product announcements. For technology detection this breadth does not matter much, the footprint is the same, but it does mean that finding Intercom on a site tells you the company has chosen an integrated, product-led approach to talking with its users rather than a traditional ticket-based help desk.

How Intercom Works

Intercom centers on a single, embeddable Messenger plus a backend that unifies conversations and customer data.

The on-page flow works like this:

• A site embeds the Intercom JavaScript snippet, which loads the widget code from Intercom's CDN and is configured with an app_id (the workspace identifier) and optional user attributes via a global intercomSettings object.
• The script boots window.Intercom, a programmable API you can call to show/hide the Messenger, send events, or update user data (for example, Intercom('show') or Intercom('update', {...})).
• Intercom injects the Messenger UI into the page inside an iframe (commonly identified by the id intercom-frame and container elements in the intercom- namespace), which isolates its styles and scripts from the host site.
• Messages flow into Intercom's shared inbox, where support and sales teams reply. Conversations can be triaged, assigned, and automated.

On the backend, Intercom maintains profiles for leads (anonymous or partially known visitors) and users (identified customers), enriched with custom attributes and event history. On top of that sit bots and AI (including the Fin AI agent and rule-based "Custom Bots"), proactive outbound messages (in-app messages, banners, posts, and email), product tours, and a Help Center knowledge base. The same identity that the Messenger snippet establishes ties all of these together, which is why finding the app_id effectively identifies the workspace.

There is an important distinction between anonymous and identified installs that affects what you will see. On a public marketing site, the Messenger usually boots in anonymous mode: it knows only what the cookie tells it. Inside a logged-in application, developers typically call Intercom('boot', { app_id, user_id, email, ... }) or pass a signed user_hash so Intercom can securely tie the conversation to a known account. When you inspect a logged-in app you may therefore see richer intercomSettings (including user attributes), whereas on a brochure site you will mostly see just the app_id. Either way, the app_id is the constant that identifies the workspace.

Real-time messaging is delivered over WebSockets to Intercom's "nexus" servers, which is why an active Messenger keeps a persistent connection open. That connection is itself a corroborating detection signal: a long-lived WebSocket to an intercom.io host is a strong indicator that the Messenger is live rather than merely embedded.

How to Tell if a Website Uses Intercom

Intercom is straightforward to detect because it touches scripts, globals, cookies, and the DOM simultaneously.

Script domains (the strongest tell)

Watch the network for requests to Intercom's infrastructure:

• widget.intercom.io — the Messenger widget bootstrap/config endpoint.
• js.intercomcdn.com — the CDN that serves the Messenger's JavaScript and assets.
• api-iam.intercom.io / *.intercom.io — API endpoints the widget talks to.
• WebSocket connections to nexus-websocket-*.intercom.io for real-time messaging.

The app_id is typically visible in the bootstrap request or in the inline snippet's intercomSettings.

JavaScript globals

In the DevTools Console, check for:

• window.Intercom — the programmable Messenger API. If it is a function, Intercom is active.
• window.intercomSettings — the configuration object, which usually contains the app_id (e.g. { app_id: "abcd1234" }).

Cookies

Intercom sets cookies prefixed with intercom-, such as intercom-id-<app_id>, intercom-session-<app_id>, and intercom-device-id-<app_id>. The app_id is embedded right in the cookie name, which both confirms Intercom and reveals the workspace.

Widget DOM

Inspect the page for the Messenger iframe and containers: an iframe with id intercom-frame, plus elements in the intercom-lightweight-app / intercom- class namespace that render the launcher bubble and the chat window.

Tools and method

1. View Source. Search the HTML for intercom, intercomSettings, or widget.intercom.io; the snippet and app_id are often inline.
2. DevTools Network tab. Reload and filter for intercom; look for widget.intercom.io and js.intercomcdn.com and read the app_id.
3. DevTools Console. Enter window.intercomSettings to print the config (including app_id), or typeof window.Intercom to confirm the API. Check Application > Cookies for intercom-id-*.
4. Wappalyzer and similar extensions will label the site "Intercom" automatically.

For a guided approach to spotting chat tools, see how to detect chat and live chat tools on a website. To understand why this matters for sales, read what technographics are and how to use tech-stack data to qualify leads, and for the general method, how to find out what technology a website uses.

Key Features

• Messenger. A customizable in-app/website chat widget for live conversations and self-serve help.
• AI and bots. The Fin AI agent and Custom Bots to deflect, qualify, and route conversations automatically.
• Shared inbox. Team triage, assignment, macros, and SLAs for handling conversations at scale.
• Proactive messaging. In-app messages, banners, tooltips, product tours, and outbound email to engage users at the right moment.
• Help Center. A hosted knowledge base that integrates with the Messenger for self-service.
• People and event data. Lead/user profiles with custom attributes and event tracking for segmentation and targeting.
• Series and orchestration. Visual campaign builders let teams coordinate multi-step sequences across the Messenger, email, and push, branching on how each contact responds.
• Integrations and apps. A large app store connects Intercom to CRMs, help-desk tools, Slack, and data platforms, and the SDKs extend the Messenger into iOS and Android apps as well as the web.

Pros and Cons

Pros

• Polished, highly customizable Messenger with a strong product-led-growth feature set.
• Tight integration of chat, bots, product tours, and outbound messaging in one tool.
• Strong AI/automation story for deflecting repetitive support questions.
• Rich developer API and large integration marketplace.

Cons

• Pricing is widely considered expensive and can scale unpredictably with seats, contacts, and resolutions.
• The breadth of features adds configuration complexity.
• Adding the Messenger script has some performance cost on page load.
• Heavy reliance on Intercom for support, marketing, and product onboarding creates lock-in.

Intercom vs Alternatives

Intercom competes with both live-chat tools and broader help-desk/conversational platforms. The table compares common alternatives.

Platform	Primary focus	Detection tell	Best for
Intercom	Messenger + AI support + engagement	widget.intercom.io, window.Intercom, intercom-frame	SaaS/product-led teams
Drift	Conversational marketing/sales chat	js.driftt.com, window.drift	B2B revenue/marketing chat
Zendesk	Help-desk + ticketing + chat	static.zdassets.com, zE widget	Support-led organizations
LiveChat	Focused live chat	cdn.livechatinc.com	SMB live chat
Crisp	Affordable multichannel chat	client.crisp.chat	Startups on a budget

If your interest is sales-oriented chat specifically, compare Intercom with our profile of Drift, which leans harder into conversational marketing.

Use Cases

• Customer support. Live chat plus AI deflection and a help center to resolve issues quickly.
• Product-led onboarding. Product tours, tooltips, and in-app messages that guide new users to activation.
• Sales and lead qualification. Routing high-intent website visitors to sales via the Messenger and bots.
• Competitive and lead research. Detecting Intercom (and extracting the app_id) is a strong technographic signal that a company is product-led and invests in customer messaging, valuable input for prospecting and competitive analysis. Combined with other detected tools, it helps you infer team structure: a site running Intercom plus a CRM and an analytics suite is likely a funded SaaS company with a real customer-success function.
• Mobile in-app messaging. Through its iOS and Android SDKs, Intercom carries the same Messenger, bots, and help center into native apps, so the detection story on the web has a direct mobile counterpart.

Frequently Asked Questions

What is the fastest way to confirm a site uses Intercom?

Open DevTools and type window.intercomSettings in the Console. If it returns an object with an app_id, Intercom is active. You can also look in the Network tab for requests to widget.intercom.io or js.intercomcdn.com, or spot the intercom-frame iframe in the DOM. If you prefer not to open DevTools at all, a fingerprinting extension such as Wappalyzer will surface the same conclusion automatically by matching those scripts and cookies.

What is the Intercom app_id and where do I find it?

The app_id is the short identifier for a company's Intercom workspace. It appears in the inline intercomSettings object, in the bootstrap request to widget.intercom.io, and embedded in cookie names like intercom-id-<app_id>. It uniquely identifies which Intercom workspace the site is connected to.

Does Intercom slow down a website?

The Messenger adds JavaScript that loads in the browser, so there is some performance cost, though Intercom loads much of the widget asynchronously to limit the impact. Whether it is noticeable depends on the site's overall performance budget and how the snippet is loaded.

Is Intercom only for support, or also for sales and marketing?

All three. Intercom combines support (live chat, AI agent, help center), product engagement (tours, in-app messages), and sales/marketing (lead routing, proactive outreach). That breadth is a key reason teams choose it, and also why it can get expensive. The same Messenger you detect on a public site may be doing pre-sales qualification, while inside the product it doubles as the primary support channel, one widget, several jobs.

What is the difference between an anonymous and an identified Intercom install?

On public marketing pages the Messenger usually boots anonymously, knowing only what its cookie holds. Inside a logged-in app, developers boot Intercom with a user_id, email, and often a signed user_hash so the conversation is securely tied to a known account. The practical effect for detection is that logged-in apps may expose richer intercomSettings, while public sites typically reveal just the app_id.

Can a website hide that it uses Intercom?

Not easily if it runs the standard Messenger. The widget must load Intercom's scripts in the browser, expose the Intercom global, and inject its iframe, all visible to anyone inspecting the page. An active Messenger also keeps a persistent WebSocket open to an intercom.io host, another hard-to-hide tell. Server-side analysis confirms it even more reliably by checking scripts, globals, and behavior together. Analyze any URL with StackOptic.