Gorgias Snooze & Ticket Statuses Explained

The three statuses, and what they mean

Per Gorgias' handling incoming tickets documentation, a ticket is always in one of exactly three states.

Open is the working state: the customer is waiting on a reply, or an agent is actively on it. Open tickets sit in your main views and count against your queue.

Snoozed is the "not yet, but not done" state. You reach for it when you can't close a ticket but don't want it staring at you either — you're waiting on a customer to send a photo of a damaged item, waiting on the warehouse to confirm stock, or promising a follow-up once a pre-order ships. A snoozed ticket disappears from your open view and comes back on its own.

Closed is the resolved state: the issue is handled and no further action is needed, so it leaves your queue. As we'll see, "closed" in Gorgias is deliberately reversible — a closed ecommerce ticket is one customer reply away from being open again.

If you're new to the platform's model of tickets, tags, and views, our what is Gorgias primer sets the wider context; this piece zooms in on the lifecycle itself.

How snooze works: durations and the header menu

To snooze, click the snooze icon in the ticket header and pick a duration. Gorgias offers a fixed set of quick presets — 1 hour, 3 hours, 6 hours, 1 day, 3 days, or 1 week — plus a calendar/time picker for snoozing until a specific date and time, which is the one you want for "reopen the morning the restock lands." The full behaviour is documented in Gorgias' snooze tickets guide.

There's a subtlety worth pinning down, because it explains behaviour that confuses people. Gorgias' own docs note that "once snoozed, the ticket status will be set to closed, the ticket will be removed from your view." In other words, snooze is implemented as a scheduled, self-reopening close rather than a fourth independent status. Practically, that's invisible day to day — a Snoozed badge with a countdown appears on the ticket, and if an admin has set it up, snoozed tickets collect in a dedicated Snoozed view in the sidebar so nothing gets truly lost.

What reopens a snoozed ticket

A snoozed ticket comes back to the top of your open queue when any one of three things happens:

1. The snooze timer expires — the ticket reappears automatically at the time you set.
2. The customer replies — a new inbound message pulls the ticket back into open immediately, even if the timer hasn't run out. This is the important one for support: if the shopper writes in again, you don't want them waiting behind a snooze you set.
3. An agent manually reopens it — click the Snoozed badge to unsnooze early or adjust the timer.

That customer-reply trigger is what makes snooze safe to use liberally. You're never gambling that a customer will be ignored; you're only deferring the proactive follow-up you owe them.

Snooze automatically with rules

You don't have to snooze by hand. Gorgias Rules can snooze tickets automatically using a "Snooze for" action, and can fire follow-up logic when the snooze delay ends (the trigger is labelled around TICKET SNOOZE DELAY ENDS). A common ecommerce pattern: when an agent tags a ticket awaiting-customer, a rule snoozes it for 3 days; if the timer ends with no reply, another rule reopens it and applies a follow-up-needed tag or sends a gentle nudge via a macro. That turns snooze from a personal reminder into a team-wide SLA hygiene mechanism.

Closing a ticket — and why it's reversible

Gorgias gives you two ways to close, depending on whether you're sending a reply on the way out:

• Close without replying — click the Close button in the ticket header. Use this when the resolution happened elsewhere (a refund processed in Shopify, a duplicate ticket) and no message is needed.
• Send & Close — the button in the reply area that sends your message and closes the ticket in one step, saving the second click. This is the workhorse for "here's your answer, we're done."

Once closed, the button updates to read Closed. But closing is not a locked door: if a customer replies to a closed ticket, Gorgias automatically reopens it, and an agent can reopen manually by clicking the Closed button. That reversibility is exactly right for ecommerce, where a "resolved" return can reignite the moment the shopper asks one more question — but it has consequences for your numbers, which we'll get to next.

How status drives your SLA report and stats

Here's the part that trips up managers reading the dashboard. Status isn't just queue hygiene — it feeds directly into how Gorgias measures performance, and the rules are less intuitive than they look.

Per Gorgias' SLA report documentation, snoozing a ticket does not pause its SLA timer. Snoozed tickets are counted based on their underlying SLA status — whether the timer has actually run out — "not just because they are snoozed." So if you snooze a ticket to get it out of sight, the clock keeps ticking underneath; a snooze is not a get-out-of-SLA card.

Closing behaviour matters too. A ticket with both a first-response and a resolution target only counts as achieved once it satisfies all the policy's conditions. A ticket that's had a first reply but is still open sits in a pending state and isn't yet included in the achieved/breached calculation. And because closes can be undone, reopened tickets can flip their outcome — a ticket that read "achieved" can become "breached" in a later reporting window when it reopens, gets worked again, and closes late. Gorgias tracks the latest SLA status inside your selected date range, so the same ticket can wear different labels depending on the window you're looking at.

The takeaway: treat status as data, not just tidiness. Snoozing to clear your view is fine; snoozing to hide a breaching ticket only hides it from you, not from the report.

The honest limits — and where an AI layer picks up

Gorgias' status model is clean and does its job well: three states, sensible reopen rules, automatable via rules, and wired into SLA reporting. Nothing here is broken. But notice what snooze and status can't do — they manage when a ticket sits in your queue, not whether it needs to be there at all.

Snooze is, at bottom, a deferral. When you snooze a "where's my order?" ticket for a day because the tracking hasn't updated, you're betting the answer will exist tomorrow and that you'll have time to write it then. The ticket still has to be read, understood, and answered by a human when it wakes up. Multiply that across a Black-Friday queue and "snooze it for later" quietly becomes a backlog with a delay timer.

This is the seam where an AI agent layer fits — and it's worth being honest about the build-versus-buy tradeoff before reaching for one. Gorgias has its own native AI Agent, and it's a real option; we cover it in Gorgias AI Agent explained. It's worth knowing that Gorgias' AI Agent is billed per automated resolution, and that some of the deepest ecommerce actions (self-service order edits, returns) lean on Shopify-gated Flows and app connections — honest context when you're comparing approaches.

Macha is a different shape of the same idea: an AI agent layer that runs on top of the Gorgias you already use, via the live Macha↔Gorgias connector — never a replacement for your help desk. It reads and writes the same tickets your statuses and SLAs already track: instead of snoozing a WISMO question, a Macha agent can look up the order through a custom tool that turns your store or 3PL's API into something the agent can call, and post a grounded reply now — so the ticket goes straight to closed rather than snoozed. And a genuine, honest contrast worth stating plainly: Macha's credits are consumed per AI action, not per resolution — a different billing model from Gorgias' per-resolution AI, with no hard-coded prices to quote here (see the pricing breakdown).

The clean division of labour: keep Gorgias' open/snoozed/closed lifecycle as the source of truth for what's in the queue and what's overdue, and layer an agent on top for the part status can't do — actually answering the deferrable tickets fast enough that you rarely need to snooze them at all.

FAQ

What are the three ticket statuses in Gorgias? Open, snoozed, and closed. Open means the ticket is active in your queue; closed means it's resolved and removed from your view; snoozed means it's temporarily hidden and set to reopen automatically after a chosen period.

What snooze-until durations does Gorgias offer? Quick presets of 1 hour, 3 hours, 6 hours, 1 day, 3 days, and 1 week, plus a calendar/time picker to snooze until a specific date and time. You snooze from the snooze icon in the ticket header.

Does a snoozed ticket reopen if the customer replies? Yes. A snoozed ticket reopens automatically when the timer expires, when the customer sends a new reply, or when an agent manually unsnoozes it — so a customer writing back is never left waiting behind a snooze.

Does snoozing pause the SLA timer in Gorgias? No. Per Gorgias' SLA report docs, snoozed tickets are counted based on their underlying SLA status (whether the timer has run out), not simply because they're snoozed — snoozing hides a ticket from view but does not stop its SLA clock.

Can I add AI to Gorgias without replacing it? Yes. Macha connects to Gorgias as a live native connector and runs on top of your existing help desk and its statuses — it doesn't replace them. It helps close deferrable tickets by looking up order data and posting grounded replies, while Gorgias stays the system of record for open, snoozed, and closed.

Ready to close the tickets you'd otherwise snooze? Start a free trial of Macha and connect it to your Gorgias in minutes.