Skip to content
Notifications
Clear all

Migrated from Help Scout to Intercom for 100 agents - what broke

3 Posts
3 Users
0 Reactions
73 Views
(@danielk)
Honorable Member
Joined: 4 months ago
Posts: 382
Topic starter   [#19920]

Just finished a forced migration off Help Scout due to scale. 100 agents, B2B SaaS. Intercom was the sales/marketing team's pick. The transition broke three core workflows for support engineering.

* **Granular role-based access control (RBAC) is gone.** Help Scout's "Teams" with mailbox-level permissions was clean. Intercom's "Teams" are just reporting groups. Actual access control requires a messy combination of "Conversation access," "Admin roles," and "Partition" assignments. Our tiered support structure (L1/L2/Engineering) is now a permissioning nightmare.
* **API rate limits hit us immediately.** Help Scout's were reasonable. Intercom's are aggressively low for a platform at this price point. Bulk actions or syncing conversation state to our internal systems now requires aggressive queuing and retry logic.
* **Automation rules are not portable.** Our Help Scout workflows relied on specific conditional logic (tags, customer tier, previous replies). Intercom's "Workflows" use a different paradigm. Recreating them wasn't a 1:1 mapping. Lost several SLA timers during the cutover.

Biggest immediate pain point: The Intercom Inbox has no native "Saved Replies" equivalent. Their "Articles" are a clunky workaround. Agents are wasting time.

Looking for concrete fixes, especially on the RBAC and automation front. How are others structuring permissions for 100+ agent teams in Intercom without giving everyone access to everything?

-dk


Trust but verify, then don't trust.


   
Quote
(@cloud_ops_learner)
Honorable Member
Joined: 6 months ago
Posts: 419
 

I'm a solo ops engineer at a 60-person B2B SaaS, where I manage our support platform as part of my infra duties. We've run both Help Scout and Intercom in production for different teams.

Here's my breakdown based on that experience:

**Target Audience and Fit:** Help Scout is built for support-first teams that need clean structure. Intercom is for sales/marketing-led orgs where support is one channel in a suite. The forced migration you described is a classic symptom of that mismatch.
**Real Pricing & Hidden Costs:** Help Scout is simpler, around $25/agent/month for your scale. Intercom's published price is just the start. You'll pay more for required add-ons like the "Inbox" you mentioned, and the aggressive API limits mean you'll spend engineering time building queuing systems, which is a real cost.
**Deployment and Integration Effort:** Migrating workflows between these platforms is a rebuild, not a lift-and-shift. Help Scout's rules and tags map cleanly to support logic. Intercom's Workflows are built for lead scoring and marketing automation. The paradigm shift is the hidden migration effort that breaks SLAs.
**Where It Breaks / The Limitation:** You hit the big ones: RBAC and rate limits. Intercom's permissioning is an afterthought for sales teams who all need the same access. Help Scout's Teams and mailbox permissions are designed for structured, tiered support. The API limit for Intercom at my last shop was 500 requests per minute per app, which we blew through daily.

I'd stick with Help Scout for a pure, scaled B2B support team. If the sales/marketing suite is non-negotiable, you need two things to decide: your exact required API call volume per day, and whether you can rebuild your L1/L2/Engineering tiers using only Intercom's "Partitions."


Still learning


   
ReplyQuote
(@annac)
Reputable Member
Joined: 4 months ago
Posts: 391
 

You're absolutely right about the paradigm shift. The part about **Workflows being built for marketing automation** is key. We tried to port a simple "auto-close resolved conversations after 72h" rule, and in Intercom you're suddenly building a canvas with delays and branches. It feels like using a bulldozer to plant a flower.

And the hidden API cost is so real. It's not just engineering time, it's the mental overhead. Now every sync job needs a retry-and-throttle layer we didn't have before. For a team your size, that's a significant new piece of infra to babysit.

Your point on pricing is also spot on. That $25/agent/month at scale? That's the *all-in* cost for Help Scout. With Intercom, that's just the entry ticket before you add the required modules.


Keep it simple.


   
ReplyQuote