Response Times for Messages vs Calls: Setting Fair Targets
How quickly should you answer a message compared with a call? Learn to set realistic targets for each channel, measure them and communicate them to customers.
A ringing phone demands an answer now. A message can wait, but not forever. The challenge for any team that offers both is deciding how long is fair for each, so customers are not left guessing and agents are not torn between the two. Without clear targets, the phone wins every time, and messages wait until someone has a spare moment.

This guide helps you set targets for calls, chat, email and other messages, measure them in a way that means something and tell customers what to expect. For the wider set of measures behind it, see The Call Center KPI List.
Why channels need different targets
The channel shapes the expectation. On a phone call, a customer is waiting in real time, so every second of ringing or hold is felt. In live chat, customers expect replies within a minute or two, because it feels like a conversation. Messaging apps are in between: people expect speed but accept gaps. Email is the slowest, and customers usually allow hours, sometimes a working day.
How expectations differ
| Calls | Messages and email | |
|---|---|---|
| Pace | Real time; both people are present. | Asynchronous; replies can come later. |
| Tolerance | Short; a few rings and a short wait. | Longer, though depends on channel and urgency. |
| What counts | Time to answer and time on hold. | Time to first reply and time to resolve. |
| Risk if slow | Caller hangs up and may not call back. | Customer sends a chaser or switches channel. |
These differences are expectations, not laws. Your own customers may be more or less patient, which is why you should ask them and check your history rather than copy an outside figure. Service Level 80/20 is one well-known approach for calls.
Define what you are measuring
Before setting a target, agree what the clock measures. "Response time" can mean several things, and a vague definition lets the number look better than the experience.
| Measure | Starts when | Stops when |
|---|---|---|
| Time to answer (calls) | The call reaches your system. | An agent picks up. |
| First response (messages) | The customer message arrives. | A human sends a real reply. |
| Time to resolution | The first contact arrives. | The case is closed. |
| Time between replies | The customer answers. | The agent replies again. |
Decide whether an automatic acknowledgement counts as a first response. For most teams it should not, because it tells the customer nothing new. Decide, too, how to treat messages that arrive outside opening hours: usually the clock starts when the team next opens, which you should state.
Set realistic targets
Start from what customers need, then check it against what your team can deliver. Look at your recent history: how long did replies actually take, and when were customers unhappy? Set a target slightly better than your typical result, meet it consistently and tighten it over time.
Setting a target for a channel
- AskFind out what customers expect, from surveys, complaints and conversations.
- MeasureRecord how long replies take now, by hour and by day.
- SetChoose a target you can meet reliably, with a separate figure for urgent matters.
- StaffPlan the rota so the target is possible at the busiest times.
- PublishTell customers, and review after a month.
Staffing is the hard part. Messages and calls often peak at different times, so one person may handle both in quiet periods. Forecasting Call Volume and Shift Planning Basics help you plan.
Tell customers what to expect
A response time is part of the service you promise. Put it where customers look: on the contact page, in the auto-reply and in the chat window. Be specific: "We usually reply to email within one working day" is useful; "We reply as soon as possible" is not. After hours, say when you will be back.
An automatic reply should confirm receipt, give the expected time and offer a route for urgent matters. Auto-Replies That Don't Annoy Customers covers wording. If your target slips, say so; an honest delay is better than silence.
Measure honestly and look beyond averages
An average hides the customers who waited longest. Report the share answered within the target, and look at the slowest cases too. Break the numbers down by hour and day to see where the problem lies. A reply time that is fine overall but poor on Monday morning means the Monday rota needs attention.
- Track first response and resolution separately.
- Count only human replies as first responses.
- Look at the worst cases as well as the typical ones.
- Check for gaming, such as sending a quick "looking into it" to stop the clock.
- Review customer feedback alongside the numbers.
A fast reply that does not solve the problem is not a success. Pair the response measures with resolution and satisfaction, and look at First Call Resolution for the phone equivalent.
Balance calls and messages in the same team
When one team handles both, calls usually take priority because someone is waiting live. That is fair, but if it is not managed, messages become an afterthought. A few approaches help: set aside blocks of time for messages, assign a person to watch the message queue at peak hours or let agents switch between them as volume demands. Whatever you choose, make the rule explicit, so agents do not have to guess.
Response-time checklist
- A defined start and stop for each measure
- Separate targets for calls, chat and email
- A faster route for urgent matters
- Targets published on the website and in auto-replies
- Rota matches the busiest times for each channel
- Monthly review of results and customer feedback
Plan for peaks and for the unexpected
Targets are easy to meet on a quiet Tuesday. They are tested by a product launch, a bank holiday, a service outage or a sudden storm of messages. Decide in advance what happens when volume doubles: which channel gets priority, who can be pulled in from other work, which messages can be answered with a standard notice and how to tell customers that replies will be slower. A calm, honest notice at the top of the contact page does more for goodwill than a silent backlog.
After each peak, look at what actually happened. How long did the longest wait last? Which targets were missed, and for how long? Use the answers to adjust your plan rather than to assign blame. Teams that review peaks learn quickly; teams that ignore them repeat the same bad week.
Response times in Call
In Call, the Inbox shows counts for the conversations in the current view, including how many are waiting on you, how many are past the first-response target and how many are unassigned, so overdue messages stand out. Conversations can be filtered by view, by channel and by owner. For calls, queues have service targets, and Reports show when calls arrive, calls by interval, agent performance and a service level projection. Callers who have waited too long on a queue can be offered a message or chat instead of waiting, and a report shows how many took the offer and how long they had waited when it was made.
Frequently asked questions
How fast should I reply to an email?
Many teams aim for the same working day, but it depends on your customers and your capacity. State a target you can meet and publish it.
Should chat be faster than email?
Usually yes. Chat feels like a conversation, so customers expect replies in minutes. If you cannot staff that, consider a slower channel or a clearly signposted delay.
Does an automatic reply count as a response?
Most teams do not count it. It confirms receipt but does not give the customer anything new. Count the first human reply.
How do I handle messages that arrive at night?
Say when you will reply, start the clock when the team opens and offer a route for urgent matters.
Is a fast reply always good?
No. A quick reply that does not help leads to more contact. Track resolution and satisfaction alongside speed.
What should I do if I keep missing my target?
Check whether the target is realistic, look at the busiest hours and adjust the rota. If that does not work, loosen the target and tell customers.