Support operations
Complaint handling for small Shopify teams: a workable system
You do not need a helpdesk suite to handle complaints well. You need one intake point, one owner per case, and a habit of asking what caused it.
Why small teams drown in complaints
Not volume — fragmentation. A complaint arrives by email, gets discussed on WhatsApp, the refund happens in Shopify admin, and the outcome is remembered by one person. Nothing is wrong at any single step, but nobody can answer "where is this now?" without asking around.
Step 1: one intake, no exceptions
Pick one destination for anything that counts as a complaint. Everything else forwards into it. A DM that gets handled in DMs will be handled twice and remembered by nobody.
- Publish one route for complaints and link it from order emails and the contact page.
- Forward social DMs and phone calls into the same place, with the order number attached.
- Record the order number at intake — a complaint without an order is a case you cannot verify.
Step 2: four states, not a workflow diagram
- New — logged, not yet read by a person.
- With us — an owner is named and the customer has been told what happens next.
- Waiting on customer — we asked for something (photo, pincode, confirmation).
- Closed — resolved, with the outcome written down in one line.
Anything more granular becomes admin nobody keeps up to date. Anything less and "waiting on customer" silently looks like neglect.
Step 3: commitments you can actually keep
- First human reply within one business day — even when the reply is "we're checking".
- A named owner per case, stated to the customer.
- A decision date for anything that needs investigation, and a message on that date whether or not it is resolved.
Under-promise deliberately. A commitment you keep at 24 hours builds more trust than one you miss at 4.
Step 4: the weekly fifteen minutes that pays for itself
Once a week, read the closed cases and tag each with a cause: product, packaging, courier, description, or expectation. Then change exactly one thing.
- Courier damage clustered on one route → change packaging or the carrier for that lane.
- "Not as described" on one SKU → the photos or the copy, not the customer.
- Delivery-time complaints in one region → state the real delivery window at checkout.
Decide tooling last
Run the system on a shared inbox and a spreadsheet for a month first. When it hurts, you will know exactly which part to automate — usually intake and order context, which is where a lightweight ticket view alongside the Shopify order earns its place. Buying the suite first just gives you a more expensive version of the same fragmentation.