The problem with comparing support-tool pricing isn't arithmetic — it's architecture. Crisp charges a flat fee per workspace regardless of team size. Help Scout charges per seat. Chatwoot splits into cloud (per-agent) and self-hosted (infrastructure-only). Similar sticker prices on day one, wildly different cost curves as your team grows. Pick the wrong pricing shape and you'll watch your support budget climb in ways the signup-day spreadsheet never warned you about.
The flat-rate model: Crisp
Crisp operates on flat-fee tiers tied to included features and agent slots, not headcount. Per Crisp's own pricing page, the Essentials plan runs $95/month and includes 10 agent seats, 50,000 customer profiles, $25 in AI credits, and an omnichannel inbox with workflow automation. The Plus tier ($295/month) covers 20+ agents and 200,000 profiles. Extra agents beyond what your plan includes cost $10/month each. That means a team of 5 agents on Essentials pays exactly what a team of 8 on the same plan pays: $95. You only pay per extra head once you exceed the included count.
If your headcount stays within the plan's agent allowance, scaling your team doesn't touch the bill at all.
The per-seat model: Help Scout
Help Scout takes the classic SaaS approach: charge per user. Per Help Scout's pricing page, Standard costs $25/user/month ($21/user billed annually) and covers 2 inboxes and basic workflows. Plus ($45/user/month, or $37.80 annually) unlocks unlimited users, 5 inboxes, and advanced workflows. Every new hire is a new line item, every month, no exceptions.
There's a real upside: unlimited inboxes and richer features unlock as you grow, and per-seat billing forces honesty about exactly who's actually working tickets. The downside shows up in the math below.
The hybrid: Chatwoot, cloud or self-hosted
Chatwoot splits into two genuinely different cost models. Cloud pricing is per-agent: the Startups tier costs $19/agent/month and includes 300 Captain AI credits and unlimited conversations; Business ($39/agent/month, billed annually) adds voice channel support and more credits.
Self-hosting is the interesting branch. The Community edition is free per agent — $0/agent/month — which means a self-hosted team of any size pays nothing for seat licensing, just infrastructure. Per Chatwoot's own documentation, a production deployment needs 4+ CPU cores, 8GB+ RAM, 50GB+ SSD, PostgreSQL, and Redis. A DigitalOcean Basic droplet matching that spec runs $48/month flat. (Premium Support self-hosted, $19/agent/month, adds Captain AI and voice; Enterprise self-hosted, $99/agent/month, adds SSO/SAML and SLA policies.)
The structural point: once you self-host on Community, adding agents doesn't touch your hosting bill — up to whatever your VPS can actually handle — only your own operational overhead.
The numbers: 3, 8, and 15 agents
Here's where pricing shape stops being theoretical:
| Team size | Crisp | Help Scout | Chatwoot Cloud | Chatwoot Self-Hosted |
|---|---|---|---|---|
| 3 agents | $45/mo (Mini, up to 4 included) | $75/mo (3 × $25) | $57/mo (3 × $19) | $48/mo (VPS only, $0/agent) |
| 8 agents | $95/mo (Essentials, up to 10 included) | $200/mo (8 × $25) | $152/mo (8 × $19) | $48/mo (same VPS, $0/agent) |
| 15 agents | $295/mo (Plus, 20+ included) | $375/mo (15 × $25) | $285/mo (15 × $19) | ~$48/mo (may need a bigger box at real scale, still infra-only) |
Read the columns, not the rows. Crisp's cost jumps between plan tiers rather than climbing smoothly. Help Scout and Chatwoot Cloud creep up in a straight line with headcount. Self-hosted Chatwoot barely moves.
At 3 agents, the gap is noise — everything lands between $45 and $75. At 15 agents it isn't: Crisp is $295/month, Help Scout has climbed to $375, Chatwoot Cloud undercuts Help Scout at $285 but still costs six times what self-hosting does. Self-hosted Chatwoot, if you're willing to own the ops, is still roughly $48.
What the curves actually mean
This isn't a case for "self-hosted is cheapest, obviously." Running your own server has real costs this number doesn't capture — your time, patching, backups, on-call stress, the inevitable 2 a.m. Postgres connection-pool fire drill. Those costs are real and, deliberately, not estimated here.
What the curves do show is that pricing shape sets your scaling incentives. With Help Scout or Chatwoot Cloud, hiring another support person is an immediate, permanent cost increase. With Crisp, it's free until you hit a plan ceiling, then it jumps. With self-hosted Chatwoot, headcount stops being a billing question and becomes an ops-capacity question.
That matters most for teams with variable access patterns — engineers dipping into tickets occasionally, a founder handling the angry-customer escalations personally. Help Scout and Chatwoot Cloud count every one of those people as a seat. Crisp and self-hosted Chatwoot don't. Pick the wrong model early and the mismatch compounds as you grow, not shrinks.
One more angle worth naming: a dev.to piece by kalwiggins argues per-seat support pricing specifically punishes teams whose access needs don't map cleanly to permanent seats. That holds up here — it's exactly the failure mode Help Scout's and Chatwoot Cloud's models share, and exactly what Crisp's flat tiers and self-hosted Chatwoot's zero-per-seat cost avoid.
Who should pick what
Small team (≤4 agents), no appetite for infrastructure: Crisp wins on simplicity and predictability — flat tiers, no per-head surprise tax, AI credits included. You know your bill in advance and it doesn't move when you hire your third support person.
Growing team with variable access (10+ people total, ≤8 of them full-time support): self-hosted Chatwoot Community gets genuinely attractive here, precisely because it inverts the usual incentive — adding people to the ticket queue doesn't move your bill, only your VPS capacity does. The tradeoff is real: you're now the one who owns uptime.
Team that wants the deepest integrations and a mature, conventional seat model: Help Scout is the most polished option on this list, and you pay proportionally for that polish as you grow. That's not a flaw — it's a legitimate trade for teams who'd rather buy predictability-per-seat than manage infrastructure.
One caveat that applies regardless of which way you lean: self-hosted Chatwoot Community excludes Captain AI, voice, custom branding, and priority support — the $48 figure is not feature-for-feature with the paid tiers, cloud or self-hosted. Don't choose it because the number looks good on a spreadsheet; choose it because you actually want to own the infrastructure.
There's no single winner here, and any comparison that hands you one is skipping the part that actually matters. The right tool depends on your team's shape, its growth curve, and how much operational risk you're willing to carry in exchange for a flatter bill. Match the pricing model to how your team actually grows, not to whichever number looks smallest on day one.
Researched and drafted with AI assistance, checked against primary and vendor sources.
Top comments (0)