Case study · Customer support

Seller support for B2B marketplaces

Company-reported case study

Actigy BPO handled first-line seller support for TradeHarbour, a European B2B marketplace. Reported first response moved from two days to four hours over five months, with marketplace decisions retained by the client.

Actigy BPO confirms the engagement and supporting records. Results apply to the stated scope and measurement windows.

First response time

Result

4 hours

Baseline: 2 days

Window: 5 months

Supporting record: Zendesk analytics

Seller CSAT

Result

4.4/5

Baseline: 3.6/5

Window: 5 months

Supporting record: Zendesk analytics

Onboarding ticket resolution

Result

1.1 days

Baseline: 3.8 days

Window: 5 months

Supporting record: Seller portal report

Client profile

TradeHarbour, a European B2B marketplace with 280 staff.

Challenge and scope

Seller questions about admission, listings, and payment status share one queue. Routine updates wait behind issues that require a policy decision.

An onboarding application, listing edit, and payout-status question may all appear under the same seller account. Routing by contact order can leave time-sensitive cases behind informational requests. The marketplace needs to determine which issues can be resolved from the seller record and which need a decision from policy or payments.

Delivery workflow

Work 6,800 monthly tickets across four seller tiers and three languages. Review onboarding and payout status and redirect policy or payment-release decisions to marketplace owners.

Tag the contact with seller tier, issue, and next owner. Use the seller portal to verify application or listing status and compare the relevant payout reference with approved payment records. Send exceptions to the marketplace with the context, evidence, and any promised response deadline.

Keep a seller-facing update cadence for cases waiting on a marketplace decision. Group and review repeat tickets by seller and issue to identify unclear requirements or missing status guidance. Sample handoffs for the correct owner and enough evidence to act without a second intake.

Delivery team

Poland, about 13 FTE. 1 support lead, 2 QA reviewers and 10 seller support associates.

Systems and tools

Zendesk, Stripe, client seller portal.

Client decision rights

The marketplace controls seller admission, payout release, and policy enforcement.

Early milestone

At week 4, first response reaches 14 hours.

Outcomes

Company-reported results, with the baseline, measurement window and supporting record described for each measure.

Reported results: Seller support for B2B marketplaces
MeasureBaselineResultWindowSupporting record
First response time2 days4 hours5 monthsZendesk analytics
Seller CSAT3.6/54.4/55 monthsZendesk analytics
Onboarding ticket resolution3.8 days1.1 days5 monthsSeller portal report
Payout-query accuracy91%99.2%5 monthsQA review sample

Interpreting the results

The first response improves from two days to four hours, and onboarding enquiries also resolve faster. Compare those measures by seller tier and issue. Review payout-query accuracy against the same records the marketplace uses and check the time awaiting a decision for issues outside the help desk’s scope.

Recommendations for new clients

For marketplaces with onboarding and payout backlogs, break out cases by seller tier and issue type. Test the accuracy of payout explanations against the seller records.

Start with routine onboarding updates and payout-status requests in one or two seller tiers. Provide the approved responses, case identifiers, and escalation contacts for listings and payments. Review a completed ticket and a policy exception end to end before adding other queues or languages.

Scope this workflow for your operation

Use the documented workflow, client-held decisions and operational checks to outline a pilot for your own workload.