Gorgias Auto-Responders Explained (Automated Replies)

First, the terminology (and the retirement you need to know about)

"Auto-responder" in Gorgias isn't one button — it's a pattern you build. Historically Gorgias had a dedicated Autoresponder Rules feature, but per Gorgias' own Autoresponder Rules (Retired) documentation, that feature is no longer available for accounts created after September 2024, and brands that had it lose access on January 30, 2026. The official guidance: Shopify brands should move automated responses to AI Agent, and everyone else builds auto-replies with Rules.

So when we say "auto-responder" today, we mean a Rule — Gorgias' if-this-then-that automation engine — configured to reply, or to close, without a human touching the ticket. If you want the full mechanics of the engine itself, Gorgias Rules explained covers the trigger → condition → action model end to end; this post is the applied version for automated replies. And if you're still getting oriented on the platform, what is Gorgias is the primer.

The three auto-responder patterns

There are really three jobs people mean when they say "automation," and each maps to a Rule shape:

• First-response auto-reply — the instant "thanks, we've received your message" acknowledgement on every new ticket, so no shopper waits in silence.
• Out-of-office (after-hours) reply — a holding message that only fires when a ticket arrives outside your business hours, setting expectations for when a human will follow up.
• Auto-close — silently closing tickets that never needed a reply at all: out-of-office bounce-backs, newsletters, order-confirmation notifications, and obvious spam.

The first two send something; the third removes noise. All three are Rules, and Gorgias ships template versions of each.

Building a first-response auto-reply

Per Gorgias' Rules documentation, you create rules under Settings (bottom-left) → Ticket management → Rules → Create rule. A basic acknowledgement auto-reply looks like this:

1. Click Create rule and pick the Autoresponder template, or start from scratch.
2. Set the trigger to WHEN → Ticket created.
3. Optionally narrow with an IF condition — for example, channel is Email, so you don't auto-reply to live chat.
4. Add the action THEN → Reply to customer, and write your message (WISMO-savvy stores often include a line like "if this is about an existing order, reply with your order number").
5. Save and activate the rule.

From that point, the rule replies to the first message on every matching new ticket. The Auto-Reply common Rule templates doc lists ready-made variants — including Shopify Order Status templates that reply with a tracking link and auto-close for recent orders that have shipped, which is the closest native thing to a WISMO deflection.

Building an out-of-office (after-hours) reply

The out-of-office pattern is the same Rule with one extra condition: it should only fire when you're actually closed. Gorgias exposes an "Emails received outside business hours" condition, but it requires you to have set your business hours first.

1. Create a new Rule from the Outside Business Hours template.
2. Trigger: WHEN → Ticket created.
3. Condition: IF → emails received outside business hours.
4. Action: THEN → Reply to customer with your after-hours message ("Thanks for reaching out — our team is offline until Monday 9am ET and will reply then").
5. Save and activate.

A common refinement is to run two rules: a during-hours acknowledgement and a separate after-hours message, so the tone matches the moment. Just make sure their conditions are mutually exclusive so a ticket can't trip both.

Building an auto-close rule

Auto-close is the unglamorous workhorse. Its whole point is to keep tickets that never needed attention from cluttering the queue — and, helpfully, from counting toward billing. Per Gorgias, an auto-closed ticket doesn't count toward your monthly billable ticket total as long as it was never responded to by an agent or a Rule. That makes auto-close a genuinely economical way to handle out-of-office bounce-backs and non-support noise.

The Auto-Close common Rule templates doc ships two general templates worth knowing: Automatic OOO replies (closes tickets that are themselves automated out-of-office messages) and Non-support tickets (closes notifications from payment processors and commerce platforms). You extend the latter by adding sender emails or subject-line patterns to its list.

The rule above is an installed [Auto Close] template — "Auto-close spam emails" — that closes irrelevant email like newsletters and promotions. Note the two lists it exposes: an exclusion list (senders it should never auto-close, so a real customer using Gmail's promotions tab isn't silenced) and an always-apply list. Those lists are the difference between a tidy inbox and one that quietly buries real tickets.

Loop-avoidance: the part people skip

The classic auto-responder failure is the email loop: your auto-reply hits an automated inbox, that inbox auto-replies back, your rule fires again, and two robots ping-pong forever. Gorgias' documentation bakes in several guardrails, and a couple more are on you:

• Auto-close OOO before you auto-reply to it. The Automatic-OOO-replies auto-close template exists precisely so out-of-office bounce-backs get closed rather than answered — the single biggest loop source.
• Exclude no-reply and automated senders. Use the exclusion list on your auto-close rule (and condition checks on your auto-reply rule) so no-reply@, notifications@, and platform emails never trigger a reply.
• Auto-reply Rules can't apply to ChannelReply tickets or internal-note-only tickets — per Gorgias' auto-reply best practices, which quietly removes a class of accidental triggers.
• Don't run outside-hours auto-replies on Facebook or Instagram — Gorgias warns these can be flagged as spam by the platforms. Keep social auto-replies out of your OOO rule's scope.
• Fire on first contact, not every message. Trigger on Ticket created rather than New message in ticket for acknowledgements, so a long back-and-forth doesn't re-send the greeting on every customer reply.

The honest limits — and where an AI layer picks up

Gorgias' auto-responders are good at what they are: fast, deterministic, cheap. A Rule will always fire on the same condition and send the same text, which is exactly what you want for an acknowledgement or a spam sweep. But notice the ceiling. An auto-reply is static — it sends the words you wrote, regardless of what the shopper actually asked. It can say "we got your message about your order"; it can't read the message, look up order #4471, see it shipped yesterday, and reply with the tracking link and a real answer. The template that comes closest (Shopify Order Status) is Shopify-gated and rule-rigid — it works only for the exact order states you pre-wired.

For anything genuinely dynamic, Gorgias points you at AI Agent — but that's an add-on with its own gating (it currently requires a connected Shopify store) and it bills per resolution, so the price scales with the very outcomes you're trying to grow. That's a fine model for some teams; it's worth understanding before you commit, which is why Gorgias AI Agent explained exists.

This is the seam where an AI agent layer fits — and it's the broader category of AI agents for customer service that does the reasoning a static rule can't. Macha is one such layer: it runs on top of the Gorgias you already use through a live native connector — it does not replace Gorgias, your Rules, or your macros. You keep your acknowledgement and auto-close Rules exactly as they are; Macha handles the tickets a static reply can't, drafting or sending grounded answers to WISMO, returns, and refund questions by reading live order data through a custom tool that turns your APIs into something the agent can call. The economics differ too: Macha bills per AI action, not per resolution — a genuine, honest contrast with Gorgias AI Agent's per-resolution model, and it means an ambiguous or half-answered ticket doesn't carry an outcome charge. See the pricing breakdown for how credits work, and connecting Macha to Gorgias for the setup. The clean division of labour: keep Gorgias Rules as the source of truth for acknowledge, route, and close, and layer an agent on top for actually answering. If your Rules also do a lot of canned-text sending, Gorgias macros explained pairs naturally with this.

FAQ

Does Gorgias still have an "Autoresponder" feature? Not as a standalone tool for new accounts. The legacy Autoresponder Rules feature is retired for accounts created after September 2024, and older accounts lose it on January 30, 2026. Today you build auto-responders as Rules, and Shopify brands are pointed toward AI Agent for automated responses.

Where do I create an auto-reply rule in Gorgias? Go to Settings (bottom-left) → Ticket management → Rules → Create rule. Use the Autoresponder or Outside Business Hours template, set the trigger to WHEN → Ticket created, add a Reply to customer action, and activate it.

Do auto-closed tickets count toward my Gorgias bill? No — as long as the ticket was never replied to by an agent or a Rule, an auto-closed ticket doesn't count toward your monthly billable ticket total. That's what makes auto-close an economical way to clear spam and out-of-office bounce-backs.

How do I stop auto-reply loops in Gorgias? Auto-close out-of-office and no-reply/notification emails before they get answered, exclude automated senders on your rules, trigger acknowledgements on Ticket created (not every new message), and avoid running outside-hours auto-replies on Facebook or Instagram, which can be flagged as spam.

Can I add AI replies without replacing Gorgias? Yes. An AI agent layer like Macha connects to Gorgias through a live native connector and runs on top of your existing help desk, Rules, and macros — it doesn't replace them. It handles the dynamic answers a static auto-reply can't, and it bills per AI action rather than per resolution.

Ready to move from "we got your message" to an actual answer? Start a free trial of Macha and connect it to your Gorgias in minutes.