Customer service for marketplaces and two-sided platforms

A buyer writes at 9pm: the vintage lamp arrived broken, the seller isn't answering, and they want their money back tonight. Ten minutes later the seller writes: the buyer is lying, the lamp was packed perfectly, and why is their payout on hold? Both are your customers. Both think you should take their side. And the support team is three people who also handle onboarding new sellers.

Running support for a marketplace is harder than for a single shop, because you sit between two groups with different needs and opposite interests. With the holiday season about eight weeks away, when order volume and disputes both climb, now is the time to set up support that can take the load. This guide shows how.

Why marketplace support is different

• Two customers, two playbooks. Buyers ask about orders and refunds; sellers ask about listings, fees and payouts. Mixing them in one queue slows both.
• You're the referee. Disputes need evidence from both sides and a decision you can defend.
• Trust and safety sits inside support. Fraud, fake listings and account takeovers often show up first as a support message.
• Sellers are worth more each. Losing one active seller can cost more than losing many buyers, but there are far fewer of them.
• Rules carry legal weight. In the EU, how you handle complaints about removed listings and suspended accounts is regulated.

What each side asks

Question	Who asks	Best channel	Automate?
"Where is my order?"	Buyer	Website or in-app chat	Yes, with order lookup
"How do refunds work?"	Buyer	Chat, help center	Yes, from your policy
"The item isn't as described"	Buyer	Chat, then a dispute form	Collect evidence automatically; a person decides
"When will I get paid?"	Seller	Seller help center, chat	Yes, from payout rules and status
"Why was my listing removed?"	Seller	Email or seller portal	Explain the rule automatically; appeals to a person
Fees, commission, VAT on fees	Seller	Seller help center	Yes, from your fee page
Account suspended or flagged for fraud	Either	Email or a secure form	Never automate the decision

Step 1: Know who you're talking to

Every conversation should start with the user's role, ideally without asking. If people are logged in, pass their role (buyer, seller, both), user ID and plan to your chat tool, so the conversation arrives tagged. In Tidio, for example, you can set contact properties from your site's code and use them in Flows and routing. For visitors who aren't logged in, ask a single question: "Are you buying or selling?"

Step 2: Separate queues, content and targets

Once you know the role, route accordingly:

• Separate queues or departments for buyers and sellers, with agents trained for each.
• Separate help content: a buyer help center and a seller help center. Seller articles go deeper on fees, payouts and listing rules.
• Different response targets. Sellers with active orders often warrant faster replies; buyers in an active dispute need clear deadlines.

Step 3: Write the rules before the replies

Inconsistent answers are the fastest way to lose trust on both sides. Before you scale support, publish clear rules for:

• refunds and returns, including who pays return shipping;
• disputes: how to open one, what evidence counts, deadlines and who decides;
• fees, commission and payout timing;
• listing standards and what happens when a listing breaks them.

Then base every saved reply and every AI answer on those pages.

If two agents could give a different answer to the same dispute, you don't have a support problem. You have a policy problem.

Step 4: Automate status on both sides

Most marketplace messages are status questions: where is my order, where is my payout, why is my listing pending. Connect order and payout data to your support tool, or at least link users to a status page, and let an AI agent answer from your rules and help content. That frees your team for the conversations where judgement matters.

Step 5: Run disputes as structured cases

• Use a form, not a chat thread, to collect order ID, photos, tracking and messages between the parties.
• Give both sides a deadline to respond, and tell them what happens if they don't.
• Let a trained person decide and record the reason.
• Watch for patterns: a seller with repeated disputes or a buyer with repeated claims needs a closer look by trust and safety.

Step 6: Check your EU obligations

If you operate in the EU, two sets of rules affect support:

• The Digital Services Act has applied to all online intermediaries since February 17, 2024. Online platforms must let users complain about decisions such as removing content or suspending accounts, and marketplaces must collect and check basic information about the traders selling on them.
• The platform-to-business rules expect platforms to run an internal complaint system for business users such as sellers. Smaller platforms (fewer than 50 staff and under €10 million turnover) are exempt from that part.

Micro and small enterprises are exempt from both of those DSA duties, though not from the DSA's basic rules, and the exemption ends once you grow past the thresholds. Even if you're exempt, a clear complaint process is good practice. This isn't legal advice, so check with a lawyer which obligations apply to your marketplace.

Common mistakes

• One queue for everyone. Sellers wait behind buyers' tracking questions.
• Disputes in chat threads. Evidence gets lost and decisions can't be reviewed.
• Bots deciding refunds or suspensions. Fast, but impossible to defend.
• Help content written for only one side. Sellers end up asking agents what the help center should answer.

Which one should you choose?

• Early-stage marketplace with a small team: start with Tidio. Tag buyers and sellers, route them to departments, and let Lyro answer the routine questions while you learn what each side needs.
• Growing marketplace with high buyer volume: Tidio's Premium plan, if most of the load is repeat buyer questions and you want Tidio's team to run the AI agent and its knowledge for you.
• Growing marketplace with several teams and brands: Zendesk's multibrand setup and case management are worth the setup work.
• App-first marketplace with detailed documentation: Intercom, if the top plan fits your budget.
• Budget help desk with separate portals: Freshdesk on the Pro plan.

Whichever you choose, set it up before the holiday peak, and read our guides on handling returns and refunds and AI chatbots for online stores for the buyer side.