Gorgias Quick Responses & Macros vs Rules (When to Use Which)

The four tools, in one sentence each

Before the framework, the vocabulary — because "quick response," "macro," and "template" get used interchangeably in Gorgias and it causes real confusion.

• A Macro is a saved, reusable response-plus-actions block that an agent applies with one click. In Gorgias, "quick response" and "macro" refer to the same thing — a pre-written reply you drop into the composer, optionally carrying actions like tagging or setting status. Per the Gorgias macros documentation, you build them under Dropdown menu (top-left) → Workflows → Tools → Macros.
• A Rule is backend if/then automation: when a ticket matches conditions, then do something — including applying a macro, tagging, assigning, or auto-replying, all with no agent present.
• A Flow is a customer-facing, interactive self-service path — a scripted series of questions and answers the shopper clicks through before a ticket ever reaches an agent.
• An AI agent is the reasoning layer: it reads the actual message, decides what the shopper wants, fetches what it needs, and answers — no keyword list or fixed script required.

The single cleanest way to hold it in your head: Macros are agent-assist, Rules are backend automation, Flows are customer self-service, and AI is judgment. For a fuller grounding on the platform itself, see what is Gorgias.

Macros: for the repetitive reply a human still sends

Reach for a Macro when a human is in the loop and the wording repeats. Macros exist to kill the retyping. If ten agents answer "where's my order?" fifty times a day, a WISMO macro gives them one consistent, on-brand reply — and, crucially, macros do more than paste text. Per the macro actions documentation, a single macro can add or remove tags, set status/priority/subject, assign an agent or team, snooze, post an internal note, set ticket and customer fields, add attachments, and fire HTTP hooks. On Shopify-connected accounts it can cancel or duplicate an order, refund shipping, or edit an address; on Recharge, manage subscriptions.

Macros are available on all Gorgias Helpdesk plans, though only owners, admins, and leads can create them — every agent can apply them. That governance split is deliberate: you want a curated library, not fifty personal variants of the same return-policy reply.

The catch is that a macro sits there until an agent chooses it. It has zero opinion about which ticket it belongs to. That's exactly the gap Rules fill. If you want the step-by-step build, our Gorgias macros explained walkthrough covers variables and composition in detail.

Rules: for the action that should happen without a human

Reach for a Rule when the trigger is predictable and you don't want to wait for a click. A Rule is the "if this, then that" engine. Per the Gorgias Rules product page, you can build conditions on the message body, detected sentiment, detected intent, the channel (chat, contact form, Help Center), and Shopify order data — then attach actions. The most powerful action for our purposes is Apply macro: a Rule can watch for "order status" phrasing, detect the WISMO intent, and automatically fire the WISMO macro with the tracking link filled in, hands-free.

Rules also do the unglamorous backend work: auto-tagging by intent (which pairs neatly with a deliberate tag taxonomy — see Gorgias tags explained), auto-assigning to the returns team, auto-closing spam, and hiding negative social comments. The mental model: a Macro is the what; a Rule is the when. Bolt them together and a repetitive ticket answers itself. Our Gorgias rules explained post goes deeper on conditions and ordering.

Flows: for the question the shopper can answer themselves

Reach for a Flow when the path is fixed and the shopper is happy to click through it. Flows are customer-facing and interactive — a scripted branch of questions and answers that lets a shopper self-serve before a human is involved: a returns walkthrough, a sizing guide, a "start a return" or "check my order" path. They're excellent for high-volume, low-variance journeys where the steps genuinely never change.

The honest caveat: the richest Flows and self-service order-management journeys are part of Gorgias's Automate / AI Agent capabilities, which are a separately-priced add-on to your Helpdesk plan — and much of the shopper-facing self-service is strongest on Shopify-connected stores. So "just use a Flow" isn't free the way a Macro or Rule is. Budget for it, and confirm what your plan includes.

The decision table (ecommerce edition)

Here's the framework applied to the four requests every Shopify support team sees daily.

Read top to bottom and the pattern is clear: the more the request varies in wording and the more judgment it needs, the further right you move — from Macro, to Rule, to Flow, to an AI agent that actually reasons.

The honest limits — and where an AI layer picks up

None of these four tools is a weakness; each is genuinely good at its job, and Rules especially are the deterministic, auditable backbone of a well-run Gorgias instance. But it's worth naming where they run out of road, because that's where teams over-invest and get frustrated.

Macros don't understand context. A macro is a static block; it can't decide it's the wrong reply for this particular customer's history or situation. Rules are rigid keyword-and-condition matching. As eesel's guide to Gorgias workflows puts it, a rule watching for "order status" quietly misses "any update on my delivery?" — same intent, different words, no trigger. Every phrasing you didn't anticipate is a rule that didn't fire. Flows only work when the path is truly fixed; the moment a shopper steps off-script, they're back in the queue, and the richest Flows sit behind the paid Automate add-on anyway.

There's also a billing shape worth understanding before you lean hard on native AI. Gorgias's AI Agent / Automate is billed per resolution — roughly $0.90 per resolved conversation on annual plans (and each resolution also counts as a helpdesk ticket), per the Gorgias AI agent pricing breakdown. That's a fine model, but it ties your automation cost directly to volume in a way that's worth modelling. Our Gorgias AI agent explained post covers the native option in full.

This is the seam where an AI agent layer fits — and the broader category of AI agents for customer service exists precisely to do the reasoning that a macro, rule, or fixed flow can't. Macha is one such layer, and the Macha ↔ Gorgias connector is live: it runs on top of the Gorgias you already use — it does not replace your help desk, your macros, or your rules. You connect it to Gorgias, and it reads and writes the same tickets: understanding a request by meaning rather than keyword, looking up an order or subscription through a custom tool that turns your REST API into something the agent can call, and drafting or sending a grounded reply. Two honest contrasts worth flagging: Macha's credits are consumed per AI action, not per resolution — a different, more predictable meter than Gorgias's per-resolution AI billing (see the pricing breakdown) — and the connector is designed to augment your existing Rules and Macros, not compete with them.

The clean division of labour: keep Macros for agent-assist, Rules for backend automation, and Flows for fixed self-service — then layer an AI agent on top for the varied, reasoning-heavy tickets the first three can't touch.

FAQ

What's the difference between a Gorgias macro and a rule? A macro is a saved response-and-actions block an agent applies with one click (the what); a rule is backend if/then automation that fires on its own when a ticket matches conditions (the when). You often combine them: a rule detects an intent and automatically applies the matching macro.

Are "quick responses" and "macros" the same thing in Gorgias? Effectively yes — Gorgias's pre-written, reusable agent replies are called macros, and "quick response" is the everyday term for the same thing. You create and manage them under Workflows → Tools → Macros.

When should I use a Flow instead of a Rule? Use a Flow when you want the shopper to self-serve through a fixed, clickable path (a returns walkthrough or order-status check) before a ticket is created. Use a Rule when you want backend automation — tagging, routing, or auto-replying — without the customer clicking through anything. Note that the richest Flows are part of the paid Automate add-on.

Do macros cost extra on Gorgias? No. Macros are available on all Gorgias Helpdesk plans. Only owners, admins, and leads can create them, but every agent can apply them. The AI Agent / Automate capabilities (which power the most advanced Flows) are a separately-priced add-on billed per resolution.

Can I add AI to Gorgias without replacing my macros and rules? Yes. An AI agent layer like Macha connects to Gorgias as a live connector and runs on top of your existing setup — it augments your macros and rules rather than replacing them, handling the varied, reasoning-heavy tickets that keyword rules and static macros miss.

Ready to add reasoning on top of the automation you already run? Start a free trial of Macha and connect it to your Gorgias in minutes.