Help Scout review: a shared inbox that grew a pricing problem

I moved off a plain shared Gmail account when two things started happening at once: replies were going out twice, and I had no idea how long anyone had been waiting. That is a small problem with an enormous number of tools competing to solve it.

I picked Help Scout because it was the only one where the customer’s experience of support was still just email.

The month in practice

Setup was under an hour, most of it DNS. Import of existing Gmail threads was partial — I got recent conversations, not the whole archive — and I stopped caring within a week.

The daily experience is genuinely good. The queue is quiet and legible. Saved replies took twenty minutes to write and cut my median response time roughly in half. Collision detection stopped the double-reply problem the same day. Assigning, snoozing and tagging all work the way you would guess, which sounds like faint praise until you have used a help desk where they do not.

The best single feature is what the customer sees: a plain email, from my address, with no ticket number and no reference footer. Three separate customers replied conversationally to threads that had gone through the tool without ever noticing it existed. For a small business trying not to sound like a call centre, that is worth real money.

Where it went wrong

Pricing. Help Scout charges per user and then meters contacts — distinct people you have talked to in the billing period. That number is not correlated with how much support work you are doing, and it is not correlated with revenue either. A launch week where 300 people email once costs far more than a quiet month where 20 customers each need serious help. The second month is the one that is actually expensive to serve.

I hit the contact tier twice in five months, both times in a week that was good news for the business. Finding out on the following invoice is not a crisis, but it is the wrong incentive baked into the bill — and for a solo operator it is a real reason to hesitate before a campaign.

The other soft spot is reporting. It is competent and shallow: volume, response time, happiness score. When I wanted to know which of my docs pages were failing hard enough to generate tickets, I ended up tagging manually and counting in a spreadsheet.

Support from the support company

Fast, human, and answered by someone who read the whole thread. Under four hours both times. It would be embarrassing for them if this were not true, but plenty of help-desk vendors manage to fail it anyway.

The verdict

Three and a half. The product is a four and a half; the pricing model takes a point off, and I am docking it because the price is not a footnote — it is the thing that will decide whether you keep this.

I am still using it. I also have a calendar reminder to re-run the numbers each January, and I have already priced the migration. That is not how you feel about software you are settled on, and the rating reflects it.