Two customers who want opposite things
A marketplace is really two businesses sharing a website. Buyers want selection, trust, and a smooth purchase; sellers want visibility, fair fees, and prompt payouts. Their questions barely overlap, and sometimes their interests directly conflict. Live chat has to serve both without treating them as one undifferentiated queue — because a buyer question and a seller question need different people and different answers.
Route by who is asking
The first job is knowing which side of the marketplace a chat comes from. A seller asking about payout timing and a buyer asking about a delivery need different expertise, and nothing frustrates faster than a payout question answered as if it were a return. Routing that distinguishes buyer from seller — by page, by account type, by a quick pre-chat prompt — is the foundation everything else rests on.
Handle disputes without picking sides badly
The hardest marketplace conversations are the two-sided ones: a buyer and seller in conflict, each in your chat wanting you to take their side. The skill is staying fair and process-driven — apply your policies consistently, keep records of what each party was told, and resist being pushed into an off-the-cuff ruling. A dispute handled evenly protects trust on both sides; one handled sloppily loses a buyer and a seller at once.
Trust is the whole product
A marketplace's real asset is trust — buyers trusting sellers deliver, sellers trusting they get paid. Responsive, fair chat support is a direct investment in that trust. Every quick, honest resolution reinforces that the platform has both sides' backs, which is exactly what keeps both sides coming back.
How MyLiveChat fits
MyLiveChat routes chats by department so buyer and seller questions reach the right expertise, keeps transcripts that matter when a dispute needs a record of what was said, and lets a single team cover both sides cleanly. It scales from one agent up, suiting a marketplace still growing into separate buyer and seller support.
You are supporting two customers with opposing interests
A marketplace runs two support operations that happen to share a queue. Buyers want their
order, a refund, or reassurance that a seller is legitimate. Sellers want visibility, payouts,
listing help, and protection from unreasonable buyers. In a dispute, helping one is often
experienced as failing the other — which is a situation no ordinary support playbook
covers.
The first structural decision is whether the two share a queue at all. Separate entry points
— a widget on the seller dashboard distinct from the buyer-facing one — let you route
to people who know that side of the business, and let the agent know immediately whose interests
they are hearing. Mixing them means every agent needs both sets of knowledge and switches
constantly between them.
Know what you can and cannot promise about a third party
The defining constraint of marketplace support is that you usually do not control the thing
the customer is asking about. The item is in the seller’s warehouse; the dispatch decision
is theirs; the stock accuracy is theirs. Agents who forget this make commitments the platform
cannot keep.
The distinction agents need to hold:
- What you control: the platform, payments held by you, the dispute process, policy enforcement, and your own timelines.
- What the seller controls: stock, dispatch, packaging, and the item itself.
- What you can commit to about the seller: only process — that you will contact them, and by when they must respond.
“I cannot dispatch it myself, but I can require a response from the seller within
48 hours, and if that does not happen the protection policy applies and I will refund you
directly.” That is honest, useful, and entirely within your power.
Disputes need a process, not judgement calls
Buyer-seller disputes are the hardest conversations on a marketplace, and the worst way to
handle them is agent discretion in the moment. Discretion produces inconsistency, inconsistency
produces appeals, and appeals produce the perception that shouting works.
What holds up is a written process both sides can see: what evidence is needed, how long each
party has, who decides, and what the outcomes can be. Agents then explain and apply the process
rather than adjudicating personally, which protects them from being the villain and protects the
platform from arbitrary-looking decisions.
Say the same thing to both sides. It is tempting to soften the message for whoever is
currently in the chat, but marketplace disputes routinely end with both parties comparing what
they were told, and any discrepancy becomes the new complaint.
Seller support is a growth function
It is easy to treat seller enquiries as internal admin and staff them lightly. That is a
mistake, because sellers are the supply side — a seller who cannot get a listing or payout
problem resolved lists elsewhere, and their inventory leaves with them.
Seller questions also skew toward the operational and urgent: a payout that has not arrived, a
listing suppressed without explanation, a sudden drop in visibility. These have a livelihood
attached, so the emotional stakes are higher than the topic suggests. Route them to people who
understand the seller tools and can get a real answer, and be specific about timelines —
“payouts run Thursday and yours is in that batch” ends an anxious week.
Trust and safety cuts across everything
Marketplaces attract fraud in both directions, and chat is often where the first signal
appears — a buyer describing a seller pushing them to pay outside the platform, a seller
reporting a suspicious bulk order. Agents need a clear, low-friction way to flag these, and
explicit instruction never to move a conversation off-platform themselves.
One firm rule worth stating plainly to both sides: the chat widget is not a verification
channel. Agents must not accept identity documents, payment details, or credentials in chat, and
should route those to the proper process.
What to measure
Report buyer and seller metrics separately — combining them hides one side degrading.
Track dispute resolution time and the appeal rate, which is your best indicator of whether the
process is understood and seen as fair. On the seller side, watch whether support responsiveness
correlates with sellers staying active; it usually does, and it is the number that turns support
from a cost line into a supply argument.