Why this varies more than sellers expect

Each marketplace sets its own buyer-message response-time expectation, and treats missing it differently — some fold it into a broader account health metric, others enforce it more informally through customer satisfaction scores. Running multiple marketplaces without knowing each platform's specific number is one of the more common gaps in an otherwise well-run operation. A seller who's diligent about shipping SLAs and inventory accuracy can still take an account health hit purely from an under-monitored message inbox on a secondary channel.

The general pattern

Most major marketplaces (Amazon, Walmart, eBay) expect a response to buyer messages within 24 hours, with some treating weekends/holidays as included in that window and others allowing exceptions. Etsy's culture leans toward faster, more personal responses given its relationship-driven buyer base, though it doesn't enforce as strict a formal SLA as Amazon's account health system does. TikTok Shop, being newer, has been tightening its response-time expectations as the platform matures — sellers should check current requirements directly rather than assume a number.

Beyond the headline response-time number, most platforms also expect:

  • Resolution, not just acknowledgment. A quick "we've received your message" reply that never actually resolves the underlying issue still leaves an unhappy buyer, and can still generate a negative review or dispute even though you technically hit the response-time clock.
  • Consistency across message types. Order-status questions, return requests, and product questions often route through different inboxes or ticket types on the same platform — a strong response time on one type doesn't offset a slow one on another if the platform (or the buyer) is tracking them separately.
  • Tone and outcome, evaluated together. A handful of platforms explicitly factor buyer-reported satisfaction with the resolution, not just the speed of the reply, into seller standing — meaning a fast but unhelpful response can score worse than a slightly slower one that actually solves the problem.

Why this feeds directly into account health

On marketplaces that track response time as a formal metric (see Account Health Metrics Compared), a pattern of slow responses can affect account standing independent of your actual product or shipping quality — meaning strong operations elsewhere can't fully offset weak message responsiveness. This is a common blind spot for sellers who are otherwise diligent: it's easy to monitor orders and inventory daily while checking a buyer-message inbox only sporadically, especially on a channel that isn't your primary sales driver.

What counts as a "response" varies too

An automated acknowledgment reply satisfies the response-time clock on some platforms but not others — some systems only count a substantive, human (or clearly resolving) reply as meeting the SLA. Don't assume an autoresponder alone protects your metric on every platform; verify what specifically counts as "responded" in your current seller dashboard documentation for each marketplace you operate on.

Setting up for consistent response times

A single, centralized inbox pulling in messages from every marketplace you sell on (see Customer Service Automation and Helpdesk Tools) prevents the common failure mode of a marketplace-specific inbox going unchecked simply because it isn't the seller's primary platform. Beyond centralizing, a few habits keep response times consistent even as volume grows:

  • Set a fixed number of daily inbox checks (e.g., morning, midday, end of day) rather than an ad hoc "whenever I remember" approach — this alone catches the majority of SLA misses caused by simple inattention.
  • Flag or tag by urgency, not just by arrival time — a shipping-delay complaint from an already-frustrated buyer deserves faster handling than a routine pre-sale product question, even if the product question arrived first.
  • Build a response-time dashboard or simple tracking sheet if your marketplaces don't surface the metric clearly on their own, so you catch a slipping average before it becomes a account-health-visible pattern.

Building this into a documented policy as you grow

Once you're handling enough message volume that you personally can't be the only person monitoring it, formalize the expectation into a written internal SLA — see the Customer Service SLA Template — so a new hire or contractor has a clear, specific standard to work against instead of an unwritten norm only you carry in your head.