Help Scout states its own reply rate, not a universal target

The workload

Help Scout sells support software, and also has to run its own support operation for its own customers, a workload the company describes on its own site rather than leaving unstated. Help Scout's homepage, as retrieved 16 September 2026, states that its own team answers 99% of emails within 24 hours, a named response-time claim about the company's own support workload, not a feature description of the product it sells others. The same page states that 80% of customers are still there after four years, a retention figure presented alongside the response-time claim, though the page does not describe how either was measured or over what period.

What the documents show

Verified: Help Scout's own page states the 99%-within-24-hours figure and the 80%-four-year retention figure as current facts, but supplies no measurement window, sample size, or methodology beside them, so this entry treats them as stated vendor claims, not an independently audited service-level report. Verified: Help Scout's own status page, also as retrieved 16 September 2026, runs on Atlassian's Statuspage, its subscription terms reference the Atlassian Terms of Service directly, and lists Help Scout's Web App, Docs Sites, Beacon, mobile apps and several AI-feature components individually, each marked with an operational state and a note that uptime is tracked over the past 90 days. At retrieval the page also listed a scheduled database maintenance window for 26 September 2026, stated in advance.

The operating cost

Verified: neither page states a dollar cost for maintaining a 99%-within-24-hours response rate; no support headcount, shift structure or tooling budget is disclosed on either page. This entry treats the response-time figure as an example of publishing a stated target, per this site's own workload research, not as evidence of what it costs Help Scout, or would cost a smaller operator, to sustain a comparable rate. Estimated: for a one-person operation attempting the same window without a team spread across time zones, the practical cost is calendar coverage, checking messages daily without exception, an inference this entry draws from the target's structure, not from anything the pages state about staffing.

The stop condition

No cited page states what happens if Help Scout's own reply rate falls below 99%, or names a floor below which the company would treat the target as broken. Editorially, the stop condition implied by publishing the figure at all is reputational: a company that states a specific reply-rate number on its own homepage invites a reader to check it against later evidence, which is a stronger public commitment than a vague promise of fast support, even without an enforcement mechanism named.

• Does a published response-rate figure state its measurement window and sample size?
• Is a status page's operational label about uptime, response time, or both?
• What would it cost a one-person support operation to match a stated 24-hour reply target every day of the year?

Help Scout's own pages state a specific reply-rate number and a specific incident-communication structure. Neither page states what either costs to sustain, which is the gap a smaller operator modeling the same practice would need to fill for themselves.