Duck Float
All posts
6 min read

How long a customer will wait for a reply (and how not to lose them meanwhile)

Speed of reply is something a customer feels before they judge the quality of the reply itself. A person writes and stares at the screen: seconds of silence stretch out, and a few hours of nothing easily turn an interested customer into one who has already gone to a competitor. That's why first response time (FRT) is one of the few support metrics worth tracking even for the smallest team. In this article we'll cover what this metric actually is, how long customers really wait depending on the channel, why reaction speed affects revenue, and a few simple steps that can cut waiting time starting this week.

What first response time is

First response time is the gap between when a customer reaches out and when they get their first human reaction. Importantly, it's the first reply, not the full resolution. Customers will wait for a hard problem to be solved — they won't wait to simply be noticed.

For example, a customer writes in the chat at 2:05 pm asking about account access. If an agent replies at 2:07 pm with "Looking into it, one moment" — the first response time is two minutes, even if the actual issue only gets resolved at 2:20 pm. That short reply already gave the customer the one thing that matters: they've been seen and someone is on it. Without it, those same fourteen minutes of silence would read as indifference rather than work in progress.

That's why FRT and full resolution time are two different metrics, and it's worth not confusing them. You can have a great first-contact resolution rate and still lose customers because the very first reaction arrives too late.

How long customers will actually wait

Expectations depend on the channel — and this is the key thing to account for:

  • Website chat. Expectations are highest here: people use chat precisely because they want an answer now. Minutes, not hours. Often this customer is already close to placing an order or making a decision — they see an "online" indicator, so silence in return reads as a flat refusal to help.
  • Messengers (Telegram). People are used to near-instant conversation, so a few minutes is fine, while a few hours already feels slow. It's the same format people use to chat with friends, and a brand that stays quiet for hours gets subconsciously compared not to other companies, but to a friend who "read it and didn't reply."
  • Email. Patience is greatest here: a reply within a few hours is usually acceptable, but even here a full day of silence is rarely forgiven. Email is still seen as the channel for questions that need time to sort out, so customers consciously budget for a pause.

The general rule is simple: the more "live" the channel, the less time you have. If you put a chat on your site, you automatically take on the obligation to reply fast — otherwise it hurts more than it helps.

Picture an online store running a separate Telegram account for shipping questions. If the average reply there takes twenty minutes, customers perceive the brand as inattentive, even if email is handled flawlessly in the meantime. Each channel runs on its own clock of expectations, which is exactly why channels can't be left on "autopilot" without a clear sense of who answers them and how fast.

Why this affects money

A fast first reply works on two fronts at once. During the sale it lifts conversion: a customer who gets an answer while still considering the purchase is far more likely to follow through. During retention it lowers churn: the feeling of "I'm being heard" is one of the main reasons customers stay. Slow support quietly eats away at both, even if the answers themselves are flawless.

Picture two customers who wrote in this week with the same question: "Will your product work for our case?" The first got a reply in five minutes, with a clarifying note and a link to a relevant example — and signed up for trial access that same day. The second got a reply the next morning, by which point their interest had cooled and a competitor's tab was already open. The question and the answer were nearly identical — timing made the difference.

There's another effect that's often overlooked: the first reply sets the expectation for every conversation that follows. If a customer gets a fast reaction at the start, they also trust that harder questions will be handled on time. If the first contact drags on, every following message they send carries a bit of anxiety — and it shows even in the tone of what they write.

Common mistakes that slow down the first reply

Most of the time the problem isn't that the team works slowly — it's how requests are organized:

  • Multiple channels with no clear owner. Email, a website form, Telegram — and nobody is quite sure who's watching each one right now.
  • Checking each channel manually, one by one. By the time someone opens email, then Telegram, then remembers to check the website form, tens of minutes have passed before a message is even read.
  • Holding off until there's a "full" answer. An agent stays quiet until they have the final solution, instead of immediately writing "I see your question, looking into it."
  • No real-time notifications. New requests only get noticed when someone happens to check.
  • One agent as the single point of entry. When they're busy, on leave, or offline, every new request simply waits with no backup plan.

None of these causes need heroic effort to fix — just a small rearrangement of the process.

How to speed up the first reply

A few levers that work even in a small team:

  • One place for all requests. Half of delays aren't slowness — just a missed message in one of the channels. See the piece on scattered requests.
  • Templates for common questions, so you don't retype the same thing every time. For more on building templates that still feel personal, see the piece on reply templates.
  • Live notifications that arrive instantly, not whenever you decide to check email.
  • A ready draft reply that you only need to review and send, instead of writing from scratch.
  • A clear rule for who replies first. Once a team has more than one person, it matters that a message doesn't sit unanswered because each agent assumes someone else will handle it.

A quick checklist for this week: confirm every channel feeds into one place; agree with the team on who answers first at each hour of the day; prepare three or four templates for the most common questions; turn on notifications anywhere they're still missing.

How to tell if you have a first-response problem

You don't need special reports to gauge the situation. Once a week, look at a handful of recent tickets and compare the time of the customer's first message against the time of the first reply — since every request in the system keeps its history, status, tags, and source, this takes a few minutes.

Ask the team directly: were there any moments this week when a request sat unanswered for an hour or more? If the same tag like "awaiting reply" keeps sitting there for a long time, that's a sign to revisit the process, not to blame a single person.

Where Duck Float fits in

We built Duck Float around speed. New messages from Telegram, the widget, and the API arrive in one inbox instantly, no refreshes, and every request immediately becomes a ticket with its own history, status, tags, and source — so nothing gets lost between channels. AI prepares a draft reply in the customer's language while the agent is still reading the request: the draft appears right in the reply field, and pressing Tab is enough to accept it, edit it, or write your own — nothing is ever sent automatically. The result is that a typical reply takes seconds — more on that in the article on faster replies. Duck Float is free during the beta; if you want to try it, message us through the widget on this site.

Try Duck Float with your team

Free while in beta. Setup takes a few minutes.

Create an account