The support@ audit: what a seed-stage SaaS inbox contains (pre-sales vs support vs billing), and why the resolution rate is the wrong first number

Nobody has published what a seed-stage SaaS support@ inbox contains: the share that is pre-sales, how-do-I, billing or bugs, when it arrives, and how much ends resolved rather than handed off. Founders choosing an AI tool therefore compare vendor resolution rates instead, and those rates span from a practitioner's rough 30% to a calculator default of 73%¹². That spread measures inbox mix and billing definitions, not tool quality. Audit 90 days of your own support@ before you compare anything.

What do founders assume about AI resolution rates?#

The common view among early-stage founders is that an AI support tool should be judged by its resolution rate, because the rate predicts both the hours saved and the bill. Vendors supply the figures. Help Scout's pricing calculator states "The average resolution rate is 73%"¹. An Intercom search ad seen on 1 October 2026 claimed a "76% Avg Resolution Rate." Klarna, the largest public case, reported in May 2025 that its chatbot "still handles two-thirds of all customer inquiries"³.

On that view the decision is arithmetic. Take monthly volume, multiply by the advertised rate, multiply by the per-resolution price, and compare the result with an hourly wage. Several Valet posts run that arithmetic, and the arithmetic is not wrong. The input is.

Why do sensible founders trust the vendor number?#

Founders trust the vendor resolution rate for good reasons, and the reasons deserve a fair statement before any objection. The rate is the only comparable figure on offer, since no founder has the time to run three tools side by side on the same inbox. It is tied to price, which makes it look audited. And at a seed-stage company the coordination cost of measuring anything is high: the person who would count the inbox is the person answering it.

The rate also matches lived experience at first. A founder who turns on any competent tool sees the easy questions vanish within a week. That early drop feels like proof of the advertised figure. It is proof of something narrower.

Where does the resolution-rate assumption break?#

The resolution-rate assumption breaks on two points: the rate is a property of the inbox, and the definition of "resolved" is written by the party paid per resolution. Both points are visible on public pages.

On the first point, the published figures are not measuring the same thing. A commenter in a May 2025 Hacker News thread, describing ten years in contact-centre AI, put typical chatbot deflection at roughly 30% of inbound contacts (wording as reported in that thread)². A former support lead who ran Fin rollouts wrote in June 2026 that "~50% of the inbounds I receive are fully written out in plain language in an FAQ"⁴. Another practitioner in the same thread wrote that "Containment from the bot alone shot up past 50%" once the bot had "account awareness"⁴. Those are different inboxes, with different shares of routine questions, producing different ceilings.

On the second point, Fin's pricing FAQ counts a resolution when "No further help is requested after Fin's last answer"⁵. A customer who gives up and a customer who was helped look identical under that rule. A commenter in the June 2026 thread called it "A very soft resolution metric"⁴. This is a principal-agent problem in its textbook form. The agent that bills per unit also defines the unit.

What decides how much of your support@ an AI can answer?#

The share of your support@ that software can truly finish equals the share of email answerable from your written facts, minus whatever the billing definition counts as silence. Everything else in the decision follows from that sentence. A tool cannot resolve a billing exception that your policy never wrote down, and it should not try.

Three lines of evidence, weakest first#

Evidence 1: the published rates span too wide to describe tools#

Published AI resolution figures run from about 30% to 76%, a range too wide to be a property of software. The low end is a practitioner's estimate across contact centres². The middle is one support lead's FAQ share and one Sierra rollout⁴. The top is a vendor calculator default and a search ad¹. Klarna's two-thirds is a single fintech at very large volume³. A seed-stage SaaS with a heavy share of bugs and billing could sit below all of them. One with a plain product and a good FAQ could sit above. Neither founder learns which from a vendor page.

Evidence 2: vendors define the unit differently#

Vendor definitions of a resolution differ in ways that move the rate. Fin counts the customer not asking again⁵. Help Scout counts a resolution "only if the customer receives an AI response and doesn't use escalation, search the knowledge base, ask more questions, or indicate that they need more help," and does not charge when the customer clicks "I still need help"¹. Same inbox, two definitions, two rates. Intercom itself declined to price its sales agent on closed revenue, writing that the purest model "breaks down" on attribution and measurement⁸. If the vendor cannot measure the outcome, the founder should not assume the rate measures it either. Our side-by-side of seven definitions is in what counts as an AI resolution.

Evidence 3: handoffs, not resolutions, are where outcomes split#

Handoff data shows the outcome a resolution rate hides. In Gorgias platform data from accounts with 200+ AI-touched tickets (October 2025 to April 2026), 55% of AI-touched tickets went to a human, and about a third of those never got a human reply. The median wait after handoff was 10 hours; the 90th percentile was 71 hours⁶. Those are e-commerce brands, not SaaS, and the cohort is self-selected by tool choice. The second-order effect still transfers: a tool can report a respectable resolution rate while a third of its handoffs end in silence. Only a record of each conversation's end state separates "resolved," "stopped asking" and "handed off and dropped."

What would a support@ audit of a seed-stage SaaS show?#

A support@ audit counts every thread in a window by category, arrival hour, first-reply time and end state. The nearest published counts come from other sectors. Gorgias found that about 1 in 9 e-commerce support inquiries is a pre-purchase question¹⁰, and that 53% of pre-purchase questions arrive outside business hours, with a median first reply of about 15 hours against 2.2 hours in hours (July 2026)⁷. Leadferno's 2024 test of 225 small-business contact forms found 42.6% got no reply at all⁹. Both state their n and method. No equivalent exists for seed-stage SaaS.

Founders describe the mix in fragments. "I write code, I do support, I handle billing issues," wrote one in r/EntrepreneurRideAlong (20+ comments, mid-2026). A thread in r/smallbusiness (10+ comments, September 2026) asked how much of the day goes to "the same 20 questions." Those fragments suggest a large routine share, but a fragment is not a denominator.

Valet could run this audit across many small inboxes and publish a quarterly aggregate, with n, method and per-segment tables. No such dataset exists today, and this page reports none. The method below lets any founder produce the same numbers for one inbox.

Summary (fill after tagging):
Routine share      = threads "Answerable = Yes" / all threads
Out-of-hours share = threads out of hours / all threads
Pre-sales share    = Pre-sales threads / all threads
Silent share       = "Stopped replying" / all threads
Dropped handoffs   = "Handed off, never answered" / all handoffs
Your honest ceiling for automation ~= Routine share
Compare any vendor rate with Routine share, not with each other.

For the five-outcome version of this method applied to leads rather than support, see the Lost Lead Audit. For a runbook that uses the audit's categories, see how to handle support@ as a solo or 3-person SaaS founder.

When is the vendor rate still the right number?#

The vendor resolution rate remains a reasonable planning input in three cases. When the inbox is high-volume and uniform, as in stores where order-status questions dominate, the mix varies less between companies and a published rate travels better. When the definition is strict, as with Help Scout's, the rate is closer to a confirmed outcome¹. And when a founder needs only a ceiling for a budget line, the advertised rate works as a worst case for cost, since a higher rate means a higher bill under per-resolution pricing.

Where this argument would be wrong, and what to do on Monday#

The case against vendor rates fails if a published, denominated study shows seed-stage SaaS inboxes are similar enough that one rate fits most of them, or if vendors move to definitions that require confirmed resolution. Either would make the vendor number a usable prior. Neither exists as of October 2026.

Until then the local optimum, picking the tool with the best advertised rate, carries a perverse incentive the founder pays for. The Monday decision is small: export 90 days of support@, tag it with the sheet above, and compute the routine share. That one number tells you more about your tool choice than any vendor page.

Where Valet fits#

Valet keeps the end state that this audit asks for. You forward support@ to a private Valet address; replies go out from your own address once the domain is verified, with nothing to migrate. Valet answers only from your own facts, and anything not on them waits for you. Every inquiry has a state and a next step, and every reply has a Valet receipt: what was asked, the rule used, the sources used and where it was sent from, so "resolved" and "handed off" are separate records. Money, complaints and legal questions come to you with one-tap replies, and the customer is told when you will reply. To start smaller, the free lead check: forward 10 to 20 recent emails and see what went unanswered or stopped after one reply.