Ecommerce customer service outsourcing: what to hand off first

How many support tickets will your orders create?

We run a managed team in India that answers written support (email, chat and helpdesk tickets) for online stores. This guide is what we ask every owner to settle before the first ticket, whoever they hire.

Start with your volume. Gorgias, a helpdesk used by many Shopify stores, publishes the median number of tickets its stores get for every 100 orders, by category. The figures come from Gorgias customers at about $10 million in yearly sales, measured in March 2026, so Amazon sellers and much smaller stores may differ.

A worked example: a clothing store with 1,000 orders a month at the apparel median of 22 per 100 gets about 220 tickets. At 10 minutes each, that is about 37 hours of replies a month, or 8.5 hours a week.

Gorgias itself warns that volume is something you benchmark against yourself, not against other stores. To find your own rate, divide last month's tickets by last month's orders and multiply by 100. The calculator starts at 10 minutes a ticket and an 18% handoff share as placeholders: time ten of your own replies, and count your own order status tickets.

Which customer service tickets are safe to hand off first?

Sort your tickets by one test: does answering it need a decision from you, or only your written policy? Questions answered by policy can go first. Anything where money moves, or where you would want to make an exception, stays with you or goes through you.

Order status questions are usually the biggest easy group. Gorgias found "where is my order" requests averaged 18% of incoming requests in its data (2023), and says up to 30% of tickets can be shipping status questions. Check your own helpdesk tags: if order status is a larger share for you, handing it off frees more time.

On Amazon, claims and anything that touches your account health are your call. A team can collect the facts and draft the reply, but you decide.

Time zones work in your favour here (our time-zone guide has the details). India is 4.5 to 5.5 hours ahead of the UK and 9.5 to 13.5 hours ahead of the mainland US, so a team working a normal Indian day clears the questions that arrived while you slept. Agree in writing which hours are covered, including weekends and the November sales peak.

What access to give an outsourced team in Shopify and your helpdesk

Never share your own login. Each person on the outside team gets their own account in Shopify, your helpdesk or Amazon Seller Central, so you can see who did what and remove access in a minute. Most platforms let you switch off the actions that move money, while still letting the team read orders and reply.

On the Basic or Starter plan, Shopify says you can't add users. That's fine: connect your store to your helpdesk and give the team helpdesk logins only. In Gorgias, every role can see a customer's order history once the store is connected, and the Lite role can reply but can't refund, so the team never needs a Shopify login.

Shopify collaborator accounts are for Shopify Partners, such as an agency or developer you let into your store, so they aren't the right tool for a support team.

Switching off the refund permission means a mistake can't move money. The team can still say "I've asked for your refund" and tag the ticket for you.

How to keep refunds and decisions with you

1. Write your policy page and your 20 most common answers first. Our customer service cost guide walks through that in its start-small steps.
2. Switch the refund permission off in Shopify or your helpdesk, so the team can say it has asked for the refund but can't send it.
3. Use one tag for "needs owner". Refunds, exceptions and angry customers get the tag and a drafted reply. You review the tag once or twice a day.
4. Keep a second check on every reply set. Before replies go out, a second person reads them against the policy page. That's how our own team works, and it's a fair thing to ask any provider.

Test it on one inbox before you hand off more

1. Pick one inbox or one kind of ticket, usually order status.
2. Run it for two weeks, through at least one busy weekend.
3. Read every reply in the first three days, then a sample each day.
4. Measure the five things below, then decide: expand, adjust or stop.

Set the pass line before you start. One example: fewer than 1 in 10 replies changed by the second week, and no more of your own time than before. For first reply time, compare with your own baseline, not with someone else's target. Gorgias found an all-industry median of 6.3 hours at its benchmark size, from 1.6 hours in hardware to 9.1 hours in arts and entertainment.

If it doesn't work, stopping is simple: remove the accounts and keep your policy page and reply library, which you wrote and still own.

Our team handles written support (email, chat and helpdesk tickets), with refunds left to you and each reply set checked by a second person. We don't do phone support. If you want to try it, send a short brief and we'll start with one inbox.

Customer data: what the law expects when someone else replies

An outside support team reads your customers' names, addresses and orders, so in UK and EU law it is a processor working for you. The UK regulator, the ICO, says there must be a written contract that binds the processor to you. The EU GDPR (Article 28) also requires a contract, and the team can only bring in other companies to handle your data with your written permission; if you gave general permission, it must tell you about changes so you can object.

The ICO uses this exact case as an example: a UK business that lets an organisation in India access customer data on its own systems is making a restricted transfer, even though nothing is sent. Its guide on international transfers lists the safeguards such a transfer needs.

This section covers UK and EU law. For US customers, ask your adviser which state privacy laws apply. None of this is legal advice: ask your adviser which contract terms and transfer safeguards fit your store, and get them signed before the test starts.

Questions

Sources

1. Customer support metrics: tickets per 100 orders and first response time by vertical (March 2026) Gorgias
2. Automate WISMO requests (18% of incoming requests) Gorgias
3. Store permissions for staff (refund permissions) Shopify Help Center
4. Create staff accounts (Basic and Starter plans can't add users) Shopify Help Center
5. Seller Central: user permissions Amazon
6. Collaborator accounts Shopify Help Center
7. User permissions (Observer, Lite, Basic, Lead, Admin) Gorgias
8. Understanding and setting light agent permissions Zendesk
9. When is a contract needed and why is it important? Information Commissioner's Office
10. A brief guide to international transfers (updated 15 January 2026) Information Commissioner's Office
11. General Data Protection Regulation, Article 28 EUR-Lex, European Union