There is no single correct reply time for support email. The right target depends on what the customer is asking, what they were told to expect, and what your team can keep up every day. This guide helps you set a target you can hit, decide which emails jump the queue, and stay responsive when you are busy.
Start with what you promised
Customers judge your speed against the expectation you set. If your contact page says you reply within one business day, a reply the next morning is on time. If it says nothing, each customer brings their own idea of fast. Publish a reply window and treat it as a commitment.
- Contact page: State your reply window and support hours
- Auto-reply: Confirm you received the message and repeat the window
Two numbers to track
One figure hides too much. Measure how long a customer waits for a human reply, and how long until the issue is closed. A fast reply that solves nothing makes the second number worse.
- Time to reply: From the customer's email to your reply
- Time to resolution: From the customer's email to the issue being closed
Not every email has the same clock
Sort by urgency, not arrival order. Some messages lose their value within hours. Others can wait until tomorrow without any harm.
| Email type | How quickly to answer |
|---|---|
| Change or cancel an order that hasn't shipped | As soon as you can, before it is fulfilled |
| Payment problem or double charge | Same day |
| Damaged or wrong item | Same day |
| Where is my order | Within your published window |
| Pre-sale product question | Quickly while the shopper is still deciding |
Set a target you can keep
A promise you miss does more damage than a slower promise you keep. Look at how many emails arrive in a normal week and how many your team can answer well in a day. Set the window with room to spare, then tighten it once you are hitting it consistently.
- ✅ Pick a window your current team can meet on a busy Monday
- ✅ Publish support hours, including weekends if you don't cover them
- ❌ Don't copy another store's promise without their staffing
- ❌ Don't count an auto-reply as a response
Get faster without getting sloppy
Speed comes from removing work, not from typing quicker. Most support volume falls into a handful of repeated questions, and each of them can be answered with the order open in front of you.
- Answer in one message: Include the tracking link, the date or the refund amount, so the customer has no reason to write back
- Keep the order in view: Check status, tracking and past refunds before you write
- Send a holding reply when you need time: Say what you are checking and when you will follow up
For the most common ticket of all, see the guide on where-is-my-order emails.
Doing this at scale
Reclaim triages each support ticket by intent, sentiment and urgency, so time-sensitive requests are easier to spot. It drafts a reply grounded in the real order, tracking and refund history, and runs in shadow, assisted or autonomous mode. Today it builds its queue from recent orders and does not connect to a helpdesk or inbox. See Reclaim.