The typical European marketplace seller is not a support organisation. It is a founder, or one operations person, who answers customers between purchasing, listings and the warehouse. Support gets the leftover hours, and the leftover hours are when the marketplace clocks run out.

This is the routine that works for that person. None of it requires a particular tool, although a tool that does it for you is the difference between a routine and a good intention.

Sort by time left, never by time received

Open the inbox and the default sort is newest first. That is wrong for marketplaces. A message from Sunday night that Amazon’s 24-hour clock has been counting since 22:14 is more urgent than the one that arrived a minute ago, and a Mirakl thread the operator has already flagged is more urgent than both.

Sort by time left before the deadline. Everything else in the routine follows from the queue being in the right order. If your tool cannot do this, do it by hand once a day: oldest unanswered first, weekend messages at the top on Monday.

Two passes a day, not one

One long support session a day produces one long gap. Two short ones (first thing, and mid-afternoon) keep every clock under 24 hours with room to spare, and the afternoon pass catches the replies to your morning replies.

Morning: everything overdue and everything due today. Afternoon: whatever came in since, plus the threads that were waiting on you (a carrier claim, a warehouse check).

The weekend is the problem. Amazon’s clock runs on Saturday. A ten-minute Sunday-evening pass over the queue, sorted by time left, is the cheapest insurance against a Monday morning of red numbers.

Let rules handle the noise

A large share of what lands in a mailbox is not a customer: order notifications, marketplace newsletters, carrier bulk updates, invoices from suppliers, “your listing has been approved”. None of it needs a reply and all of it hides the messages that do.

Write rules for the noise, not for the customers. “From the marketplace’s notification address: mark done.” “Subject starts with ‘Invoice’ from a known supplier: tag and move on.” The goal of a rule is to make the queue smaller, never to answer a person automatically. Auto-replies to customers on a marketplace are a bad idea: they reset nothing on the operator’s side and they read as exactly what they are.

Recognise the five questions

Eighty percent of marketplace threads are five questions: where is it, it arrived damaged or wrong, I want to return it, send me the invoice, cancel it. A person who has answered each of these a hundred times can answer them in twenty seconds, if the facts are in front of them: the parcel’s real status, the return window, whether the invoice exists.

So the useful investment is not a library of canned replies but a way to get the facts next to the thread. For “where is it,” that is the carrier’s tracking. For returns, the order date against your return policy. For invoices, the invoicing tool. When the fact is one click away, the reply is trivial. When it is three tabs away, the reply gets postponed, and postponed replies are the ones that go overdue.

Write shorthand, send full sentences

The person doing this job knows exactly what they want to say and does not have time to write it nicely a hundred times. “Order on the way, arrives Thursday, sorry for the delay.” That is the whole content. The greeting, the full sentences, the sign-off and the customer’s language are packaging.

Separating the two is the biggest time saver in the routine. Type the content. Let the tool (or a template, or a colleague) turn it into a proper reply with your sign-off, and translate it if the customer wrote in another language. Read the result. Send. The rule that keeps this honest: the packaging may change the tone, never the facts. If the shorthand says Thursday, the reply says Thursday.

Anything that moves money waits for a click

Refunds, cancellations, replacements. These are the actions customers push hardest for and the ones you most regret doing in a hurry. On a marketplace they are also performed on the marketplace, where they are visible to the operator and cannot be undone.

The routine here is a deliberate pause: check the order live (has it already been refunded? has it shipped?), decide, click, and keep a record of who clicked and when. A tool can do the checking and the record-keeping. The click stays human.

Measure three numbers on Friday

Not a dashboard. Three numbers, written down weekly:

How many threads went overdue on any marketplace’s clock. The target is zero. If it is not zero, the reason is almost always the weekend or a single bad day, and both have fixes.
Median time to first reply. Not the average, which one forgotten thread ruins. The median tells you what a normal customer experienced.
How many threads you answered with the facts in hand versus “let me check.” Every “let me check” is two threads instead of one.

When the first number is zero for four weeks running, the routine is working, and you can stop thinking about it, which is the point.

The whole routine on one card

Queue sorted by time left, weekends included.
Two passes a day, ten minutes on Sunday evening.
Rules for noise, never for people.
Facts next to the thread before you reply.
Shorthand in, full reply out, facts unchanged.
Money waits for a click, and the click is logged.
Three numbers on Friday.

Most of this is discipline. The rest is tooling that makes the discipline cheap enough to keep.