What is intercom actually for? Seems like chat but it does a lot more

Head of Product

Intercom occupies a category that has expanded well beyond live chat, and understanding that distinction matters before evaluating it against simpler tools. The product started as a way to put a chat widget on a website so visitors could ask questions in real time. Over the years it evolved into what the company calls a "customer communications platform," meaning it tries to consolidate the conversations that happen across the entire customer lifecycle — from the first anonymous website visit through onboarding, ongoing support, and renewal. That scope is what surprises most new evaluators. At its core, Intercom works by creating a unified thread for every contact. When someone visits your site, Intercom can identify them (anonymously at first, then by email once they sign up), and that record carries forward. The chat widget is the front door, but behind it sits a full help desk with a shared inbox where support agents triage, assign, and respond to conversations. Conversations can come in through live chat, email, or in some configurations social channels, and they all land in the same place. Agents can leave internal notes, tag conversations, set statuses, and collaborate without the customer seeing any of it. Layered on top is an automation layer called workflows, where teams build logic that routes incoming messages, sends proactive outbound messages based on user behavior, and triggers replies without human involvement. If a user has been on the pricing page three times in a week, for example, a rule can fire a targeted message. That proactive, behavior-triggered messaging is what separates Intercom from a straightforward ticketing tool and moves it closer to a lifecycle marketing system. The product also includes a self-service help center where you publish articles that the chatbot can surface automatically before escalating to a human agent. Intercom tends to fit well for SaaS companies and digital businesses where customers interact primarily through a web app or mobile product, and where support volume is high enough to justify the overhead of a dedicated inbox environment but not so transactional that a basic email queue would suffice. Teams that want to blend support with proactive outreach — think in-app tooltips, onboarding checklists, and targeted banners alongside live chat — tend to get the most from it. It fits less naturally for companies with primarily phone-based support, complex ticketing workflows with deep SLA requirements, or field service operations where the interaction model is fundamentally different. The honest caveat is that pricing scales with the number of contacts and seats, and the bill can grow quickly as usage expands. Many features that feel important — advanced automation, AI-powered responses, certain integrations — sit on higher pricing tiers, so the cost of the version you actually want to run is often higher than the entry price suggests. There is also meaningful configuration work involved in getting automated workflows to behave correctly, particularly if you want the AI bot to deflect a meaningful percentage of inbound volume. If you're evaluating Intercom, spend time in a trial mapping your actual conversation volume and sources before committing, then test which features are available on which tier against your specific requirements.