Gorgias prices its plans by monthly ticket or interaction volume: each tier includes a set number of tickets, and exceeding it triggers overage charges. The model rewards large teams with predictable volume and penalises small stores, whose ticket counts spike unpredictably and whose tickets are often handled by the founder anyway.
How does Gorgias pricing actually work?
We will describe the model rather than quote numbers, because exact prices change and you should always check current pricing. Structurally, as of mid-2026:
-
Plans are tiered by ticket or interaction volume. Each plan includes a monthly allowance of tickets (conversations your team touches).
-
Overages apply. Exceed the allowance and you pay additional charges for the extra tickets, or you upgrade to the next tier.
-
Automation and AI features vary by plan, and AI-driven interactions may be metered separately from human-handled tickets depending on plan structure.
None of this is hidden or unusual; per-unit billing is standard for helpdesks. The question is what unit you are billed on. Gorgias bills on tickets, meaning your bill tracks how much your customers contact you, not how much work the software saves you.
Why does per-ticket billing suit large teams?
For a brand with a five-person support team, the model is coherent:
-
Volume is high and statistically smooth, so a tier can be chosen confidently
-
The value being purchased is workflow efficiency (macros, routing, SLAs, reporting) applied across thousands of tickets
-
Overage months are rare and absorbable within a larger support budget
In that context, paying per ticket is roughly paying for the workload the platform organises. Fair enough.
Why does the same model hurt small stores?
Three mechanics work against you when you are small.
1. Spikes hit exactly when you can least afford them
Small-store volume is lumpy. One viral reel, one holiday campaign, one courier meltdown, and tickets triple for two weeks. Under per-ticket billing, your best sales month and your worst logistics month both produce your biggest support bill. Overage charges arrive precisely when cash is committed to inventory or ads.
2. You pay the same whether software or humans do the work
A ticket the founder answers manually at midnight counts against the allowance just like an automated one. For a small store, where automation coverage is the whole point, the meter does not distinguish between the platform saving you an hour and the platform merely displaying a message you answered yourself.
3. The ticket count is not really under your control
You can control replies; you cannot control inbound. Customers double-message, ask on two channels, and follow up when shipping is slow. WISMO alone commonly accounts for 25-50% of ecommerce ticket volume per industry reporting, and it scales with your order count. Growth mechanically raises your support bill even if every added ticket is a ten-second answer.
What does a volume spike look like under different models?
Consider a small store that normally gets 800 messages a month and has a launch month at 2,400.
| Pricing model | Normal month | Spike month | What happens |
|---|---|---|---|
| Per ticket (Gorgias-style) | Within tier | Over allowance | Overage charges or forced upgrade |
| Per contact (ManyChat-style) | Based on list size | List grows, bill grows | Cost rises and stays risen |
| Per AI reply (ReplAi) | Grow plan, $79.99/mo for 2,500 replies | Near plan ceiling | Upgrade if sustained; no per-ticket overage mechanics |
The per-reply column uses ReplAi's real public pricing: Free (100 replies/mo), Starter $24.99 (500), Grow $79.99 (2,500), Pro $299.95 (10,000). The point is not that one number beats another; prices change and volumes differ. The point is which direction the risk faces. Per-ticket billing puts spike risk on you; flat reply tiers cap it. Our full cost guide is in how much an AI chatbot costs for a Shopify store.
What questions should you ask before signing a per-ticket contract?
-
What exactly counts as a billable ticket or interaction? Does a customer double-texting create one ticket or two? Do AI interactions meter separately?
-
What are the overage rates, and can you cap them?
-
What did your last six months of volume look like, including your single spikiest month?
-
What share of tickets will actually be automated, and does automated resolution cost less than human-handled?
-
What is the annual commitment, and what happens to unused allowance in quiet months?
If the answers make your spiky months expensive and your quiet months wasteful, the model is mismatched to your stage, whatever the sticker price says.
What is the alternative for small Shopify stores?
Flip the unit: pay for answers delivered, not messages received. ReplAi charges per AI reply on flat monthly tiers, and the AI does the answering: under 14 seconds average response, 24/7, with 80% of messages fully automated across the merchant cohort in Q1 2026. It takes real Shopify actions in chat (order tracking, returns, COD orders, catalogue search, abandoned cart follow-ups) on Instagram, Messenger, WhatsApp, and WebChat, with human takeover from the same inbox when needed.
There is a free 100-reply plan, every plan includes onboarding with a real person, and setup is about 10 minutes via one-click Shopify install. If you are actively comparing, see Gorgias alternatives for small Shopify stores, then book a demo with your real volume numbers.
Frequently asked questions
Is Gorgias overpriced? Not inherently, and we will not pretend otherwise. For multi-agent teams with steady volume, per-ticket pricing maps reasonably to value received. The problem is fit: small stores buy team workflow tooling they do not use and accept spike risk they cannot absorb. Check Gorgias's current pricing directly, as tiers and inclusions change.
How do I estimate my real ticket volume before choosing a tier? Export or count two to three months of inbound across every channel: email, Instagram, WhatsApp, Messenger, web chat. Most merchants undercount social DMs badly. Then look at your worst spike month in the last year, because that month, not the average, determines your overage exposure.
Does per-reply pricing have its own catch? The honest caveat: a reply meter runs when the AI answers, so high automated volume needs an appropriately sized plan. ReplAi's tiers are flat and public, and usage maps to credits where 100 credits covers roughly 50-150 replies depending on conversation complexity, so you can watch usage and resize deliberately rather than being surprised by overages.
If I leave Gorgias, do I lose my support history? Your Shopify order data, customer records, and channel conversations (Instagram, WhatsApp) live in Shopify and Meta, not in the helpdesk, so the operational core survives any migration. What you leave behind is internal ticket metadata like tags and macros, which most small stores can rebuild in an afternoon.