First response time is one of the first numbers every e-commerce founder learns to track. It’s simple to measure, easy to put on a dashboard and feels like a direct reflection of how much you care about customers.
It’s also one of the most misunderstood metrics in support. Getting it right isn’t about chasing the lowest possible number. It’s about setting the right target for each channel and making sure a fast first response actually leads somewhere.
What first response time actually measures
First response time is the gap between when a customer contacts you and when they get a reply. It doesn’t measure whether the problem was solved, whether the answer was correct or whether the customer had to write back three more times.
That distinction matters, because it’s very easy to improve first response time without improving anything else. An automatic “We’ve received your message” email technically counts as a response in some help desks. Customers don’t see it that way.
Targets by channel
Customer expectations vary a lot depending on how they reach you. Reasonable targets for a growing online store look roughly like this.
Live chat:
Under two minutes. If someone opens a chat window, they expect a conversation, not a wait. If you can’t staff chat to that level, it’s better to set clear hours or route chat to email than to leave people staring at a typing indicator.
Social media messages:
Within an hour during business hours. Social replies are often semi-public, and slow responses can be visible to other customers.
Email and contact forms:
Within a few hours, and ideally the same business day. Next-day replies are acceptable for smaller brands, but customers increasingly compare you to the fastest store they’ve bought from, not the average.
Phone:
Under a few minutes of hold time. Long holds create more frustration than almost any other channel.
These aren’t fixed rules. A high-end furniture brand with long delivery windows will face different expectations than a fast-fashion store shipping thousands of orders a day. But they’re a sensible starting point.
Why faster isn’t always better
A five-second reply that doesn’t help is worse than a five-minute reply that does.
Many stores now use AI to answer tickets instantly, and for routine questions such as order status, return windows or shipping options, that can be excellent. But speed without accuracy backfires.
In a May 2026 survey of 1,000 U.S. consumers that Kim cc conducted through Critical Mix’s kNOW panel, about half of AI-resolved tickets were reopened. Each reopened ticket means the customer waited twice and trusted you a little less the second time.
The goal is a fast response that’s also right.
Pair first response time with resolution metrics
To get a true picture, track first response time alongside a few other numbers.
Full resolution time shows how long it takes to actually solve the problem, not just acknowledge it.
Reopen rate shows how often customers have to come back because the first answer didn’t work.
Customer satisfaction by ticket type shows whether speed is translating into happy customers, or whether certain categories, such as refunds or damaged orders, are dragging scores down.
If first response time improves while reopen rates climb, you’ve made support faster on paper and worse in practice. Treating response time as one input to a broader customer-service strategy, rather than the goal itself, is what keeps that from happening.
How to bring first response time down the right way
Separate routine tickets from complex ones. Simple, repetitive questions can be answered instantly, either with well-built AI or saved replies. Complex issues should go straight to an experienced person rather than waiting in a general queue.
Let AI judge its own confidence. The most reliable AI support setups score how sure they are about each answer. High-confidence replies go out immediately. Uncertain ones are routed to a human for review. That keeps speed high without sending confident-sounding wrong answers. This confidence-based split is exactly what Kim cc runs on: AI answers the high-confidence routine tickets in seconds, while uncertain ones route to a human before they’re sent.
Staff for your busiest hours. Look at when tickets actually arrive. Many stores see spikes in the evening and on weekends, when shoppers are browsing and their teams are offline.
Fix the causes of common tickets. If “Where is my order?” makes up a large share of volume, better tracking emails and clearer delivery estimates at checkout can lower ticket volume and response times at the same time.
Always offer a path to a person. Fast AI responses work best when customers know they can reach a human if they need one. Hiding that option undermines whatever goodwill speed creates.
Conclusion
A good first response time for an online store is minutes on live chat, an hour or less on social and the same business day on email. But the number only matters if the response that follows actually helps.
Measure how quickly you reply, but judge your support by how quickly customers get their problem solved and whether they’d come back to buy again.
