The Amazon 24-Hour Response Rule: How It Is Measured, What Pauses It and How to Never Miss It
)
Amazon's 24-hour response rule requires sellers to respond to every buyer message within 24 hours, including weekends and holidays, or mark it "no response needed" if no action is required. Amazon tracks compliance with this rule as a rolling percentage in Account Health, and falling below the expected rate puts your account at risk. This guide covers what counts as a response, what pauses the clock, what a pattern of misses actually costs, and how to set an internal SLA, an auto-responder and routing that keeps a team inside the rule at volume.
What the rule says, in Amazon's words
Amazon's Seller Central help states that sellers must respond to buyer messages within 24 hours, seven days a week, including weekends and holidays. Amazon tracks this as a response-time compliance rate inside Account Health, under customer service performance.
A separate late response figure sits alongside overall compliance: the share of messages that missed the 24-hour window.
Where and how buyer messages arrive, and what you are allowed to send back, is covered in our Amazon Buyer-Seller Messaging guide. This post is about the clock.
What counts as a response and what pauses the clock
A reply from the seller counts, whether or not it resolves the issue.
Marking a message "no response needed", available when a message does not require action, stops the clock without counting as a miss.
The clock runs continuously. It does not pause for a closed store, a weekend, or a holiday. It starts when the buyer sends the message, not when you see it, so a message that lands at 11.59pm on a Saturday has been running all weekend by the time a Monday inbox is opened.
Each message on an order thread carries its own clock. Only the specific message needs a reply, not the full order history.
An acknowledgement-only auto-reply can satisfy the response-time timestamp without actually answering the buyer's question. That distinction matters more than the metric suggests, and the next section explains why.
What a missed deadline costs
Consistently missing the 24-hour window puts your Account Health rating at risk, and a compliance rate hovering just above Amazon's threshold is two bad weekends from a performance warning, not a safe position.
The bigger risk runs through Order Defect Rate (ODR). Amazon expects ODR under 1%, calculated over a 60-day window from three triggers: a seller rating of 1 or 2 stars, an A-to-z Guarantee claim (counted against you whether Amazon rules for you or the buyer), and a payment chargeback. A seller doing 300 orders a month is only two or three granted claims from the line.
A slow response does not count against ODR directly, but it is usually what causes the claim. A buyer with a late or damaged package who does not hear back quickly enough goes to the order page and files a claim rather than waiting for a reply. Our guide to Amazon A-to-z claims has the full breakdown of handling a claim once it is filed, and our Amazon performance metrics guide covers ODR and the other Account Health numbers in detail.
Setting an internal SLA tighter than Amazon's
24 hours is Amazon's outer limit, not a target worth aiming for. Most sellers running this well set an internal SLA well under it, generally 8 to 12 hours for a standard buyer message, because the 24-hour clock does not distinguish between a routine question and something urgent.
A tiered SLA works better than one flat number:
A message mentioning a claim, damage, a missing item or the wrong product: treat as highest priority, under 2 hours. A buyer with this kind of problem often files a claim within minutes of not hearing back.
A standard order question: under 12 hours.
Everything else, pre-sales and general questions: inside the 24-hour ceiling, ideally same-day.
Cover weekends and holidays the same way as weekdays, since the deadline does not take a day off, and set escalation rules against the clock rather than against the calendar. A workable pattern is three graduated alerts: a reminder at 18 hours, a hand-off to a second person at 22 hours if there is still no reply, and a supervisor alert at 23 hours. By the time the deadline is close, every message has either been answered or is with someone who can answer it.
Auto-responders: what they can and cannot do
An auto-responder on Amazon sends an automatic reply the moment a buyer message arrives, before a person looks at it. Inside Amazon's messaging policy, it can acknowledge receipt, share expected reply times, and, if it pulls order data, answer straightforward questions like shipping status with the actual tracking number.
It does not stop the 24-hour clock unless what it sends actually counts as a response. A generic "we got your message" acknowledgement may satisfy the timestamp, but an unhelpful auto-reply protects the compliance number and does nothing for the risk that runs through a dissatisfied buyer filing a claim.
An auto-responder helps most as an out-of-hours acknowledgement, or as the first line on order-status questions a template can answer with live data. It hurts when it is the only response a buyer ever gets: a template that does not answer anything, sent to look responsive, loses the customer even while it clears the metric.
To set one up:
Connect Amazon to your messaging tool, whether that is Seller Central's own automation settings or a helpdesk.
Grant the messaging and order-sync permissions it needs to see order status and history.
Set the trigger conditions (order status, keywords, or hours the store is closed) and the template each trigger sends.
Write each template around the specific answer, not a placeholder. An order-status template should pull the live tracking number rather than say "we'll get back to you."
Review which templates buyers respond well to, and cut the ones that just restate the question back at them.
Auto-responders are for inbound messages. Post-order follow-up messages, including feedback requests, are a different tool with their own policy rules; see our Amazon feedback request templates for those.
Routing, templates and volume
Four things cut response time at volume, and none of them require a specific tool.
Route by order status, so a damaged-item complaint and a pre-sales question are not sitting in the same queue. Messages with words like "refund", "damaged" or "never arrived" go to a person first; a confident automated answer to an upset buyer is the fastest route to a claim.
Keep a short set of templates for the questions that repeat most (shipping delay, return started, wrong item, pre-sales sizing) and update them when a question stops matching the template. Map your incoming volume by type once a quarter; if routine questions are more than half of it, which they usually are, that is the share automation can take.
Run Amazon beside every other channel in one queue rather than several separate inboxes, so a message does not sit unseen because it landed somewhere checked less often. The most common cause of a missed deadline is not a slow agent, it is a message buried under another channel's backlog.
Work by time to breach, not oldest-first. Check, at least daily, which messages are closest to the 24-hour mark. Oldest-first misses the ones about to breach in favour of ones with hours still on the clock.
Tracking the 24-hour clock in a helpdesk
Running this inside a helpdesk puts a countdown on every Amazon message rather than a plain timestamp, so a team can see what is close to breach without checking each thread's send time by hand. Breach alerts at set intervals catch a message before it becomes a miss rather than after, and because each marketplace runs its own clock, the countdown is set per marketplace rather than one ticket age for everything.
Three things a helpdesk needs to do this properly: the order data attached to the ticket natively, so a reply can carry the live tracking number rather than a placeholder; awareness of the marketplace's clock, so escalation fires at the right hour without custom configuration; and routing that recognises the language of a buyer about to file a claim and sends that message to a person.
AI can draft or send substantive replies to order-status and shipping questions, using live tracking data rather than a placeholder acknowledgement, while anything that reads as a complaint or a claim risks routes to a person first. A report showing response-time compliance, average response time by team member and time of day, and how many messages ran close to breach catches a slipping pattern before Amazon's own Account Health report would. Run the same report against last November's volume before peak season; the setup that copes with triple the messages is the one to keep.
eDesk connects to Buyer-Seller Messaging directly through Seller Central authorisation, without a separate bridge. Our Amazon helpdesk software page has the full setup across marketplaces.
Frequently asked questions
Do I have to reply to Amazon messages within 24 hours on weekends?
Yes. The clock runs seven days a week, including weekends and holidays, and does not pause because the store is closed.
Does an auto-reply count as a response on Amazon?
It can satisfy the response-time clock if it is substantive. A generic acknowledgement may clear the timestamp but does not resolve the buyer's issue, which matters beyond the raw response-time number.
What is Amazon's late response rate?
The share of buyer messages that missed the 24-hour window, tracked alongside overall response-time compliance in Account Health.
What happens if I miss the 24-hour response window?
An occasional miss affects your compliance percentage. A pattern of misses puts your Account Health rating at risk, and slow responses are frequently what pushes a buyer to file an A-to-z claim, which affects Order Defect Rate directly.
How do I know whether my setup is working?
Watch three numbers weekly: response-time compliance in Account Health, your average response time across channels (aim for under 12 hours), and ODR (under 1%). Compliance holding while ODR climbs means issues are escalating before they reach you.
How do I track Amazon response time across a team?
A helpdesk that shows a countdown per message, alerts before a deadline is close, and reports compliance across the team catches slippage before it becomes a pattern. eDesk does this alongside every other sales channel in one queue.
Ready to stop watching the clock by hand?
Author:
)