Running Shopify support without a helpdesk

What a helpdesk actually gives you

Worth being precise, because it is a real list and some of it matters a lot:

• One queue for email, chat, social and sometimes voice
• Assignment, ownership and collision prevention
• SLAs and escalation rules
• Shared macros with variables
• Customer and order context in the ticket
• Reporting on volume, response time and agent performance
• Order actions such as refunds without leaving the tool

If you need the first three, buy a helpdesk. This article is not an argument against them.

What most small stores actually need

Look at that list again from the position of a store with one or two people answering email. The channel problem does not exist. The assignment problem is solved by a rota. The SLA problem is solved by clearing the inbox daily.

What is left is the middle three: templates, order context, and knowing how you are doing. Those are solvable without moving your inbox anywhere.

The setup

1. Delegated shared inbox

Google Workspace delegation on support@, each person on their own login. Ten minutes to configure, and it removes the shared-password problem permanently. Full setup here.

2. Four action labels

Waiting on carrier, waiting on customer, escalated, refund pending. Each one means someone has to do something. Descriptive labels do not survive contact with a busy week.

3. Templates built around scenarios, not topics

Not "shipping" but "fulfilled, no carrier scan yet". The scenario determines the reply; the topic does not. Our WISMO set is organised this way.

4. Order context next to the email

This is the one that decides whether the whole setup holds. If answering an order question means opening Shopify, searching, and copying a tracking number back, you will feel the pain dozens of times a day — and eventually conclude you need a helpdesk, when what you needed was the order on screen.

5. Two numbers, monthly

First response time, and the share of tickets that are order status. Those two tell you whether the setup is holding and where the volume comes from. Anything more is reporting you will not act on at this size.

The economics, briefly

Helpdesks price by agent or by ticket. Per-agent means three people costs three times one. Per-ticket means your busiest month costs the most, which is precisely when margin is tightest. Neither model is unfair — they reflect real cost — but both assume support is a function with headcount.

Below that scale, the honest comparison is not helpdesk versus cheaper helpdesk. It is helpdesk versus fixing the one thing that is actually slow.

When to switch anyway

Switch when any two of these are true:

• Support arrives on more than one channel and you are checking several places
• More than five people answer email
• You need SLAs you can actually report against
• Tickets get lost, not occasionally but structurally
• You need refunds and cancellations from inside the support tool

At that point a helpdesk is the right spend and delaying it costs more than it saves. Our alternatives guide covers the options, including staying put.