A professional email response time is the one you have promised and can keep. For a client team that means a first reply within one working day on email, faster on WhatsApp, with the full answer following when it is ready.
Below: the definitions that separate first response time from response time and resolution time, two published benchmarks with their sources, and a policy paragraph you can adopt today. Then how to track the number in Gmail and Outlook, and which tools report it.
Measure first response time (client message to first reply), response time (every reply) and resolution time (first message to close). Report the median and the p90, never the mean alone. A workable client-team policy: first response within one working day on email, two working hours on WhatsApp, and a human acknowledgment within the hour on anything marked urgent. Gmail and Outlook have no built-in response time report, so tracking needs an export or a tool.
What is a professional email response time?
The answer depends on who is writing and what they expect, so the useful version of the question is: what have you told the client to expect? A client who was told at kickoff that you reply within one working day experiences a 20-hour reply as normal. A client who was told nothing experiences the same 20 hours as being ignored, because their reference point is their own phone.
Two published surveys give a sense of the gap between expectation and practice, both checked in October 2026. Toister Performance Solutions surveyed more than 3,200 consumers in March 2020 and found that replying within one hour meets the expectations of 88 percent of them.
SuperOffice's customer service benchmark report tested 1,000 companies by sending each a customer service email. The average response time among those that replied was 12 hours and 10 minutes, and 62 percent did not reply at all. Both measured consumer-facing support, where the writer is a stranger. Numbers for named-client work are yours to set, which is what the policy section is for.
First response time, response time and resolution time
| Term | What it measures | Starts | Stops |
|---|---|---|---|
| First response time | How long a new message from the other side waited for any reply from your team | The client's message arrives | The first reply from your side is sent |
| Response time | How long each reply took, across the whole conversation | Each message from the other side | Your next reply to it |
| Resolution time | How long the whole matter took | The first message in the thread | The thread is closed or the last reply is sent |
| Median and p90 | The typical case and the slow tail | Half of replies were faster than the median | Nine in ten were faster than the p90 |
The last row matters more than it looks. An average first response time of four hours can hide a client who waited three days, because a hundred ten-minute replies pull the mean down. The median tells you the typical experience. The p90 tells you what the unlucky tenth of your clients lived through, and that is the number that decides renewals. Report both, and treat the p90 as the policy number.
Two more definitions keep the numbers honest. Business hours: a message that arrives Friday at 6pm and gets a reply Monday at 9am took 15 minutes in business hours and 63 hours on the clock. Decide which one your policy uses and say so. And auto-replies do not count as a first response. An acknowledgment sent by a person does.
What a reasonable response time policy looks like by channel
A policy for a client team sets a first response target per channel, says what counts as a response, and names the exceptions. The targets below are a starting point for agencies, consultancies and account teams. Tighten them where the contract says so.
| Channel | First response | Full answer | Notes |
|---|---|---|---|
| Email from a client | Within one working day | Within three working days, or by a date given in the first reply | The first reply can be an acknowledgment with a date |
| Email the client marked urgent | Within one working hour | Same day where possible | Define urgent at kickoff so the word keeps its meaning |
| WhatsApp Business | Within two working hours | Same day | The channel sets the expectation; a one-line acknowledgment counts |
| Shared or team mailbox | Within half a working day | As for email | Somebody has to own it, or the target belongs to nobody |
| Internal email | Within two working days | As agreed | Colleagues read silence differently from clients, but not by much |
| Out of hours | Next working morning | As for email | Say this in the signature or the auto-reply so nobody waits |
How to write the response time policy
One paragraph, written in the client's language, shared at kickoff and repeated in the working agreement. It states the target, what counts, the hours, and what to do when something is urgent. Here is a version to adapt.
We reply to every email from you within one working day, Monday to Friday, 9 to 6 in your time zone. The first reply may be a short acknowledgment with a date for the full answer, and we keep that date. On WhatsApp we reply within two working hours. If something cannot wait, put URGENT in the subject line or call Jordan on the number below, and you will hear from a person within the hour. If we miss any of these, tell us, and we will say what went wrong.
Internally, add two lines the client does not see: who covers each inbox when its owner is out, and the number you measure yourself against. That number should be the p90, because the policy is a promise to every client, including the unlucky tenth.
How to track email response time in Gmail and Outlook
Neither Gmail nor Outlook has a built-in response time report. Gmail's Nudges (Settings, See all settings, General, Nudges) surface sent messages with no reply and received messages you have not answered, one person at a time, with no numbers. In Outlook the equivalent is flagging a message with Follow Up and Add Reminder.
The Microsoft 365 admin center's Email activity report (Reports, Usage, Exchange, Email activity) lists send, receive and read actions per user and nothing about reply time. Checked October 2026. So people build it, in one of four ways.
- Export and compute. Pull message headers for a mailbox (Google Takeout or the Gmail API for Gmail; Power Query or an Outlook export for Microsoft 365), pair each inbound message with the first outbound reply in the same thread, subtract the timestamps, and take the median and p90 in a spreadsheet. It works for one mailbox at a time and goes stale the day it is built.
- Script it. A Google Apps Script on a schedule, or a Power Automate flow, writes thread timestamps to a sheet. It needs someone to own it, and it breaks when the thread structure does something unexpected, such as a reply with a changed subject.
- Sample by hand. Once a month, pick 30 client threads and time them. Cheap, and it finds the slow tail only if the sample happens to include it.
- Use a tool that reads the mailbox. Shared inbox tools and help desks report first response time because the thread timestamps are data they already hold. This is the only approach that reports per teammate and per client without maintenance.
Tools that report email response time
Help desks and shared inbox tools built around a support queue report first response time per agent and per inbox. Some add SLA rules that flag a thread before it breaches. The report is scoped to the queue: it answers how fast the team was, with no per-client view and no record of what the fast reply promised. Several put the reporting on a higher tier.
Our comparison pages set each of the main ones against Sektra on this point. Whatever you look at, check three things: whether the report uses averages or percentiles, whether it respects business hours, and whether it can report per client rather than per queue. A client team needs the per-client view, because the question is never how fast the team is on average. It is how long Northwind waited.
Where Sektra fits
We build Sektra, a shared inbox that syncs with Gmail, Outlook, IMAP and WhatsApp Business, and its analytics are built around the definitions above. First response, response and resolution time are reported as p50 and p90 for each teammate, inbox and client, on email and WhatsApp alike, over any date range.
Reply coverage shows the share of client messages that got a reply at all. Commitments made, met and overdue sit next to the timing numbers, because a fast reply that promises Thursday and misses it is the slower outcome.
Every metric has a plain-language definition and a worked example behind it. How the analytics are calculated is written down so a client can be shown the method. A daily one-sentence read says what the numbers mean. The per-client p90 is the number for customer success teams to put in the quarterly review, and the product page covers the rest.
There is a longer argument for why reply speed on its own is the wrong metric for account teams. The short version is that it is necessary and insufficient, which is why the commitments sit beside it.
A response time policy is a promise about the worst case. Measure the worst case, and the promise means something.
