Tool SOPs/Gorgias/Refund Macro

Gorgias Refund Macro SOP

AY
Anand Yadav · Founder, ReccordSOP
·Last reviewed June 1, 2026

The refund macro is the most-used macro in any DTC support helpdesk. It also has the highest variance in execution because every agent has small differences in tone, refund amount logic, and follow-up. This SOP locks down a single way to refund, with rep judgment preserved for edge cases.

Why this SOP matters

If two agents handle the same refund scenario differently, your customer experience is inconsistent. Inconsistent CX over hundreds of tickets a week erodes brand trust without showing up in any single metric. The refund macro is where you fix that.

Step-by-step SOP

  1. 1

    Define the refund-eligible scenarios

    Damaged on arrival, wrong item shipped, late delivery past promised date, customer remorse within return window. List the rest as escalations.

  2. 2

    Build the macro response template

    Use Gorgias variables for first name, order number, and refund amount. Include a sentence about why the refund is being issued for documentation.

  3. 3

    Configure the macro action: refund order in Shopify

    Use the built-in Shopify action. Set partial vs full refund based on macro logic. Tag the order in Shopify with the refund reason.

  4. 4

    Add the ticket tag

    Apply tags refund-issued and refund-reason-[type] for analytics. These power your monthly refund reporting.

  5. 5

    Set up follow-up automation

    Trigger a customer satisfaction survey 3 days after refund. Surveys after refunds show how well your CX recovers from a negative event.

  6. 6

    Train the agent on when not to use the macro

    If the customer is asking for store credit instead, or if the refund exceeds your one-touch limit (typically $200), it's an escalation, not a macro.

  7. 7

    Test the macro on a sandbox ticket weekly

    Shopify connection breaks silently. Catch it before customers do.

  8. 8

    Review macro usage monthly

    If usage is dropping, agents are bypassing the macro. Find out why.

Common mistakes to avoid

  • ×Not setting a one-touch refund limit, leading to agents authorizing $500 refunds without escalation
  • ×Forgetting to tag the order in Shopify, breaking month-end finance reconciliation
  • ×Hardcoding the refund reason in the email template instead of using a dropdown variable
  • ×Not testing after Gorgias-Shopify connection updates (refund action stops working silently)
  • ×Letting agents personalize the macro until it no longer resembles the SOP version

Stop rewriting this SOP every quarter

Record your screen while performing the gorgias refund macro. ReccordSOP turns the recording into a SOP with timestamped screenshots. When your live setup changes, drift detection flags it.

Generate this SOP free

FAQ

What refund amount should require escalation?

Most DTC brands set $200 as the one-touch limit. Refunds above need supervisor approval. Calibrate to your AOV.

Should agents apologize in the refund macro?

Yes, briefly. A short apology in the template, with room for one personal sentence from the agent. Robotic refund messages damage CX.

How do I track which refunds came from macros vs manual?

Tag tickets with refund-via-macro vs refund-manual. Compare CSAT between the two. Your manual refunds should show higher CSAT or you're under-trained on the macro.

AY
Anand YadavFounder, ReccordSOP

I built ReccordSOP after watching too many DTC ops teams lose months to undocumented workflows. These SOPs are battle-tested with Shopify operators running $1M to $50M brands.

Last reviewed June 1, 2026

More Gorgias SOPs