How Do I Stop a Gorgias Auto-Reply Loop and Auto-Close Misfires?

A Gorgias auto-reply loops because the rule triggers on New Message In Ticket without the condition Message From Agent Is False, so every new message, including your agents' own replies, fires it again. Add that condition, or trigger the acknowledgement on Ticket Created, which happens once per ticket. Auto-close misfires have a different cause: rule order. Rules that share a trigger run top to bottom, so the auto-close rule has to sit above the auto-reply rule to close spam before anything answers it.

Which cause matches what I'm seeing?

Start here, then jump to the matching section below.

Why does my auto-reply fire on every message?

The rule triggers on "New Message In Ticket" and has no guard against replies. When an auto-reply fires on a new message rather than only on ticket created, Gorgias re-evaluates the rule every time a message lands on the ticket, including your agents' replies and the customer's follow-ups. Each qualifying message fires the auto-reply again, and you get a stack of duplicate canned responses.

The fix is one condition. Add Message From Agent Is False to the rule. Gorgias's Rules FAQs recommend this condition so the rule doesn't activate when a team member responds; an agent's reply no longer counts as a fresh trigger, and the loop breaks. If you only want to acknowledge the customer's first inbound message, trigger the rule on Ticket Created instead of New Message In Ticket. That event happens once per ticket, so it can't loop.

There's also a safety net you don't configure. Gorgias throttles duplicate auto-replies itself. The Rules FAQs say: "we don't send a single auto-reply more than once per 5 min per customer, to avoid spamming customers with the same message over and over again." That 5-minute per-customer window is why a loop can look intermittent. Rapid messages get collapsed, but a thread that runs for hours still re-fires on each new message unless you add the from-agent guard. Treat the throttle as a backstop. The cure is Message From Agent Is False plus the right trigger event. For how the WHEN / IF / THEN structure works, see Gorgias rules explained.

Why do two auto-replies fire on one ticket?

More than one rule matches the same message. If you've built several auto-reply rules over time (one for order status, one for returns, one for "we're closed") and their conditions overlap, a single inbound email can satisfy two of them and get two replies. Rules with the same trigger run top to bottom, so both fire unless one is scoped tightly enough to exclude the other.

The fix: consolidate and scope. Audit your active auto-reply rules and make their conditions mutually exclusive (tags, channel, or keyword conditions that can't both be true), or fold them into one rule with branching. The 5-minute throttle suppresses an identical duplicate, but two different auto-replies aren't identical, so the throttle won't help here. Scoping has to. When you build or edit these, how to set up rules in Gorgias walks through the condition builder step by step.

Why is auto-close closing real customer tickets?

The auto-close rule matches too broadly, or the right addresses aren't excluded. Gorgias ships Auto-close spam as a managed automation. Its rules documentation says it "can't be modified or duplicated" like an ordinary rule. What you can tune on the rule's detail screen is its Email exclusion list (addresses or domains it should never touch) and its Always apply list (addresses it should always close). When a genuine sender keeps getting swept up, such as a supplier, a marketplace notification you actually read, or a VIP customer on an unusual domain, add them to the exclusion list rather than turning auto-close off.

The same detail screen lets you check the blast radius before you trust it. The Affected tickets preview shows a live sample of tickets the rule is closing, so you can see whether anything legitimate is in there.

In what order do Gorgias rules run, and where should auto-close go?

Auto-close sitting below auto-reply means the auto-reply fires first. Gorgias runs rules in a fixed trigger priority. Its rules documentation lists six triggers in this order: Ticket created, New message in ticket, Ticket updated, Ticket assigned to user, Ticket snooze delay ends, then Satisfaction survey responded. When two rules share the same trigger, they run top to bottom in the order they're listed on the Rules page, and you reorder them by dragging the six-dot icon next to each rule. If auto-close and auto-reply both trigger on "Ticket Created" but auto-reply is listed higher, a spam ticket gets an auto-reply before auto-close closes it. Now you've replied to a spammer.

The fix: keep the auto-close rule above the auto-reply rule, on the same event. The rule's detail screen carries its own callout: "keep this rule at the top of your rules to ensure it triggers first." Put auto-close first and give both rules the same first-line event (Ticket Created, New Message In Ticket, or both), so the close runs first and the auto-reply never touches a ticket already binned as spam.

Why do rule fixes stop working when customer wording changes?

None of the above is a Gorgias defect. The rule engine is deterministic, and once you know the trigger order and the from-agent guard, it's predictable: a rule either matched or it didn't. That's also the ceiling. Auto-reply and auto-close both decide by pattern (sender, keyword, tag, channel). They can't tell that "where's my stuff" and "I never got my order, this is the third time I'm writing" are the same intent with different heat, or that a spam-looking address is a frustrated repeat customer. So you end up hand-maintaining exclusion lists and keyword conditions, which quietly break when wording shifts. If loops and misfires keep returning because customer language escapes your conditions, you've hit the edge of what rules can express.

Can an AI agent handle what rules can't?

This is where an AI agent helps. AI agents for customer service act on intent rather than exact keywords, so a genuine question gets answered and true junk gets closed without a hand-ranked stack of rules to keep in sync. Macha is one such agent, and it runs on top of the Gorgias you already use, not instead of it. It reads and writes the same tickets your rules touch (replies, tags, status, assignment), so your rules keep doing the routing they're good at while the agent handles the intent-heavy work. For the mechanics, Gorgias AI agent explained and connecting Gorgias to Macha to automate ticket replies cover the connection and what it can do.

Because an agent acts on meaning, you don't switch it on and hope. Macha lets you batch-grade a candidate agent against your real historical Gorgias tickets before it touches a live queue, and you can extend it with a custom tool that turns any REST API into an action, such as looking up order status mid-conversation, which no native rule condition can do. Macha bills per ticket (one conversation, charged once however many messages it takes), never per resolution, from $299 a month for up to 750 tickets. The pricing page has the tiers.

FAQ

Why does my Gorgias auto-reply fire on every message instead of just once? Because the rule triggers on New Message In Ticket, and Gorgias re-evaluates it on every new message, including your agents' replies. Add the condition Message From Agent Is False so agent responses don't re-trigger it, or trigger the rule on Ticket Created (once per ticket) if you only want to acknowledge the customer's first message.

How often can the same auto-reply be sent to one customer? Gorgias throttles it: per its Rules FAQs, "we don't send a single auto-reply more than once per 5 min per customer." That's a backstop against spamming, not a substitute for the "Message From Agent Is False" condition. A thread spanning hours will still loop without the guard.

How do I stop auto-close from closing real customer tickets? Add the sender's address or domain to the auto-close rule's Email exclusion list so it's never swept up, and use the Affected tickets preview to check what the rule is closing before you trust it. Auto-close spam is a managed automation that can't be modified or duplicated, so you tune it through its exclusion and "always apply" lists rather than rewriting its logic.

Should auto-close be above or below my auto-reply rule? Above. Keep the auto-close rule at the top and give both rules the same first-line event (Ticket Created and/or New Message In Ticket), so spam is closed before the auto-reply can respond. Rules with the same trigger run top to bottom.

Can AI replace these rules entirely? It doesn't have to. An AI agent like Macha connects on top of Gorgias and acts on intent, so it can answer real questions and close true junk without a hand-ranked rule stack, while your rules keep handling routing. See connecting Gorgias to Macha for how the layering works.

Tired of babysitting rule order and exclusion lists? Start a free trial and grade a Macha agent against your own Gorgias history before it touches a live ticket.