headset, man wearing a headset, headphone, music, listening, man, guy, male, man listening to music, excited, shouting, saiyed irfan anwarhushen, headphone, excited, excited, excited, excited, excited
Photo by SAIYEDIRFANANWARHUSHEN on Pixabay

Tools and providers

Part of Customer service software: marketplace inbox fit checks

Customer service software: marketplace inbox fit checks

Customer service software for UK marketplace sellers: five checks for inbox routing, connector write-back and queue performance before you approve a helpdesk.

What to take away

Customer service software for UK marketplace sellers needs a working route from the buyer's message to the support queue and back. Use the checks below to test that route before extending or replacing a helpdesk.

  • Zendesk fits a support team running several channels, where routing rules and service-level timers do the work.
  • Gorgias fits a smaller team that answers from the order list and wants storefront and marketplace messages in one view.
  • Neither ships a native Amazon or eBay message pipeline, so budget for a connector or forwarding rule that writes replies back to the marketplace.
  • Both process customer records on your instructions, so a written processing agreement and a retention rule come before the first import.

What separates the two platforms

Zendesk was built as a general ticketing helpdesk, and its core objects are still brands, groups, macros and service-level timers; background on how the product developed sits outside this comparison. Gorgias began as a storefront helpdesk and keeps the order beside the conversation, which suits sellers who answer from an order list rather than a shared queue.

The deciding question is which channels a tool treats as first class. UK sellers often run a storefront and two or three marketplaces at once, and each surface exposes buyer messages differently. Amazon and eBay messaging are connected routes, not native inboxes: a connector reaches Amazon through the Selling Partner API and eBay through its developer APIs, then writes the reply back into the marketplace thread. Marketplace-message connectors are sold separately — ChannelReply, for instance, sits between Amazon or eBay and a helpdesk inbox — and both vendors publish integration directories you can search for the channels you sell on.

Where a seller already answers storefront email in one of the two, extending it to marketplace messages normally costs less than running a second helpdesk. Routing rules, agent permissions and reports stay in one place, and training effort is not repeated.

Zendesk and Gorgias compared on the deciding points

Zendesk vs Gorgias

Zendesk

Core object
Tickets and queues
Marketplace messages
Connector app or forwarded email
Routing
Brands, groups, macros, timers
Reporting
Agent workload and timers
Pricing unit
Per agent seat
Data role
Processor under agreement

Gorgias

Core object
Conversations tied to orders
Marketplace messages
Connector app or storefront integration
Routing
Rules, tags, automations
Reporting
Volume with order context
Pricing unit
Contact or ticket bands
Data role
Processor under agreement

Zendesk and Gorgias compared

Zendesk

Core object
Tickets and queues
Marketplace messages
Connector app or forwarded email
Routing
Brands, groups, macros, service-level timers
Reporting
Agent workload and timers
Pricing unit
Per agent seat, tiered by features
Data role
Processor under a processing agreement

Gorgias

Core object
Conversations tied to orders
Marketplace messages
Connector app or storefront integration
Routing
Rules, tags, automations
Reporting
Volume with order and revenue context
Pricing unit
Contact or ticket volume bands
Data role
Processor under a processing agreement

Five checks before you approve either tool

Five steps before approving

  • Map each marketplace message route and deadline
  • Test connector in sandbox; confirm replies land in thread
  • Set retention rule to close and delete old conversations
  • Record exit routeticket export and connector revocation
  • Price twelve months of seats, bands and connector fees
  1. Confirm the marketplace route.Ask how the connector reaches Amazon and eBay, and whether it writes replies back into the buyer thread rather than only logging them.
  2. Fix the payable event.Decide whether you are billed per agent seat or per contact band, and write down what counts as a contact.
  3. Price your peak, not your average.Get quotes at your quiet-month and peak-month volumes, plus the overage rule above the band.
  4. Request the data papers.The data processing agreement, the current sub-processor list and the retention settings for chat transcripts and buyer emails, in writing.
  5. Run one queue for thirty days.Compare first-response time and reopened tickets with your current route, and keep the raw exports.

What sits outside the seat price

Seats are only the visible cost. Contact-based bands, the marketplace connector, implementation days and extra reporting sit outside them. A contact band that resets each month can move the bill further than an extra seat does. Fix the payable event before you compare quotes, using the method in these notes on marketplace software pricing models. Read the contract on the same pass: notice period, the overage rule above the band, the connector's own terms, and what happens to exported tickets and transcripts at exit.

Subscriptions are standard-rated for VAT, and the registration threshold has stood at £90,000 since 1 April 2024 (GOV.UK), so check the rules on registering for VAT before signing a twelve-month term.

Customer records and UK data protection

Both platforms process personal data on the seller's instructions rather than deciding what happens to it, so the seller keeps the UK GDPR duties: lawful basis, retention, subject access and breach reporting. Ask for the data processing agreement, the current sub-processor list and the retention settings in writing. Check whether chat transcripts and marketplace buyer emails are handled under the same rule.

The Information Commissioner's Office (ICO) is the UK's data protection regulator.

Judging fit before you commit

Run one queue, not all of them, for thirty days. Compare first-response time and reopened tickets against the current route, and keep the raw exports. Score the results with the evidence discipline in this marketplace software quality checklist. If the connector cannot write replies back to the marketplace thread, the tool is a reporting screen rather than a support system, whatever the demonstration showed.

Common questions

Do Zendesk and Gorgias read Amazon buyer messages natively?

No. Both rely on an integration or a forwarded email address, and Amazon's own messaging rules still govern what you may send. Test the write-back before you rely on it for first response.

Check Amazon's Communication Guidelines and eBay's Member-to-member contact policy alongside the connector's capabilities.

Which is cheaper for a two-person UK seller?

It depends on agent count, billable message volume, connector charges and the features you need. Compare Zendesk's seat model with Gorgias's volume-based pricing, rather than treating a two-person team as enough information to choose. Neither vendor quotes a single price that fits every seller, so ask both for a quote at your quiet-month and peak-month volumes and check what resets each month.

Do I need a data processing agreement with either vendor?

Yes. Both act as processors, so the agreement is the document that sets retention, sub-processors and deletion. Keep it with the contract and review it when marketplace terms or connectors change.

Can one seller run both tools at once?

Yes, but there is rarely a reason. Splitting queues across two inboxes fragments reporting and doubles the routing work, unless a legacy storefront contract forces it.

More in Tools and providers