The handoff gap: one-third of AI-handed-off tickets never get a human reply. How to measure yours, and what "resolved" should mean

A deflected ticket ended without a person. A resolved ticket ended with the customer's problem fixed. Most AI billing cannot tell the two apart. Gorgias's own platform data shows why that matters: 55% of AI-touched tickets ended in a human handoff, the median wait after handoff was 10 hours, and 33% of handed-off tickets never got a human reply at all.¹

This runbook measures the same three numbers in your helpdesk. It takes about 90 minutes. At the end you will have your own handoff rate, your own wait, your own abandoned count, and a written definition of "resolved" that you can check without the vendor's word.

What the Gorgias handoff numbers say#

The Gorgias handoff study is the largest public measurement of what happens after an AI passes a ticket to a person. It covers Gorgias merchants from October 2025 to April 2026, in accounts with 200 or more AI-touched tickets, published 28 April 2026.¹

Source: Gorgias Ecom Lab, "The cheapest ticket is the one a human never touches", 28 April 2026.¹ Gorgias defines abandonment as a handed-off ticket with no later human response.

Read the 90th percentile twice. One handoff in ten waited about three days. Email and contact forms, the channels most small teams run from a shared inbox, lost the most.

Gorgias draws its own conclusion: "The only exit is fewer handoffs."¹ That is half right. Fewer unneeded handoffs is a fair goal. But the handoffs that remain are money questions, complaints and the hard cases. Those need a person who replies.

What the gap costs a small store#

The handoff gap turns into a monthly count you can picture. Illustration Take a 300-order apparel store. Gorgias reports about 22 tickets per 100 orders for apparel and accessories.² That is 66 tickets a month. Assume every one is AI-touched. At Gorgias's rates, about 36 hand off and about 12 never get a human reply. Twelve customers a month asked for a person and heard nothing.

Deflected, answered, resolved: what each word means#

A ticket state is only useful if you can check it from your own records. Vendors bill on their own definitions, and most of them count a customer who went quiet as a success.

• Fin bills an outcome when "No further help is requested after Fin's last answer."³
• Gorgias bills when "the AI resolves a customer conversation entirely on its own. The customer asks something, the AI handles it, the conversation closes."⁴ Its research defines AI resolution rate as the share of AI-touched tickets closed without a human agent message.¹
• 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."⁵
• HubSpot Breeze reportedly treats a conversation as resolved when there is no human handoff within 72 hours. That wording comes from a secondary source; check it on a HubSpot page.⁶

None of these definitions asks whether the answer was right. Under "no further help requested", a helped customer and a customer who gave up look the same. A thread in r/webdev (60+ comments, about November 2025) put it bluntly: an AI whose promises the company will not stand behind "isn't 'support', it's a deflection layer."⁷ For the full vendor-by-vendor comparison, see what counts as an AI resolution.

Use the six states below instead. Each one names the evidence that proves it.

State	Plain definition	Evidence that proves it	Vendor terms that may count it as "resolved"
Deflected	The ticket ended with no person involved. Nobody knows if the customer was helped.	None. Silence is not evidence.	Fin "no further help is requested"; Gorgias "the conversation closes"
Answered	A reply went out that matches your written facts.	The reply, checked against your price list, policy or help article.	All of the above, if no follow-up came
Resolved	The customer's problem is finished.	The customer confirmed, or an event exists in your records: order changed, refund issued per policy, replacement shipped.	Help Scout's rule comes closest, because a customer's own action removes the charge
Booked	The inquiry became a sale, appointment or order.	A calendar event, order or signed quote you can open.	Rarely billed this way by AI support vendors
Handed off	A named person owns the ticket, and the customer was told when they will reply.	Owner name and reply-by time written in the thread.	HubSpot (reported): resolved if no handoff within 72 hours
Abandoned	Handed off, then no human reply ever came.	No human message after the handoff timestamp.	Can close on a timer and look like a resolution

Vendor wording from each vendor's pricing page or post, read 1 October 2026; HubSpot via Resolve247 (confidence M). Abandonment as defined by Gorgias Ecom Lab, 2026.

Before you start: prerequisites and the use-this-if filter#

The audit needs admin or reporting access to your helpdesk, a spreadsheet, and 30 days of AI-touched tickets. Check these before you export anything.

1. Confirm your role. You need permission to export tickets with timestamps. If the export button is missing, ask the account owner for a reporting role. Do not proceed with screenshots.
2. Find the handoff field. Look for a handoff event, a tag the AI adds, or an assignment change from the AI to a team member. If none exists, stop. Ask your vendor how a handoff is recorded. You cannot measure what is not logged.
3. Find the first human reply time. Your export must show when a person first wrote back. A "first response time" that counts the AI's reply will hide the gap.
4. Check the volume. Gorgias measured accounts with 200 or more AI-touched tickets.¹ Under about 50 tickets, treat your results as a rough read, not a benchmark.

How to measure your handoff gap, step by step#

The measurement takes seven steps. Each step has a check. If a check fails, fix it before you move on.

1. Export 30 days of AI-touched tickets. Include: created time, channel, handoff time, first human reply time, closed time, close reason. Check: your row count matches the AI ticket count on your dashboard. If it does not, look for merged tickets or a channel filter.
2. Count handoffs. Divide tickets with a handoff time by all AI-touched tickets. That is your handoff rate. Gorgias's figure is 55%.¹ Check: spot-read five handoffs to confirm the field means what you think.
3. Measure the wait. For each handoff with a human reply, subtract handoff time from first human reply time. Sort the column. Take the middle value (median) and the value 90% of the way down (90th percentile). Compare with 10 hours and 71 hours.
4. Count abandoned tickets. Count handoffs with no human reply at all. Divide by all handoffs. Compare with 33%. Split the count by channel and compare with 42% for forms, 30% for email and 13% for chat.¹
5. Read 20 "resolved" tickets. Pick them at random from tickets the AI closed. Label each one with a state from the table above. Check: count how many you could prove as answered, resolved or booked. The rest are deflected.
6. Price what you paid for. Multiply last month's billed resolutions by your unit price. Then apply your deflected share from step 5. That is your estimate of what you paid for silence.
7. Write your definition down. Put one sentence at the top of your weekly report, such as: "Resolved means the customer confirmed, or an order, refund or booking exists." Report handoffs, wait and abandoned next to it, every week.

The three most common failure modes, and the fix for each#

The audit usually surfaces the same three faults. Each one has a cause you can see in the export and a fix you can make the same week.

Failure 1: silence is counted as resolved#

A ticket that closes on a timer, after the customer stops writing, counts as an AI resolution under most billing rules. The customer may have bought elsewhere. A founder in r/micro_saas titled a September 2026 thread "We lost 56 customers after I tried to save money with AI" (240+ comments); one line in Google's snippet said to "escalate to a human when it detects the AI is stuck on a loop."⁸ A G2 reviewer wrote in September 2026 that "Fin can sometimes get stuck in feedback loops," leaving "customers feeling frustrated."⁹

Fix: Split auto-closed tickets with no last customer message into their own line, labelled "unknown". Do not add them to resolved. If your vendor bills them, ask for a dispute path.

Failure 2: the handoff lands in a queue nobody owns#

A handoff that lands in an unassigned view waits until someone happens to look. That is how a third of handoffs end with no reply. A July 2026 Trustpilot reviewer described an AI that "closed tickets without proper replies."¹⁰

Fix: Route every handoff to one named person by rule, with a backup for days off. Tell the customer a reply-by time in their time zone. Set an alert at that time. Never write "someone will be in touch."

Failure 3: the customer has to start again#

A handoff without context makes the customer repeat the whole story. Many quit instead. Check five handed-off tickets: could the person reply without scrolling the full transcript?

Fix: Add a short context note at handoff: who the customer is, what they asked in their own words, what the AI already said, what it promised, and why it handed off. The handoff contract has a template you can copy.

Rollback and the weekly health check#

Set a rollback trigger before you change anything. A reasonable trigger: abandoned handoffs above 10% of handoffs for one full week, or any money promise the AI made that you did not authorise.

1. Roll back by topic, not all at once. Find the two topics with the most abandoned handoffs. Switch the AI to draft-only or off for those topics. Leave the rest running.
2. Reopen the abandoned tickets. Reply to each one from a person. Apologise in one line, answer the question, and give a time if anything is still open.
3. Re-run steps 2 to 4 after seven days. Check that abandoned is falling and that the median wait is under your stated reply-by promise.
4. Keep the weekly line. Handoff rate, median wait, 90th-percentile wait, abandoned count, and your definition of resolved. Five numbers, one line, every Monday.

Where Valet fits#

Valet handles written inquiries for small businesses: email, website forms and listing leads forwarded to it. Every inquiry has a state, a next step and a time in the Valet Inquiry States: New, Answered, Time held, Followed up, Booked, or closed with a reason logged. Money questions, complaints, contracts and anything not in the owner's facts go to the owner with one-tap replies, and the customer is told when the owner will reply. Each reply carries a Valet receipt showing what was asked, the rule used and the sources. Valet has not published handoff or owner-reply numbers; with receipts, it could report both. To see where your own inquiries stall, start with the free lead check: forward 10 to 20 recent inquiries and see which went unanswered or stopped after one reply.