Running Help Scout?

Help Scout mailboxes routing to the wrong team? We bring it back.

Help Scout stays out of the way until a workflow silently stops firing on the mailbox that gets the paying customers, Docs search starts returning nothing for a search anyone would try, or the shared inbox fills up with messages from an alias that nobody remembers adding. We look at the workflow history, the mailbox settings and the Beacon configuration, and we hand it back with routing you can explain in one sentence.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

help-scout.log

still broken

What it is

Help Scout at a glance

Help Scout is an email-first helpdesk from Help Scout PBC, founded in 2011 in Boston and run as a certified B Corp. It gives support teams a shared inbox that looks and feels like email to the customer, with internal threads, workflows, saved replies, reporting and a Docs knowledge base attached.

Teams choose it because customers get a plain-looking email rather than a ticket number, and because it keeps the UI focused instead of trying to be a full CRM. Live chat is handled through Beacon, which also surfaces Docs articles inline. The API is REST and covers mailboxes, conversations, customers, workflows and reports.

Type
Email-first shared inbox helpdesk
First released
2011
License
Proprietary, per-user subscription
Maintained by
Help Scout PBC
Typically used for
Shared customer email, knowledge base, in-app chat via Beacon

The honest version

Help Scout pros and cons

No technology is all upside. This is where Help Scout earns its place and where it tends to cause trouble.

Where Help Scout is strong

  • Customers see email, not a ticketReplies look like a normal message from a person, which removes the friction of 'Case #48291' subject lines and often raises reply rates by itself.
  • The UI stays out of the wayThe agent view focuses on reading and writing the message, with internal threads and tags discoverable but not loud.
  • Workflows are easy to readRules read as conditions and actions in plain English, which keeps the automation layer legible when a new teammate has to debug it.
  • Docs and Beacon work togetherArticles surface inside the chat widget as suggestions, which deflects the easier tickets before an agent has to answer them.
  • Reports cover the useful metricsVolume, resolution time, customer happiness and workflow activity are available out of the box without needing a separate analytics tool.
  • Honest B Corp pricingThe plans are straightforward with no surprise upsells, and the per-user cost is predictable at the scale most SMB teams run at.

Where Help Scout bites

  • Not built for ticket-number workflowsTeams migrating from Zendesk or Jira Service Management who rely on case IDs across systems find Help Scout's conversation model harder to bridge.
  • Reporting depth is limitedBeyond the built-in reports, deeper analysis needs an API export. Cohorts, funnels and attribution are not native concepts.
  • Beacon customization is shallowThe chat widget covers common cases but customizing behavior beyond presets usually means writing against the JS API and hoping it keeps working.
  • Docs search is string-basedPartial matches, synonyms and semantic search are weaker than modern tools, and articles with the wrong title can simply disappear from search.
  • Workflow debugging is thinWhen a workflow does not fire, the activity trail does not always show which condition failed. You end up re-running a conversation to reproduce it.
  • Multilingual support needs workDocs sites by language are possible but setup is clunky, and detecting a customer's language from the inbound message is not built in.

Sound familiar?

Common Help Scout problems we fix

The Help Scout problems that bring people to us, and what you have once each one is fixed.

Workflow did not run: conditions did not match

A workflow quietly stops firing

A condition on a tag that was renamed, a mailbox restriction that no longer includes the inbox the mail actually arrives on, or a prior workflow that already closed the conversation.

Workflow firing on the right messages

SMTP: 550 DMARC alignment failed

Replies from Help Scout get rejected

A custom sending domain where SPF and DKIM are not fully set, or a DMARC policy at reject while the authentication is only partially aligned.

Mail delivers from your domain

Email forwarding loop detected

A mailbox stops receiving mail

A Google Workspace rule forwarding back to the same address, or a secondary alias that reinjects messages into the inbox they came from.

Mail flows in without bouncing

Docs search returned empty result set

Customers cannot find articles that exist

Titles missing the exact phrase a customer would type, a Docs collection marked private that holds the public answer, or indexing paused after a bulk edit.

Docs search returns the right articles

Beacon: failed to send message

Beacon chat drops under load

Websocket connection blocked by a strict CSP, business-hours routing to an empty team, or a cookie policy that prevents the widget from persisting a session.

Beacon reliably online during hours

API: 429 Too Many Requests

Integrations hit the hourly API limit

A sync that lists conversations without using the modifiedSince filter, or a webhook replay running without exponential backoff.

Integrations stay within the quota

Integration: HubSpot sync failed

Third-party integrations stop updating

An OAuth refresh that never happened, a field mapping to a property that was removed in HubSpot, or a conversation containing characters the target system does not accept.

Sync healthy between systems

Saved reply variable not resolved

Saved replies send with raw template placeholders

A variable referring to a customer property that is blank, or a merge field renamed after the saved reply was written.

Saved replies render cleanly for every customer

What we do

Help Scout help, from rescue to upkeep

Ring us for one broken workflow, or move the whole helpdesk estate onto our care.

Rescue
Mail bouncing, workflows silent, or Beacon offline during business hours. We stabilize the mailbox first and write up what broke second.
Domain and deliverability
SPF, DKIM, DMARC and custom sending domains set up so replies land in the inbox and not spam.
Workflow and routing design
Conditions, order of workflows and tag taxonomy rebuilt so new teammates can read the automation without a map.
Docs structure and search
Article titles, categories and internal links reworked so Docs search returns the right answer on the first try.
API and integrations
Custom integrations with HubSpot, Salesforce, Shopify and internal tools using the Help Scout API, with retries and rate-limit respect.
Managed Tech
Weekly workflow reviews, deliverability watchers, Beacon health checks and a US engineer to call when a mailbox starts bouncing.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Help Scout alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Help Scout questions

Something else? Call+1 737 727 7327

Why did our Help Scout workflow stop firing?

The three most common causes are a condition on a tag that was renamed or removed, a mailbox scope that no longer includes the inbox mail actually lands in, and an earlier workflow that closes or assigns the conversation first. Replaying the conversation with activity on screen is the fastest way to tell which one it is.

Why are our replies going to spam?

Usually the custom sending domain is only partially set up. SPF may pass but DKIM is missing, or the DMARC policy is at reject while alignment is on the wrong side. Getting both SPF and DKIM to align on the sending domain, then letting DMARC settle, clears most of it. A reputation warm-up helps if you just switched domains.

Should we use Help Scout or Zendesk?

If your customers expect a reply that reads like email and your team is under fifty agents, Help Scout usually wins on customer experience and admin time. If you need case IDs threaded through other systems, deep reporting or complex multi-channel routing with SLAs, Zendesk tends to fit better. We help teams move either direction when the fit stops working.

Can Beacon be styled to match our product?

The common styling, trigger and routing options are available without code; anything bespoke means writing against the Beacon JS API. We build custom Beacon integrations that keep working after platform updates, and we test them across the browsers your customers actually use.

How do we export Help Scout data to our warehouse?

The API covers conversations, customers, workflows and reports. We build an incremental pipeline that uses modifiedSince filters, respects the hourly limit, and lands clean rows in BigQuery, Snowflake or Postgres. Once in place, your BI team can report on Help Scout data alongside everything else.

How much does Help Scout help cost?

Estimates are free of charge. Describe the mailboxes involved, the workflows in question and any recent changes, and a Hawkins.Tech engineer responds with a price.

Free estimate

Help Scout giving you trouble?

Tell us which mailbox is affected and what customers are seeing, and a Hawkins.Tech engineer gets back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.