Quick signals
What this product actually is
Intercom is built around real-time messaging and AI-first resolution: best for teams where live chat and proactive engagement drive support, not traditional ticketing workflows. Fin AI and product tours add cost quickly.
Pricing behavior (not a price list)
These points describe when users typically pay more, what actions trigger upgrades, and the mechanics of how costs escalate.
Actions that trigger upgrades
- Need multi-team inboxes and round-robin—Advanced $99/seat from Essential $39
- Workflows and automation—Advanced tier
- SLA policies and breach tracking—Expert $139/seat
- SSO, HIPAA, multibrand—Expert tier
- Fin resolution volume exceeds budget—cap available but disables AI when hit
- Proactive Support Plus messages exceed 500/mo—usage-based overage
When costs usually spike
- Fin $0.99/resolution has no per-seat cap by default; 10K resolutions = $9,900/mo
- Proactive Support Plus 500 messages included; Product Tours, Surveys, Posts count
- SMS, WhatsApp, phone usage-based; costs vary by region and volume
- Lite vs Full seats: Advanced/Expert include free Lite seats; verify who needs Full
- Copilot: 10 free suggestions/agent/mo; unlimited = $29/agent add-on
- Resolution definition: customer confirms or doesn't ask more—can undercount complexity
Plans and variants (structural only)
Grouped by type to show structure, not to rank or recommend specific SKUs.
Plans
- Essential - $39/seat/mo - Basic chat and product tours
- Advanced - $99/seat/mo - Automation and reporting depth
- Expert - $139/seat/mo - Full platform and API
- Fin AI - $0.99/resolution - AI chatbot add-on
Costs and limitations
Common limits
- Fin resolutions add up: 1,000/mo = $990; 5,000 = $4,950 on top of seats
- Proactive Support Plus: $99/mo + overage for messages beyond 500
- Essential lacks multi-team inboxes; Advanced $99/seat required for round-robin
- Ticketing workflows less mature than Zendesk/Freshdesk; built for chat, not queues
- SLA policies and breach tracking only on Expert ($139/seat)
- No native e-commerce order lookup; Gorgias wins for Shopify
What breaks first
- Fin resolution cost at scale: 5,000+/mo adds $5K+ to seat costs
- Proactive messaging overage when Tours/Surveys/Posts scale
- Essential → Advanced jump ($39 → $99) for multi-team and automation
- Ticketing and queue workflows feel secondary to chat; queue-centric teams struggle
- Usage-based channels (SMS, WhatsApp) create unpredictable bills
- Expert tier for compliance (SSO, HIPAA); enterprise custom pricing
Decision checklist
Use these checks to validate fit for Intercom before you commit to an architecture or contract.
- Ticket queue vs conversational support model: Is email/chat resolution threaded or formal tickets?
- Per-agent vs per-ticket pricing model: What is your projected ticket volume vs agent count?
- Enterprise depth vs simplicity and adoption: How many integrations and workflow automations do you need?
- General-purpose vs vertical-specific (e-commerce): Does order lookup and refund-in-ticket dominate your support queue?
- Upgrade trigger: Need multi-team inboxes and round-robin—Advanced $99/seat from Essential $39
- What breaks first: Fin resolution cost at scale: 5,000+/mo adds $5K+ to seat costs
Implementation & evaluation notes
These are the practical "gotchas" and questions that usually decide whether Intercom fits your team and workflow.
Implementation gotchas
- Chat-first, unified inbox → Less mature ticket workflows than Zendesk/Freshdesk
- Ticketing workflows less mature than Zendesk/Freshdesk; built for chat, not queues
Questions to ask before you buy
- Which actions or usage metrics trigger an upgrade (e.g., Need multi-team inboxes and round-robin—Advanced $99/seat from Essential $39)?
- Under what usage shape do costs or limits show up first (e.g., Fin $0.99/resolution has no per-seat cap by default; 10K resolutions = $9,900/mo)?
- What breaks first in production (e.g., Fin resolution cost at scale: 5,000+/mo adds $5K+ to seat costs) — and what is the workaround?
- Validate: Ticket queue vs conversational support model: Is email/chat resolution threaded or formal tickets?
- Validate: Per-agent vs per-ticket pricing model: What is your projected ticket volume vs agent count?
Fit assessment
- SaaS product teams that want a single platform for in-product onboarding messages, proactive lifecycle campaigns, and reactive support chat — eliminating the need for separate tools for each function.
- Growth-stage B2B SaaS companies where the support team is small but needs to handle both reactive chat support and proactive customer success outreach from one platform.
- Teams that want to measure support's impact on retention and expansion — Intercom's conversation data and customer lifecycle context make it easier to correlate support quality with revenue outcomes.
- Traditional ticket-queue workflows; Zendesk/Freshdesk better for queue-centric ops
- E-commerce support with order lookup—Gorgias native; Intercom requires integrations
- Email-heavy support; Help Scout's shared inbox and collision detection superior
- Budget-sensitive; Fin resolution costs unpredictable at high volume
- Need mature SLA policies and breach tracking—Expert tier $139/seat
- Collaborative inbox over tickets—Front built for multi-touch conversations
Trade-offs
Every design choice has a cost. Here are the explicit trade-offs:
- Fin pay-per-resolution ($0.99) → Unpredictable cost at high volume vs flat AI add-ons
- Chat-first, unified inbox → Less mature ticket workflows than Zendesk/Freshdesk
- Proactive engagement (tours, surveys) → Proactive Support Plus add-on and message limits
- Essential $39 entry → Multi-team and automation require Advanced $99
- Strong engagement + support combo → Overkill for email-only support teams
Common alternatives people evaluate next
These are common “next shortlists” — same tier, step-down, step-sideways, or step-up — with a quick reason why.
-
Zendesk — step-upZendesk handles higher-volume ticket operations more efficiently once conversation counts scale past what a single inbox can manage. The better choice when structured SLA-driven ticket workflows matter more than proactive in-app messaging.
-
Freshdesk — step-downFreshdesk is the step-down for teams that need multi-channel ticket routing without Intercom's messaging and engagement layer. Handles email, phone, and social from one queue at significantly lower cost per seat.
-
Help Scout — step-downHelp Scout covers the core shared inbox use case at a fraction of Intercom's cost. Best when the team primarily responds to inbound email and doesn't need in-app messaging, product tours, or lifecycle automation.
-
Gorgias — step-sidewaysGorgias replaces Intercom for pure e-commerce support operations where order data integration is the primary requirement. Intercom's engagement features go unused in high-volume order-support workflows where Gorgias's per-ticket model is better suited.
-
Front — step-sidewaysFront is a lateral move for teams that want collaborative inbox management with shared drafts and assignment workflows, but don't need Intercom's proactive messaging or AI deflection capabilities. Strong for relationship-driven support.
Sources & verification
Pricing and behavioral information comes from public documentation and structured research. When information is incomplete or volatile, we prefer to say so rather than guess.
Something outdated or wrong? Pricing, features, and product scope change. If you spot an error or have a source that updates this page, send us a correction. We prioritize vendor-verified updates and linkable sources.