Gorgias Rules / auto-tag / auto-reply not firing on Shopify tickets.

Several products can look like “support never answered the customer.” They do not share a settings panel. This page is only Gorgias when a Rule that should auto-tag, auto-reply, assign, or escalate a Shopify-linked ticket does not run. Choosing a helpdesk implementation versus a 72-hour ops install is Gorgias vs ops install. A Shopify Inbox queue drowning in WISMO is Shopify Inbox flooded. Shopify Inbox automated response silence is Shopify Inbox auto-reply not working. Hiring a support VA versus buying the install is support VA vs ops install. This page is only: Gorgias Rules not firing.

Seven ordinary reasons a Rule never lands usefully: the Rule is draft / paused / never saved, the channel does not match the ticket, WHEN filters skip everyone, THEN actions are empty, the Shopify integration is thin or disconnected, the ticket is closed / spam / already tagged so the Rule skips, or permissions were revoked. Walk them in that order. You already pay for Gorgias. You do not need another chatbot app to open Rules.

Open Gorgias → Rules (or Automation). Confirm the Rule status is active / on, not draft, paused, or “saved as draft” after an edit. Half-finished Rules look identical to a dead automation. Turn it on, hit Save, and force one brand-new ticket from a fresh customer identity that matches the WHEN clause.

Honest proof: screenshot the Rule header with status and last saved time before you blame deliverability or Shopify. A draft Rule cannot auto-tag.

A Rule scoped to email never sees a chat widget ticket. A chat- only Rule never sees the shared support inbox. Instagram / Facebook / SMS integrations that are “connected” but missing scopes also look like silence. Match the Rule’s channel filter to how the customer actually wrote — or widen the channel condition temporarily while you prove the THEN actions.

If you tested from Shopify Inbox instead of Gorgias, stop — that is a different product (Inbox auto-reply). Prove the ticket exists inside Gorgias first.

Over-strict WHEN clauses are the most common “not firing” bug: subject must contain an exact phrase the customer never typed, tag must already exist (so new tickets never match), intent / AI classification must equal a label your account does not use, or “from VIP segment” while the test profile is ordinary. Open the Rule’s WHEN block. Temporarily relax one condition at a time. Re-test with a ticket that deliberately matches.

AND vs OR mistakes also skip everyone — three AND conditions that each look reasonable together match almost nobody. Prefer one honest filter, prove the Rule fires, then tighten.

A Rule can be active and match WHEN while THEN does nothing useful: missing Add tag, empty Reply / Internal note body, Assign to a deleted teammate, or a macro that was renamed. Open THEN. Add one plain action — tag wismo or a one-line auto-reply with store name and expected window. Save. Re-run a matching ticket. Avoid stuffing a full FAQ into the first auto-reply; that belongs in macros and the repetitive support playbook.

Variables that resolve empty can make an auto-reply look “not showing.” Prefer short static text first, prove it appears, then add Shopify order variables carefully.

Rules that depend on Shopify order status, customer tags, or product SKUs fail silently when the Gorgias ↔ Shopify app is disconnected, the wrong store is linked, or the ticket has no customer email that matches a Shopify customer. Open Integrations → Shopify. Confirm the live store. Open the ticket side panel — if order context is blank, fix the integration before rewriting WHEN filters.

This is still not a reason to buy another helpdesk. Reconnect, then re-test one ticket with a known paid order email.

Many Rules only run on new / open tickets. Replaying an old closed thread, a spam-classified message, or a ticket that already has the target tag often skips the Rule — staff then say “not firing” after the first live test looked fine. Create a brand-new open ticket from a fresh identity. Do not reuse a closed WISMO thread as your only proof.

If the Rule fired once and later messages in the same ticket are silent, check whether THEN includes “only if tag is missing” or similar once-only logic. That is expected skip behavior — not a broken product.

Gorgias can still show Rules while Shopify scopes, email forwarding, chat widget, or social channels lost access after a staff change or reinstall. Settings look fine. Tickets never get the tag. Re-open Integrations. Confirm Gorgias still has the permissions it needs. Reconnect under an account that still has access — do not rebuild the whole support stack first.

Permissions bugs are also why people bounce to support VA vs ops quotes or a full Gorgias implementation RFP. Most of the time the fix is reconnect + one proven new ticket, not a retainer.

Counting how many identical WISMO threads hit Shopify Inbox is Shopify Inbox flooded— not Gorgias Rules. Shopify Inbox automated response silence is Shopify Inbox auto-reply not working. Comparing a support VA hire to a 72-hour ops install is support VA vs ops install. Choosing a Gorgias helpdesk implementation versus the Latch install is Gorgias vs ops install. Repetitive ticket copy and macros are repetitive support.

The only honest test for this page: Rule active, correct channel, WHEN matches a real new ticket, THEN has a tag or reply, Shopify linked, brand-new open ticket identity, then confirm the tag / auto-reply appears in Gorgias. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: turn the Rule on, match channel and WHEN, publish a short THEN action, reconnect Shopify, test from a fresh ticket. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: Gorgias vs ops install, Shopify Inbox flooded, Shopify Inbox auto-reply not working, support VA vs ops install.

Pay for help when the work is not the Gorgias Rule toggle — it is connecting the stack you already have so lead capture is not dying in DMs, ops exceptions land in a channel you already check, and checkout-ready paths are one live workflow instead of a draft Rule plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a chatbot retainer, not a Gorgias implementation, not a support VA, not a Flow agency rebuild, not a brand or theme job.

Other shops’ public ranges, not testimonials: a Gorgias Rules / support-ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or ticket-cut claim.

What it does not buy: more orders, recovered revenue, fewer tickets, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.