Shopify Support Handover Checklist

The short version: A support handover transfers five things: access, knowledge, voice, open work, and measurement. Get every account and permission on day one, document how this store actually handles its top twenty situations, agree the tone customers already know, hand over open tickets with context instead of a bare export, and baseline the metrics so the new team can prove it is holding the line.

1. Access: everything, on day one

Helpdesk or inbox (Shopify Inbox, Gorgias, Zendesk, or plain email) with the right permission level – not the owner's login.
Shopify staff account scoped to orders and customers; note what it cannot do (refunds, address changes) so nobody discovers limits mid-ticket.
Live chat, reviews app, returns portal, shipping and tracking tools, and any social inboxes customers use.
Password handover through a password manager invite, never a spreadsheet or a chat message.

2. Knowledge: the top twenty situations, in writing

Every store's queue is concentrated: where-is-my-order, returns and exchanges, damaged or wrong items, discount and price questions, sizing or product advice, address changes, cancellations, and a handful of store-specific ones. For each, the handover document states the policy, the steps in the tools, the macro or template if one exists, and where the edge cases go. If the previous holder kept this in their head, the first handover task is a structured interview to get it onto paper – undocumented knowledge is the single biggest handover risk.

3. Voice: how this store talks

Customers notice a voice change before they notice anything else. Capture the store's greeting and sign-off conventions, how formal or playful replies run, what the store never says, and how complaints and angry customers are handled – including exactly which situations get a goodwill gesture and who authorizes it. Two or three real past tickets, anonymized, teach more than a page of adjectives.

4. Open work: tickets with context, not a data dump

Every open ticket listed with its status, what the customer was last told, and what happens next – and by when.
Pending refunds, replacements in transit, and promised callbacks or follow-ups flagged separately: these are commitments, not tickets.
Known problem orders and ongoing carrier or supplier disputes documented with their reference numbers.
A short overlap period where the outgoing holder answers questions beats a clean cutover almost every time.

5. Measurement: baseline before the switch

Record the outgoing state: ticket volume by week, first response time, resolution time, and customer satisfaction if it is tracked. Without a baseline, every later conversation about whether support improved is opinion. The incoming team reports against the same numbers from week one – the same discipline we run on stores handling 300 or more tickets a week, where the queue's patterns are visible in the data within days.

6. The first two weeks

Expect a shakedown list: permissions that turn out narrower than described, a policy nobody wrote down, one app nobody mentioned. Log them, resolve them with the owner in a single weekly pass, and update the handover document as you go – by the end of week two it should be the store's real support manual, ready for the next handover to be painless.

Handing over your store's support?

We take over Shopify and WooCommerce support queues with a structured handover: access, documentation, voice, and reporting from day one.

E-Commerce Support Service Discuss Your Requirements

The Shopify Support Handover Checklist: Taking Over a Store's Customer Service Cleanly