First response time in ecommerce support: what to measure

What it measures

The time between a customer's first message and the first human reply that contains an answer. Two words carry the weight there:

• Human. An autoresponder saying "we got your message" is not a first response. Counting it makes the number look great and changes nothing for the customer.
• Answer. "Looking into this" is a holding message. Sometimes necessary, but it should not reset the clock.

Median, not average

Averages are wrecked by outliers. One ticket that sat over a bank holiday weekend can drag a month's average up by hours while the typical customer waited twenty minutes.

Track the median for the typical experience, and the 90th percentile for the tail. The gap between them is the interesting part: a median of 30 minutes with a 90th percentile of 3 days means most people are fine and a specific group is being badly failed. Find out which group.

Business hours or wall clock

Both, and know which you are quoting. Business-hours FRT tells you whether your process works. Wall-clock FRT tells you what the customer actually experienced. A store with a 2-hour business-hours FRT that only works weekdays gives a Friday-evening customer a 60-hour wait, and only one of those numbers reflects that.

What target is reasonable

Published benchmarks vary enormously and are mostly drawn from companies unlike yours, so use them for direction rather than as a goal. A more useful framing:

• Under an hour in business hours is genuinely fast and noticeable to customers.
• Same business day is fine for most Shopify stores and rarely generates complaints.
• Over 24 hours starts producing chase emails, which increases your volume and makes the next number worse.

That last point is the one worth internalising. Slow first responses generate additional tickets, so FRT is partly self-inflicted.

What actually moves it

In rough order of effect for a small Shopify team:

1. Remove the lookup. If most tickets are order questions and each needs a Shopify visit, that lookup is most of your handling time. Removing it compounds across the whole queue.
2. Scenario templates, not topic templates. Choosing between eight named situations is faster and more accurate than adapting one generic reply.
3. Clear the inbox at a fixed time. Twice a day at set hours beats "whenever there is a gap", because the gap never comes.
4. Cut the volume upstream. Better shipping notifications reduce WISMO, which is the biggest single category for most stores.
5. Stop measuring what you will not act on. Two numbers you check monthly beat a dashboard nobody opens.

The metric nobody tracks but should

Replies per resolved conversation. If a typical order question takes 3.4 messages to resolve, your first reply is not answering it. Usually that means it lacks a specific status, a date, or a next step — the customer writes back to ask for the thing you left out.

Getting that number closer to 1.5 reduces total volume more reliably than speeding up individual replies, and it is a better use of attention than shaving minutes off FRT.