Why customers write, by marketplace: the same products, four different inboxes
Reason shares for 490 customer conversations on four UK marketplaces. Returns dominate on one, delivery on another, faults on a third. The operator shapes the inbox as much as the product does.
The reason matrix
Take every customer conversation on four UK marketplaces over 90 days, classify each one by the reason in the customer’s first message, and lay the shares out as a grid. Rows are marketplaces, columns are reasons, the tint is the share of that marketplace’s conversations. Same seller, largely the same products.
How to read it
- Marketplace A is a returns inbox. A quarter of its conversations start with “I would like to return”. The operator’s own returns flow sends the customer to the seller first, so the seller’s inbox becomes the returns desk. Two thirds of refunds wrote in first follows the same threads to the refund.
- Marketplace C is a delivery inbox. Delivery delay and item not received together are 39%. This operator sells the seller’s bulky furniture on booked two-man delivery slots, and the slot is where things go wrong. Carrier by carrier.
- Marketplace B is a quality inbox. A third of conversations report a fault. Same products as A and C. The difference is the courier’s handling and, on one range, the packaging.
The operator shapes the inbox
It is tempting to read a reason matrix as a verdict on your products. The rows say otherwise. The same sideboard produces return requests on one marketplace and fault reports on another, because each operator routes customers differently: one exposes a “contact the seller” button on the returns page, another has its own customer service team absorb order-status questions, a third ships via its own carrier contract. Before changing a product, check whether the same SKU behaves the same on a second marketplace. Usually it does not.
Using it on Monday
- Match reply templates to the row. The returns-heavy marketplace needs a returns template with the operator’s exact process; the delivery-heavy one needs a template that quotes the carrier’s tracking and the rebooking route.
- Staff the right morning. Return requests are patient; item-not-received messages are not. The delivery-heavy marketplace is where a Monday backlog turns into overdue SLAs.
- Send the faults column to operations. A 32% fault share on one marketplace with a 16% share on another for the same products is a courier or packaging conversation, not a customer-service one.
- Watch for the wrong-colour column. It is small, and it is almost always a listing image problem you can fix in an afternoon.
- Reason shares differ more by marketplace than by product.
- Each operator's routing turns the seller inbox into a returns desk, a delivery desk or a quality desk.
- Compare the same SKU across marketplaces before blaming the product.
- Templates, staffing and operations follow-ups should follow the row, not the total.
Questions people ask
What do marketplace customers contact sellers about most?
In 490 classified conversations across four UK marketplaces, the largest reasons were return requests (9–33% depending on marketplace), faulty items (16–43%), delivery delays (12–20%) and item not received (7–19%). Cancellations, missing parts and wrong colour made up the rest. The mix differs more by marketplace than by product.
How are customer messages classified by reason?
From the first customer message in each thread, into a fixed list of categories: item not received, wrong item, wrong colour, faulty item, damaged packaging, missing parts, delivery delay, cancellation, return, refund, order status, product question, other. Operator notices are excluded before classification so that system tasks do not count as customer reasons.