If you run your own shop, customer support is a conversation between two people: the customer and you. You set the tone, you decide how fast to answer, you pick the words. If you get it wrong, you lose that customer.

The moment you sell through a marketplace, a third party sits in every conversation. It is the marketplace operator, and it is not neutral. It holds the money, it grades your answers, and it can quietly stop showing your products. Most helpdesk software was designed for the first situation. It gets used for the second, and that is where sellers get hurt.

Here is what actually changes.

There are three parties in the thread, not two

On a Mirakl-powered marketplace (Leroy Merlin, Carrefour, MediaMarkt, Worten, and dozens more run on it) a customer message is not sent to you. It is sent to the marketplace, which shows it to you. The operator can read it, can reply in the same thread, and often does: “Dear seller, please answer the customer within 24 hours.” When you reply, you choose who receives it: the customer, the operator, or both.

That choice matters more than it looks. A reply to the operator that the customer never sees does not count as answering the customer. A reply to the customer that leaves the operator’s question hanging leaves you marked as unresponsive on their side. Generic helpdesks do not have a “to whom” on the reply box because in a two-party world there is nothing to choose.

Amazon is different again. There is no message thread in an API you can plug into. Buyer messages arrive as emails from an anonymised address, with rules about what you may put in a reply (no links to your own site, no marketing), and a 24-hour clock that Amazon measures whether or not you noticed the email.

The clock is not yours

In your own shop, response time is a customer-satisfaction metric. On a marketplace it is an account-health metric. Mirakl operators show each seller a response-time figure and set a target. Amazon tracks the share of buyer messages answered within 24 hours. Fall behind and the consequences are not a bad review but a worse Buy Box position, a warning, or a suspended account.

The practical difference is where “overdue” comes from. It is not a rule you set in your helpdesk to keep yourself honest. It is a deadline the marketplace already started counting when the message landed, including Saturday evening. A support queue for marketplace sellers has to sort by time left, not by time received. Those are not the same list.

Every thread is about an order, and the order lives elsewhere

Shop support has questions about products, shipping options, sizes. Marketplace support is overwhelmingly about a specific order: where it is, why it hasn’t arrived, how to return it, whether the refund went through. The order is the unit of work.

But the order does not live in your helpdesk. It lives in the marketplace, and the parcel lives with the carrier. A refund is not something you type into a reply. It is an action on the marketplace that has states (which lines, how much, whether it has already been partially refunded) and consequences (the operator sees it, the customer is notified by the marketplace, not by you).

So a useful support tool for marketplaces has to read the order live before it lets you say anything about it, and it has to execute the refund where the refund actually happens, with a confirmation step, because that action moves money and cannot be undone.

Your customers write in languages you do not speak

Sell on Amazon.de, Leroy Merlin France and Worten Portugal from a warehouse in Spain, and in one morning you will read German, French and Portuguese, and be expected to answer in each. Translation software exists, but customer support translation has a specific failure mode that general translation does not care about: a translated reply that changes an order number, drops a tracking code, or comes back in the wrong language is worse than no reply at all.

We have watched a translation model return a Spanish reply for a Bulgarian customer and call it done. That is why any translation that goes out to a customer needs a check, not just a model: same references in and out, the right language out, and a human who saw it before it was sent.

The reply box has rules per channel

A WhatsApp customer reads *bold* as bold. A Mirakl marketplace strips formatting. Amazon rejects some content outright. An email renders HTML. Emojis are fine in one channel and unprofessional in another.

Write once, and the tool should render for the channel. If the tool does not know what channel it is writing to, it will send asterisks to Leroy Merlin and a bare URL to Amazon, and you will find out from the customer.

Volume is spiky and mostly repetitive

A marketplace seller’s inbox on a Monday morning is a hundred threads, of which eighty are variations of five questions: where is it, it arrived damaged, I want to return it, send me the invoice, cancel it. The remaining twenty need a person.

The tools that work here do not try to answer everything automatically. They recognise the five questions, check the facts (the parcel status, the return window, the invoice), and put a correct draft in front of the person, who reads it and sends it. Twenty seconds per thread instead of four minutes, and no invented delivery dates.

What this means for choosing a tool

If a helpdesk vendor’s demo shows a Shopify order and a chat widget, ask the following before you sign anything:

Does the reply box know whether it is writing to the customer or the operator?
Is the queue sorted by time left on the marketplace’s clock, weekends included?
Does it read the order live from the marketplace before it lets an agent talk about it?
Can it execute a refund on the marketplace, with confirmation and a log?
Does it check translations, or just produce them?
Does it render formatting per channel?

If the answers are no, the tool will manage your email fine. It will not manage your marketplace account. That is the job.