What counts as a good response time, and why it matters less than you think

The benchmark question everyone asks

"What's a good response time" is one of the most common questions in support, and the honest answer depends on the channel. Under a minute for live chat is the modern expectation, mostly because chat implies someone is there right now. Email doesn't carry that expectation, so a few hours is still considered solid, and replying the same day is acceptable for anything less urgent.

A rough breakdown that holds up across most industries: live chat under a minute is excellent, under five minutes is fine, and anything past that starts to feel slow for a channel built around immediacy. Email under an hour is great, under four hours is normal, and past a day starts costing you goodwill. Social replies sit closer to chat than email, since customers there expect public visibility.

You can plug your own number into the response time grader if you want a quick read on where you land.

Why speed alone isn't the whole story

Here's the part that gets missed: a fast, wrong answer is worse than a slower, right one. Answering in thirty seconds with something that doesn't solve the problem just starts a longer back and forth, and the customer's actual wait time, until their problem is solved, ends up longer than if you'd taken five extra minutes to get it right the first time.

Support teams that fixate on how quickly they reply sometimes end up optimizing for the wrong thing, answering fast and marking a ticket handled without checking whether the problem actually went away. Time to resolution is the number that actually tracks with whether a customer sticks around, and it's a less flattering metric to put on a dashboard, which might be part of why it gets less attention than it should.

Speed gets a customer's attention. Getting the answer right is what keeps them. The setups that help most make both easier at the same time, instead of trading one for the other.