Amazon Customer Service for Sellers Messaging Rules, Response Times and Account Health

Most advice about Amazon customer service is generic service advice with Amazon's name attached. Be empathetic, personalize the reply, respond quickly. All true, and none of it tells you that thanking a customer for their order, adding your logo, or mentioning a complementary product in the same message can get that message blocked before the buyer sees it.

The rules are narrow, and they are enforced on content rather than intent.

Amazon permits communication necessary to complete an order or provide customer service. Its guidance to sellers sets out proactive message requirements: every proactive message must include the 17-digit Order ID, be sent within 30 days of order completion, and be written in the buyer's language of preference.

Generally permitted

• Replying to a buyer inquiry about their order
• Resolving a problem with the product or delivery
• Requesting information needed to complete the order
• A neutral review or feedback request, once per order
• Scheduling delivery for large or specialized items

Prohibited

• Marketing or promotional content, including vouchers and cross-sells
• Order or shipment confirmations Amazon already sends
• Messages that only say thank you or "we're here to help"
• Language incentivizing positive reviews or offering compensation
• Requests to remove or update an existing review
• Repeat requests for a review or feedback on the same order
• External links or contact information except where specifically permitted by Amazon for order completion or another allowed purpose

Content restrictions sit on top of that list. Emojis, decorative formatting, and attachments carrying promotional material are all problems, and so is the softer stuff. "We're a small family business" is persuasive content, not service content.

This is where the standard advice goes wrong. Cross-selling inside a buyer message is marketing, and the fact that it is helpful does not exempt it. If a customer asks whether a sleeve fits their laptop, answer the question. Pointing them to your other products is a listing and advertising job, not a messaging one. Our guide to Amazon customer engagement tools covers which channels are actually built for that.

Autoresponders deserve the same scrutiny. An automated acknowledgment that adds nothing but "we received your message" sits close to the prohibited thank-you category, and it does not stop the response clock. Automation does not exempt a message from Amazon's communication rules. Whether a response is drafted manually, from a template, or with AI assistance, the final message still needs to comply with Amazon's permitted-message requirements.

Amazon expects sellers to respond to buyer messages within 24 hours. The clock does not pause for your business hours.

Weekend coverage is not optional if you receive weekend messages, which most sellers do.

Marking messages "No response needed" is for genuine non-questions, such as a buyer's out-of-office auto-reply. Using it to clear a backlog misreports your own service level and leaves real questions unanswered.

The Request a Review button does not create a response obligation, because it sends from Amazon rather than from you. It is also the safest way to request a review, since the content is Amazon's.

Speed matters beyond the response metric. For seller-fulfilled orders, Amazon notes that a buyer may become eligible to file an A-to-z Guarantee claim after 48 hours, giving sellers another reason to resolve service issues promptly.

Order Defect Rate is where service problems become account problems. Amazon's policy is that sellers maintain an ODR under 1% in order to sell in the Amazon store, and a rate above 1% may result in a restriction of selling privileges.

Three components make up ODR: negative feedback rate, A-to-z Guarantee claim rate, and credit card chargeback rate. An order with more than one defect counts once.

The claims detail is where sellers get surprised, because not every claim counts and the categories are more specific than most guides suggest.

Two details worth holding on to. Amazon states that if a claim decision is reversed on appeal and you are found not to be at fault, the claim is removed from your ODR. And under Amazon's Buy Shipping protection, if you purchase Buy Shipping and ship on time, claims where a customer reports a delivery problem do not affect your ODR, though you remain responsible for the financial loss.

A buyer-withdrawn claim can be a favorable outcome, because Amazon's ODR guidance excludes qualifying withdrawn claims from the metric. The goal, however, should be to resolve the underlying customer issue rather than pressure a buyer to withdraw a claim.

Amazon publishes the measurement window, so there is no need to guess at it. ODR covers all orders with one or more defects as a percentage of total orders over a given 60-day period, and the window rolls forward. One detail inside that calculation catches people out: the negative feedback component is order-correlated, which means Amazon looks at the date the order was placed rather than the date the feedback arrived. A defect leaves your metric when the order date falls outside the 60-day window, not 60 days after the complaint. Additional defect-free orders can also reduce the percentage. Check Account Health for your current metric and the exact dates of your window rather than estimating recovery from order volume alone. Our account health guide covers how the other metrics interact.

You cannot have honest negative feedback removed. You can have feedback struck when it breaks Amazon's rules, and sellers routinely leave eligible strikes on the table because nobody checks.

Request removal through Feedback Manager, using the Request removal action next to the Order ID in the Recent Feedback table. Amazon may remove eligible feedback or strike it through in certain fulfillment-related cases when:

• The comment is a product review rather than feedback about the transaction
• It concerns fulfillment or customer service for an order Amazon fulfilled
• It contains obscene language
• It includes personally identifiable information

If a buyer withdraws feedback themselves, Amazon's guidance says it is not counted as part of ODR.

Do not ask buyers to remove or change product reviews. That request is prohibited in Buyer-Seller Messaging, as is encouraging buyers to send complaints to you privately instead of posting them. For seller feedback, use Feedback Manager when the comment qualifies for Amazon's removal or strike-through criteria. Resolve the buyer's underlying problem without offering compensation, incentives, or conditioning a resolution on changing public feedback.

When a claim arrives, you usually have a window to respond before Amazon decides. Use it properly.

Respond with evidence, not argument. Tracking, delivery confirmation, and message history showing what you offered and when.

Resolve directly where the claim is valid. A prompt resolution can prevent a service problem from escalating further and may reduce the account-health consequences associated with an unresolved dispute.

Answer within Amazon's stated window. No response means Amazon decides on what it has, which is the buyer's account of events.

Keep the message history clean. Your messaging record is the evidence. A thread showing a prompt, compliant, helpful response is worth more than anything you write in the claim form.

Which of those four fall to you depends on how the order was fulfilled. For FBA orders, Amazon handles many issues tied specifically to fulfillment and delivery. Seller responsibilities can still remain for matters such as product quality, listing accuracy, authenticity, and other seller-controlled issues, and those are the claims where your own evidence and your own response window decide the outcome.

Templates, stripped. Build templates for your recurring questions, then remove everything Amazon does not allow: logos, links, signatures with contact details, "please leave five stars," emojis, and thank-you-only messages. Review them annually, because compliance problems often come from templates written years ago that nobody revisited.

Coverage, not heroics. Decide who answers on Saturday before Saturday. The 24-hour expectation runs whether or not someone is at a desk.

Documentation. Keep records of every interaction. In a claim or a chargeback, the message history is your case.

Fix the listing when the same question repeats. Ten identical questions about dimensions is a listing problem wearing a customer service costume, and the fix removes both the messages and the returns behind them. Our guide to review and return analysis covers how to tag the themes and route them.

CMO operating rule: treat every message as evidence, not conversation. Before anything is sent, we ask whether it would read well in a claim review, because that is where it may end up. The habit removes the marketing instinct that gets messages blocked, and it makes the thread useful when a claim or chargeback arrives.

[EXAMPLE SLOT, OPEN. Holding for one real anonymized claim that turned on the message history: what the buyer claimed, what the thread showed, how it was decided. Drops in here directly beneath the rule. Do not publish filler in this slot and do not quietly delete it, the rule above is weaker without it. ]