Why do generic helpdesks struggle with marketplace support?
Generic helpdesks assume one requester and one problem. On a marketplace every dispute has a second party with its own deadline.
- Buyer and seller roles on each contact. One email address can belong to a buyer, a seller or both. Without role and seller tier on the ticket, agents answer payout questions with buyer macros.
- Two parties per case. A damaged-item claim means a thread with the buyer, a thread with the seller and an internal record linking them.
- Investigations need private space. Trust and safety notes about a suspected fraud ring must never reach the user being reviewed, so comments and side conversations have to stay internal.
- Money answers live elsewhere. Holds, reserves and fee ledgers sit in the payments system, so a missing-payout ticket stalls while someone waits on finance.
- Some deadlines come from law. Under the INFORM Consumers Act, a US marketplace has 10 days to collect a high-volume seller's bank, tax and contact details once the seller passes 200 sales and $5,000 in revenue within 12 months, then 10 more days to verify them. In the EU, the platform-to-business regulation requires a statement of reasons when a platform restricts or suspends a business user.
- Fraud targets the help desk. Scammers pose as sellers to redirect payouts, or as buyers to claim refunds on delivered orders. Agents need recent account changes in front of them.
How should a marketplace organize its support inbox?
Give each side its own queues, put trust and safety above everything, and make disputes a separate team so nobody judges their own customer's case.
| Queue | What lands there | SLA target | Owner |
|---|---|---|---|
| Trust and safety urgent | Off-platform payment requests, account takeover signs, threats, dangerous or counterfeit goods | Example: human reply in 15 minutes, 24/7 | Trust and safety operations |
| Disputes | Contested not-received and not-as-described claims, with both parties' evidence | Example: decision within 5 business days of escalation | Disputes team |
| Buyer orders and claims | Tracking, cancellations, uncontested claims, returns | Example: 4 business hours | Buyer support |
| Seller payouts and fees | Missing or held payouts, fee questions, invoices | Example: 1 business day, and always before the next payout run | Seller support with finance |
| Seller verification and tax | Missing documents, high-volume seller checks, tax form corrections | Inside the INFORM Act's 10-day windows where they apply | Seller compliance |
| Listing and account appeals | Removed listings, restrictions, suspensions | Example: 2 business days, decided by a person | Policy team |
| Managed sellers | Top sellers and brand partners with an account manager | Example: 1 business hour | Seller success |
| Legal and rights notices | Intellectual property complaints, law enforcement requests | Set by legal policy | Legal |
Routing rules
- Trust and safety keywords first. A workflow tags "gift card", "wire", "pay me directly" and similar phrases and assigns them before any other rule runs.
- Role and tier from company metadata. Role, seller tier and region become filters and columns, so managed sellers skip the general queue.
- Round-robin inside buyer support and seller support (Growth and up).
- One claim ID on both threads. Tag the buyer's and the seller's conversations with the same claim ID, and let a webhook open the case in your disputes system.
- Finance in Slack, not email. Ask payments about a stuck payout in a side conversation, and give finance reviewers free Lite seats to comment and approve.
- Jira for product bugs. A workflow creates a Jira issue when several sellers report the same dashboard problem.
Which reply templates does a marketplace support team need?
Write templates for replies where one side loses, money is held or a scam is in play, and have policy and legal review each one.
Dispute decided for the buyer (to the seller)
Hi {seller_name}, we've reviewed claim {claim_id} for order {order_id}. The buyer reported {issue}, and we didn't receive {missing_evidence} by {deadline}, so we refunded the buyer {amount} under our buyer guarantee. Under our seller policy, {recovery_outcome}. If you have evidence we haven't seen, reply within {appeal_days} days and someone who wasn't involved in this decision will review it.
Dispute decided for the seller (to the buyer)
Hi {buyer_name}, we looked into claim {claim_id}. The seller sent {evidence_summary}, which shows {finding}, so we can't refund this order under the buyer guarantee. If something new comes up, reply and we'll take another look.
Payout on hold
Hi {seller_name}, your payout of {amount} due on {date} is on hold because {recorded_reason}. To release it, {required_action}. We'll review it within {review_time}, and the money goes out on the next payout run.
Listing removed
Hi {seller_name}, we removed your listing "{listing_title}" on {date} because it breaks our {policy_name} policy: {specific_reason}. Your other listings aren't affected. If you think we got this wrong, appeal here: {appeal_link}. A member of our policy team will review the appeal personally.
Keep the specific reason in both of the last two templates: the EU's Digital Services Act and platform-to-business regulation require a statement of reasons when a platform restricts a seller or removes their content.
Off-platform payment warning
Hi {first_name}, thank you for telling us. Please don't send money, gift cards or codes outside {marketplace_name} or follow links to pay elsewhere. Payments made off the platform aren't covered by {protection_name}. Our trust and safety team is reviewing the other account and will {next_step} by {date}.
How should a marketplace staff support across the year?
Staff each side separately, keep trust and safety running around the clock, and plan for shopping events, payout runs and tax season.
Who does what
- Buyer support and seller support work separately; seller support gets read access to the payout ledger.
- Disputes works contested claims from both sides' evidence, apart from buyer and seller support.
- Trust and safety covers scams, takeovers and prohibited items 24/7, because fraud doesn't keep office hours.
- Seller success looks after top sellers by name.
- Policy and appeals reviews removals and suspensions, with a different reviewer from the one who made the original call.
When volume peaks
- Late November to December. Shopping events bring buyer tracking and delivery questions, and seller questions about shipping cutoffs and promotion fees.
- January. Holiday returns arrive alongside seller tax questions. Sellers get Form 1099-K by January 31 if a payment platform or marketplace paid them more than $20,000 across more than 200 transactions. Under HMRC's digital platform reporting rules, UK platforms report most sellers' income to HMRC by 31 January (sellers with fewer than 30 sales and under about EUR 2,000 of goods a year are excluded) and must give sellers a copy.
- The day after each payout run. Failed and held payouts arrive as a wave, so schedule seller support for it.
- Fee or policy changes. Publish the help center article first and fully staff seller support for the following week.
Cross-train buyer support on uncontested claims before December, and use forecasting in Insights to roster around payout dates and shopping events.
Where does AI help a marketplace support team?
AI shortens each human reply and removes routine, uncontested requests from the queue, so people spend their time on disputes, appeals and fraud.
- Sourced drafts. Copilot drafts replies that cite the buyer guarantee, seller policy or fee schedule. Aftersales measures a 2.4× faster median reply for teams using it on every conversation.
- Dispute summaries. A claim reaches the disputes team as both parties' positions, the evidence and the deadlines, instead of two long threads.
- Translation. Cross-border buyers and sellers write in their own language; Copilot translates in 31 languages, including right-to-left scripts.
- Agent for routine conversations. The routine share of buyer and seller questions can close before reaching a queue; the AI customer service for marketplaces page lists which ones and where Agent hands off.
- Monitors on every conversation. Monitors score every dispute reply against your policy, so a reviewer sees which buyer-side agents skip the seller's evidence before an appeal arrives.
- Early warnings. Insights spots a jump in "payout missing" conversations after a payout run, or in not-received claims for one carrier, while it is still small.
What support metrics should a marketplace track?
Measure each side separately and add dispute and payout metrics. A blended CSAT score hides unfairness to one side.
| Metric | Formula | Target guidance |
|---|---|---|
| Buyer contact rate | Buyer conversations ÷ orders | Trend down; split by contact reason |
| Seller contact rate | Seller conversations ÷ active sellers | Trend down; expect spikes after fee or policy changes |
| Dispute decision time | Median time from escalation to decision | Inside your published policy; review every breach |
| Appeal overturn rate | Decisions reversed on appeal ÷ decisions appealed | Investigate a rise: it points to unclear policy or inconsistent reviewers |
| Payout contact rate | Payout conversations ÷ payouts sent | Low and steady; a spike means a batch problem |
| Chargebacks after contact | Chargebacks on orders where the buyer contacted support first ÷ all chargebacks | Trend down; each one is a claim support didn't settle |
| Trust and safety response time | Median time from report to human reply | Minutes, by channel and hour |
| CSAT by side | Satisfied responses ÷ responses, for buyers and sellers separately | Watch the gap between the two |
| Cost per conversation | (Seats + AI resolutions + channel costs) ÷ conversations | Trend down with both CSAT scores steady |
Insights reports resolution rate, CSAT for AI and humans and cost per conversation. Every plan includes the Events API and CSV export; Scale adds Snowflake, BigQuery and Redshift sync, so support data can sit beside your order and payout tables.
How do marketplaces switch customer service software?
Move one side at a time. Sellers make a good first group: the queue is smaller and the questions more predictable.
Many teams work in Zendesk, Freshdesk or Intercom beside an in-house admin tool for payouts and moderation. Compare Zendesk alternatives or Intercom alternatives. If agents stay in Zendesk or Freshdesk for now, add Agent there first and move the queues over later.
- Map account role, seller tier, claim ID and verification status to custom fields, and keep only macros and tags you still use.
- Connect the admin tool through the API or webhooks so payout and moderation records appear on the ticket.
- Migrate history; on Growth and Scale, Aftersales runs the migration with you.
- Run seller queues in parallel for two weeks, then move buyers and phone, and trust and safety last.
Plans start free; paid seats cost $24 to $109 a month billed annually (pricing).