How to Lower Your Gorgias Bill (Without Losing Coverage)

First, understand what Gorgias actually charges you for

You cannot cut a bill you do not understand, and Gorgias's model trips up a lot of teams. A ticket becomes billable the moment at least one message is sent from your helpdesk — whether that message comes from a human agent, the AI Agent, or an automated Rule. Per Gorgias's how you're billed documentation, the corollary matters just as much: an inbound ticket that never gets a helpdesk reply is not billable, and neither are internal-only changes like tags, notes, or assignee updates, nor replies you make directly outside the helpdesk (for example, answering a Facebook DM in Facebook itself).

Gorgias also filters newsletters, spam, and auto-responders automatically, so you generally are not paying for the marketing noise that lands in a shared inbox. The plan tiers, as of 2026, run from Starter at $10/month for 50 tickets, to Basic at $60 for 300, Pro at $360 for 2,000, and Advanced at $900 for 5,000, with overage tickets billed at $0.40 on Starter/Basic, $0.36 on Pro/Advanced, and $0.32 on Enterprise (Gorgias pricing). If any of that is fuzzy, our Gorgias pricing explained breakdown goes deeper, and what is Gorgias covers the product itself.

Lever 1: Kill spam and auto-created billable tickets

Gorgias's automatic spam filtering is good but not perfect. The tickets that quietly cost you are the ones where a Rule fires an auto-reply to something that never needed one — an out-of-office bounce, a "do-not-reply" system email, a promotional address that slipped past the filter. Because a Rule-sent message makes a ticket billable, an over-eager auto-reply rule can mint billable tickets by the hundred during a campaign send.

Audit your Rules for any that reply broadly on inbound. Tighten conditions so auto-replies only fire on genuine customer intents (order status, returns, WISMO) rather than "any new email." Add sender-based exclusions for known no-reply and vendor addresses. The goal is simple: never let the helpdesk send the first message unless a human customer actually needs an answer. This is the single cheapest lever, because it removes cost without touching your response quality at all.

Lever 2: Stop the reopen-mints-a-new-ticket trap

This is the one that generates the most billing shock, and it is worth understanding precisely. Gorgias splits a dormant conversation into a new ticket when a customer replies after a channel-specific inactivity window: 10+ days for email, 3+ days for voice and SMS, while chat and social do not split. Each new ticket is billable only if it receives a helpdesk response — but in practice it usually does, which is why merchants describe getting "charged twice for the same conversation."

Merchant reviews are blunt about this. One 2026 pricing analysis notes that "reopened tickets after a few days of inactivity often count as new, meaning you might get charged twice for the same conversation," and that "volume spikes can double your costs overnight" for seasonal stores (Featurebase). You cannot switch the windows off, but you can work with them:

• Resolve fully the first time. A conversation that is genuinely closed is far less likely to reopen 11 days later. Ambiguous, half-answered tickets are the ones that boomerang.
• Batch slow back-and-forths inside the window. If a customer needs a follow-up, keeping the exchange inside the 10-day email window means it stays one billable ticket, not two.
• Watch the WISMO pattern. "Where is my order?" threads that reopen when the package is late are a classic double-count. Proactive shipping updates cut the reopen before it happens.

Lever 3: Right-size the plan (up or down)

The screen above is where the biggest single adjustment usually lives. Under Settings → Account → Billing & usage, the Usage & Plans tab lets you adjust your ticket tier and AI Agent interaction tier directly, with a live Summary that recalculates as you change the dropdowns.

The right-sizing question cuts both ways. If you are consistently paying overage — say you are on Pro (2,000 tickets) but running 2,600 most months — the math often favours moving up a tier, because bundled tickets are cheaper per unit than overage tickets. Conversely, if you provisioned for a Black Friday peak and now run at half that volume, you are paying for headroom you do not use, and stepping down (or removing an add-on product you never adopted) is free money. Pull three to six months of your actual ticket counts from the usage view before you touch the dropdown, and size to your typical month with a small buffer, not your worst one.

Lever 4: Deflect the repetitive volume

Every lever above right-sizes what you pay per ticket. Deflection is the only one that lowers the number of tickets, which is why it compounds. In an ecommerce inbox, a large share of volume is a handful of intents — WISMO, returns and exchanges, subscription changes, discount and address edits — and these are exactly the questions that can be answered without a human ever opening the ticket.

Here the pricing model gets subtle, and it is where merchants get burned. Gorgias's own AI Agent is billed per resolution: an AI interaction runs $0.90 on annual plans or $1.00 monthly, and — critically — each AI Agent interaction also counts as a helpdesk ticket. When the AI resolves a conversation without handing it to a human, you pay both the automation fee and the ticket fee (a human handover means only the ticket fee applies). That dual charge is the source of the loudest complaints: one pricing analysis flags a Pro customer automating 30% of tickets watching costs jump "from $360 to approximately $720 monthly," and Shopify App Store reviews describe five-figure AI charges arriving on top of an already-large annual subscription (Featurebase). Our Gorgias AI Agent explained post covers the mechanics in full.

The takeaway is not "avoid AI" — deflection is genuinely the best way to shrink a usage-based bill. It is that the billing unit determines whether AI saves you money or quietly doubles it.

The honest verdict

Gorgias earns its place, especially for Shopify-native brands. The unified inbox, the deep Shopify/Shopify Plus integration that surfaces order and customer data right beside the ticket, the macros and rules, and the genuinely capable AI Agent are why it is a category leader in ecommerce support — and our Gorgias review credits all of that. Usage-based pricing is also, in principle, fair: a two-person store on Starter pays $10, not a per-seat tax.

But the complaints are real and you should size for them. The reopen-mints-a-ticket mechanic surprises people. Seasonal spikes can double a bill overnight because overage is uncapped. The AI double-billing structure is confusing enough that it has driven public frustration, and the pricing overall is frequently called one of the more opaque in the category. Gorgias is also tightly Shopify-dependent — a strength if you are on Shopify, a limitation if you are not — and some merchants report firm sales pressure at renewal. If those tradeoffs push you past the point of right-sizing, our best Gorgias alternatives guide is the next stop. Otherwise, the four levers here will meaningfully lower most bills without costing you any coverage.

Where does an AI layer fit without changing help desks? Macha runs on top of the Gorgias you already use as a native connector — it is not a helpdesk replacement, and it does not change how Gorgias bills tickets. What it changes is the unit of AI cost: Macha charges per AI action rather than per resolution, so the pricing does not double every time an agent closes a conversation. It reads and writes the same Gorgias tickets your team already works, resolves the repetitive WISMO and returns volume before it needs a human, and can look up live order or account status through a custom tool that turns your REST API into something the agent can call. Because credits are consumed per action, not per deflection, you can see the whole cost breakdown on the pricing page. Deflect the repetitive volume, keep Gorgias as the system of record, and let the billing unit work for you instead of against you.

FAQ

What counts as a billable ticket in Gorgias? Any ticket where at least one message is sent from the helpdesk — by a human agent, the AI Agent, or a Rule. Inbound tickets that never get a helpdesk reply, internal-only changes (tags, notes, assignee), and replies made directly outside the helpdesk are not billable. Newsletters, spam, and auto-responders are filtered out automatically.

Do reopened tickets cost extra? They can. Gorgias mints a new (billable-if-answered) ticket when a customer replies after 10+ days on email, or 3+ days on voice or SMS; chat and social do not split. Resolving fully the first time and keeping follow-ups inside the window is the way to avoid double-counting.

Why did my Gorgias bill spike? Usually one of three things: a seasonal volume spike pushing you into uncapped overage, an auto-reply Rule minting billable tickets, or AI Agent resolutions double-charging (automation fee plus ticket fee). Check the Usage & Plans view to see which.

Where do I change my Gorgias plan? Go to Settings → Account → Billing & usage → Usage & Plans. You can adjust the ticket tier and AI interaction tier from the dropdowns, remove add-on products, and see a live Summary before confirming.

Can I add AI without doubling my bill the way Gorgias's per-resolution AI can? Macha connects to Gorgias as a native layer and charges per AI action rather than per resolution, so cost tracks the work done rather than doubling on every closed ticket. It runs on top of Gorgias — it does not replace it — and Gorgias stays your system of record.

Want to shrink the repetitive volume that drives your Gorgias bill? Start a free trial of Macha and connect it to your Gorgias in minutes.