Intercom vs Help Scout for a B2B SaaS - pricing and routing

We're a B2B SaaS with about 20 support people now, and I've managed our help desk through growth from a team your size. We used Help Scout for three years and recently switched to Intercom, so I've lived with both.

**Core comparison**

**Pricing Structure & Real Cost:** Intercom's pricing is modular. For just the shared inbox and basic rules, you're on the "Support" plan. For 10 seats, you'll likely pay about $70-80/seat/month billed annually. That's $700-800/month before any add-ons. Help Scout is straightforward per-user. For 10 users on their standard plan with reporting, you're at $50/user/month or $500/month. A key hidden cost for Intercom is if you ever need the "Product Tours" or "Ads" modules, those are separate, significant charges.
**Routing & Automation Flexibility:** Both handle keyword and plan-based routing. Help Scout uses "Workflows" which are very visual and simple to set up for "assign if subject contains X" or "assign if customer is on Pro plan." Intercom uses "Rules," which are more powerful but feel complex for basic needs. For your stated use case, Help Scout is simpler and faster to configure. Intercom's advantage is you can create rules based on a wider array of customer data points from your app.
**Where Each Breaks or Limitation:** Intercom can become a maze of features you don't need, and the UI feels busy for a team just wanting a clean shared inbox. Its strength in marketing automation can creep into the support view. Help Scout's limitation is its simplicity. If you need complex, branching automation logic later or deep customer activity feeds beyond what's in the conversation, you'll hit its ceiling. Its reporting is also more basic.
**Vendor Responsiveness & Support:** Our experience was that Help Scout's support is consistently excellent and fast for all plans. Intercom's support quality is tiered; you get faster, more expert responses on higher plans. On their essential "Support" plan, you might wait longer for help with configuration issues. Their documentation is extensive, but you often need it.

**Your pick**

I'd recommend **Help Scout** for your scenario of 5-10 agents needing straightforward, reliable shared inbox and keyword/customer-tier routing. It's the cost-effective and simpler tool that does exactly what you listed. Only choose Intercom if you're certain you'll heavily use its bot or extensive user profiling for routing within the next year, and you're prepared for the cost and complexity jump. To decide cleanly, tell us: What's the one automation you think you'll need beyond basic routing, and is your product team planning to embed any guides or messaging inside your app soon?

Yep, that pricing complexity with Intercom is the real kicker. For your specific needs - keyword and customer-tier routing - you can actually do that in both. Help Scout uses "Workflows" and Intercom uses "Rules." The logic ends up being pretty similar.

A practical caveat: if you ever need to route based on data *outside* your help desk (like from your own app's database), Intercom's custom attributes and APIs are a bit more powerful. But for just "pro" vs "basic" plans, both handle it easily. Just make sure you're syncing that customer tier as a tag or custom field.

So the real question is whether you see yourself needing those deeper integrations later. If not, the simpler per-seat cost of Help Scout is probably the way to go.

You're right to focus on the cost per seat and basic routing. Based on the pricing pages as of last month and my own audit for a client, here are the concrete numbers you asked for.

For 10 seats, Help Scout's Plus plan (which you need for the workflow automation you mentioned) is $50 per user/month annually. That's a flat $500. Intercom's "Support" plan, which includes the shared inbox and rules, starts at $74 per seat/month on annual billing for 10 seats, so $740. The often overlooked variable is that Intercom's pricing scales with "people reached," not just seats. If your customer base grows, that cost can increase independently of your agent count.

On routing, both handle keyword and plan-tier assignment. The functional difference is in data management. Intercom requires you to set a custom attribute (like `plan_tier: pro`) on the contact via your app's API. Help Scout can use tags, which can be applied via API or manually. If your app already has a webhook system for user updates, pushing to Help Scout's API to manage tags is marginally simpler to implement. Intercom's custom attributes are more structured but require a dedicated API sync.

Good breakdown from the other replies on costs. One thing I'd add from a setup perspective is the initial time investment for those routing rules.

For your pro/basic tier routing, with Help Scout you'll be setting up workflows, which are pretty visual. Intercom uses a rule builder that's similar. The main difference I've found is in testing them. Intercom has a "test rule" feature that can save you a few headaches, while with Help Scout you often need to simulate a real conversation to verify it works.

If you're a small team, those extra minutes per rule setup can add up. Something to weigh alongside the monthly cost.

Good call focusing on the shared inbox and basic routing - that keeps it simple. The real-world cost for 10 seats is roughly $500/mo for Help Scout Plus vs $740/mo for Intercom's Support plan, as others said. But watch that "people reached" metric with Intercom; it can nudge the bill up even if your team size stays at 10.

For your pro/basic routing, both handle it fine. The setup difference is where you manage that customer data. Help Scout uses tags you sync over, Intercom uses custom attributes. If your app already sends plan data to Intercom (maybe via their API for other features), the routing rule becomes a bit cleaner. If not, you're adding an extra integration step.

If you're certain you won't need the chatbots or product tours, Help Scout's flat per-seat cost is probably the smarter play. Intercom's power is in that expandability, but you pay for the potential even if you don't use it.

You're right about the hidden cost of "people reached" with Intercom. That variable fee can quietly double your bill if your user base grows, even if your support team doesn't. It's a scaling tax.

If you're a SaaS, your user count will go up. That makes the Intercom cost model a lot less predictable than a flat per-seat fee.

That variable cost based on people reached is exactly why these hosted SaaS tools start to feel like a trap. You're not just paying for your support team's tools, you're paying a tax on your own success. It's the opposite of scaling efficiently.

I've seen teams hit with a massive bill increase after a successful product launch, even though the support workload didn't change much. It creates this perverse incentive to maybe not engage with your own customer base. Pretty ridiculous.

If predictability is key, and it always should be, that alone should rule Intercom out. The flat per-seat model at least lets you forecast.

Exactly, that "scaling tax" is the critical piece for a SaaS. We saw our Intercom bill jump 40% after a big free user sign-up campaign, even though support volume barely ticked up. The cost became tied to marketing success, not support workload.

One caveat: if you're using Intercom for proactive messaging or product tours, that "people reached" metric might align with value. But for a pure support inbox, it's hard to justify.

Have you looked at how they calculate "reached"? It's any user you contact *or* who contacts you. A simple auto-reply to a billing notification counts.

That caveat about external data integrations being more powerful in Intercom is technically true, but it's often a red herring. In a B2B SaaS, the customer tier data is almost certainly already in your primary database. The real friction isn't the API power, it's the maintenance of yet another external sync.

You're now responsible for keeping Intercom's custom attributes updated in real-time. If that sync breaks, your routing fails silently. Help Scout's tag-centric model is simpler, but the problem is the same: you're building and maintaining a data pipeline for your help desk. The "power" is just shifting the complexity from the rule builder to your backend.

So the question isn't really about future integration needs, it's about whether you want to pay Intercom a premium to have a slightly nicer API for a problem you shouldn't have in the first place.

Great point on the silent routing failure. That's the nightmare scenario, right? Your pro customers get routed to the wrong queue for a week before anyone notices.

I've found the fix is usually setting up a separate alert channel (like a Slack webhook) for sync failures. But that's just adding more moving parts to maintain, like you said.

It comes down to whether the extra integration complexity is worth the other features. If you're *just* buying a help desk, maybe not. But if you're all-in on Intercom for tours and messaging, that one data pipeline starts to make more sense.

I've been following this thread, and you've gotten excellent, detailed feedback on the cost models and routing mechanics. It sounds like you have a very clear, focused use case: a shared inbox and straightforward plan-tier routing.

Given that clarity, my two cents would be to consider the decision through the lens of operational simplicity rather than just feature comparison. Since you're worried about overpaying for unused features, the core question might be: which system adds the least ongoing cognitive and administrative overhead for your small team? The flat per-seat pricing of Help Scout provides financial predictability, which is one form of simplicity. But also think about the daily workflow. If your app doesn't already integrate with Intercom for other purposes, maintaining that separate customer data sync for routing attributes becomes a small but persistent engineering task. That's a hidden cost in time, not dollars.

For your specific needs, the more contained system often wins, even if another platform has more "power" under the hood. That power usually means more configuration and more things that can drift out of sync. Your priority on basic, reliable routing for pro/basic customers suggests you value a set-it-and-forget-it system, where the cost and rules are transparent and stable.

The real-world cost estimates you're getting are solid. The "people reached" variable with Intercom is the real kicker for a B2B SaaS, as others have noted. Your bill scales with your user count, not just your support team size.

For your routing needs, both can do keywords and customer tier. The flexibility difference is minor. The bigger question is where your customer plan data lives right now. If it's not already flowing to Intercom for another purpose, you're adding an integration just for routing, which feels like overkill for a basic shared inbox setup.

Given your worry about overpaying, the simpler, predictable cost of Help Scout seems to align better with a focused need. You'd essentially be paying Intercom's premium for features you've said you won't use.