The Two-Customer Problem

Most businesses have one type of customer. Marketplaces have two: buyers and sellers. And their interests directly conflict.

A buyer wants a refund for a late delivery. A seller wants to keep the payment because they shipped on time and the delay was the carrier's fault. Both contact your support team. Both think they're right. You have to make a decision that will make one of them unhappy.

This is why marketplace support is uniquely hard. But it's also why automation is uniquely valuable — routing the right question to the right team with the right context saves enormous amounts of time.

Buyer Questions (What They Ask)

Order-related (50% of buyer volume):

• "Where's my order?"
• "The item doesn't match the listing"
• "I need to cancel my order"
• "I never received my package"

Payment and refunds (25%):

• "I want a refund"
• "I was overcharged"
• "How do I use a promo code?"

Trust and safety (15%):

• "Is this seller legit?"
• "The seller isn't responding"
• "I think this listing is a scam"

Account (10%):

• "How do I change my address?"
• "How do I leave a review?"
• Password reset, email change, etc.

Seller Questions (What They Ask)

Payouts and fees (35% of seller volume):

• "When do I get paid?"
• "Why was my fee higher this month?"
• "Where's my payout?"
• "How do fees work?"

Listing management (25%):

• "How do I update my listing?"
• "My listing was removed — why?"
• "How do I add variations?"

Disputes and returns (20%):

• "A buyer wants a refund but the item was delivered"
• "How do I handle a return?"
• "The buyer's complaint is false"

Account and verification (20%):

• "How do I verify my identity?"
• "My account is under review"
• "How do I change my payout method?"

The Routing Challenge

The first thing your support system needs to do is figure out: is this a buyer or a seller? Then route accordingly.

Buyers and sellers often use different language for the same underlying concept. A buyer says "I want a refund." A seller says "the buyer wants their money back." Same transaction, different perspective, different routing.

Intent classification handles this naturally. The classifier identifies:

• return_request (buyer) → route to buyer support with refund authority
• dispute_resolution (seller) → route to seller support with transaction details
• payout_inquiry (seller) → auto-respond with payout schedule
• order_tracking (buyer) → auto-respond with tracking link

Automating Marketplace Support

What to automate for buyers:

• Order tracking (auto-pull tracking data)
• Basic refund requests within policy (auto-process)
• Promo code issues (auto-respond with instructions)
• Account management (password reset, address change)

What to automate for sellers:

• Payout schedule questions (auto-respond with schedule)
• Fee explanations (auto-respond with fee structure)
• Listing format questions (auto-respond with guidelines link)
• Verification status (auto-respond with status check)

What needs humans:

• Disputes between buyers and sellers (someone has to decide)
• Trust and safety issues (fraud, scam reports)
• Account suspensions and appeals
• Complex fee disputes
• Escalated complaints from either side

Handling Disputes

Disputes are the hardest part of marketplace support. Here's a practical framework:

Step 1: Classify the dispute type. Is it about delivery (carrier issue), product quality (seller issue), or misrepresentation (listing issue)? Classification catches this automatically.

Step 2: Gather evidence from both sides. Auto-request: send the buyer a form asking for photos/details, send the seller a form asking for shipping proof/details. Don't make a decision until you have both sides.

Step 3: Apply your policy. If your marketplace has clear policies (returns within 14 days, seller ships within 3 days, etc.), many disputes resolve by simply applying the rules. Automate the policy application where possible.

Step 4: Communicate the decision. Tell both parties what happened and why. The losing party will be unhappy — that's unavoidable. But clear, specific reasoning ("Your return was approved because the item doesn't match the listing photos") is better than vague ("Your dispute was resolved").

The Metrics That Matter for Marketplaces

• Buyer satisfaction: If buyers aren't happy, they stop buying. Track buyer CSAT separately from seller CSAT.
• Seller satisfaction: If sellers aren't happy, they leave and take their inventory with them. Track separately.
• Dispute resolution time: How long from dispute filed to resolution? Target: under 48 hours.
• Dispute rate: What percentage of transactions result in disputes? Rising dispute rate = platform trust problem.
• GMV-per-support-ticket: How much gross merchandise volume is generated per support ticket? This tells you if support costs are proportional to revenue.

Track buyer and seller satisfaction independently. Optimizing for one at the expense of the other kills marketplaces.