All resources

Operations

How to Write a Shopify Customer Service SOP From Scratch

A Standard Operating Procedure — SOP — is the document that tells your support agent exactly what to do when a customer contacts your store. Without one, every agent makes different decisions, CSAT scores are inconsistent, and you get pulled back into the inbox every time an edge case arrives. With one, your inbox runs without you. This guide shows you how to write your first Shopify customer service SOP in under two hours.

By Patrick · Founder, Virtual Freelance Solutions · 10+ years in eCommerce customer support

Why most Shopify stores do not have an SOP — and why that is a problem

Most founders start by answering support themselves. They know the policies in their head. When they hire a VA or outsource to an agency, they assume the agent will figure it out. The agent does figure it out — by guessing. And guessing produces inconsistent replies, over-refunding, and customers who learn they can push for better outcomes by escalating. An SOP removes guesswork entirely.

What a Shopify customer service SOP covers

A complete SOP has five sections:

  1. Refund and return policy
  2. Shipping and delivery responses
  3. Subscription management (if you sell subscriptions)
  4. Escalation rules
  5. Brand voice guidelines

You do not need a 20-page document. A one-page SOP covering these five sections handles 90 percent of the tickets your store receives.

Section 1 — Refund and return policy

Write down:

  • Your return window (e.g. 30 days from delivery)
  • Conditions required (e.g. unused, original packaging)
  • Returnless refund threshold (e.g. orders under $30 — refund without return)
  • What to do if the customer is outside the return window (e.g. offer store credit, or deny)
  • Dollar threshold above which to escalate to the founder

This section alone resolves the majority of tickets your agent will receive.

Section 2 — Shipping and delivery responses

Write down:

  • Your standard shipping timeframe per region
  • What to say when an order is delayed at the supplier
  • What to say when tracking shows delivered but the customer says missing
  • How to handle a lost in transit claim (open carrier investigation vs. immediate reship)

Include a template response for each scenario. Your agent copies, personalises with the customer's name and order number, and sends.

Section 3 — Subscription management

If you sell subscriptions via Recharge, Skio, or Stay AI, add:

  • How to process a pause request
  • How to process a cancellation — including any save-desk offer to make first
  • How to handle a failed payment and resend the billing link
  • Swap or product change requests

Section 4 — Escalation rules

Not every ticket can be resolved at agent level. Define clearly:

  • Which situations require founder approval (e.g. refunds above $150, legal threats, media enquiries)
  • How to escalate (e.g. tag the ticket "Escalate — Founder" in Gorgias or Zendesk and email the founder)
  • Target response time for escalated tickets

Section 5 — Brand voice guidelines

Write three things:

  1. Tone — formal or casual? One sentence describing how your brand sounds.
  2. Sign-off — exactly how every email should end (e.g. "Warm regards, [First Name] — [Brand Name] Support")
  3. Words to avoid — any phrases that feel off-brand (e.g. "unfortunately," "I apologise for the inconvenience," excessive exclamation marks)

Pro tip

Once your SOP is written, hand it to us and we can start managing your inbox the same week. Our agents work from your SOP from day one — following your policies and brand voice exactly. From $10/hr, no lock-in contracts. See our pricing to get started.

How to keep your SOP current

An SOP is a living document. Review it after every new supplier issue, every policy change, and every time an agent asks you a question that is not covered. Add the answer to the SOP so the next agent never needs to ask again. Store the SOP somewhere your agent can access it during every shift — a shared Google Doc works perfectly.

Frequently asked questions

How long should my first SOP be?
One page for most stores. Two pages if you sell subscriptions. Longer than that and agents stop reading it.
Do I need a different SOP for each helpdesk tool?
No. The SOP covers your policies and voice. Tool-specific instructions (how to process a refund in Gorgias vs. Zendesk) can be added as a one-paragraph appendix for each tool.
What if my policies change after I hand over the inbox?
Update the SOP and brief your agent. Changes take effect on the next shift. Keep a version history so you can track what changed and when.

People Also Ask

Related resources

Related service pages

Want to see how this would look for your brand?

We'll walk through your current support stack, ticket categories, and tooling — and show you what an operationalized version looks like inside Zendesk, Gorgias, or Help Scout.