# Gorgias Pricing Explained: How 'Billable Tickets' Inflate Your 2026 Costs
> Gorgias's pricing model seems simple, but its reliance on 'billable tickets,' overage fees, and AI add-ons creates unpredictable costs that penalize store growth.
Source: https://arbyn.app/blog/gorgias-pricing-explained-how-billable-tickets-inflate-your-2026-costs
Published: 2026-08-31
---
For a growing Shopify store, success is measured by increased sales and customer engagement. But what happens when the tools meant to support that growth start to penalize it? Many helpdesk platforms seem straightforward on the surface, offering tiered plans for a set monthly price. The problem lies buried in the fine print: complex billing mechanics, usage limits, and punitive overage fees that can cause costs to spiral unexpectedly after a successful campaign or sales season. This is the frustrating reality for many store owners navigating gorgias pricing, a model built around a seemingly simple unit of value called the "billable ticket." This single metric can turn a predictable operational expense into a source of constant financial anxiety, creating a significant trust gap between the software provider and the business owner.

While this usage-based approach is designed to scale with a business, its mechanics frequently cause it to scale against it, creating wildly unpredictable bills that penalize the very growth the tool is meant to support. The core of the issue is a fundamental misalignment of incentives: the helpdesk provider’s revenue increases with every billable event, including spam, customer confusion that creates multiple tickets for one issue, and inefficient automated replies. The store owner, on the other hand, strives for maximum efficiency, aiming to resolve issues quickly and prevent unnecessary inquiries. This conflict means the platform can profit from the exact operational friction that store owners work tirelessly to eliminate, turning the relationship into an adversarial one. For any store owner focused on maintaining healthy margins, understanding how this billing mechanic truly works is the first and most critical step toward regaining control over a key operational expense and avoiding a nasty end-of-month surprise.

What 'Billable Ticket' Actually Means for Your Invoice

At the heart of the Gorgias pricing model is the "billable ticket," a term whose definition is the primary driver of cost variability and budget headaches. A ticket becomes billable the moment an outbound message is sent from your helpdesk to a customer, a trigger that is far broader than many initially assume. This includes not just a manual reply from an agent, but also any automated response from a pre-set rule, a message sent by a workflow, or a resolution provided by an automation agent. Once that first outbound message is sent, the entire conversation counts as one billable ticket against your monthly allowance, no matter how many subsequent messages are exchanged within a short time frame. This seems straightforward until you realize that common best practices, like setting up an auto-responder to acknowledge every new inquiry, instantly turn every single inbound message, including spam, into a billable event. That simple, helpful "We've received your email" message just cost you money, transforming a customer service best practice into a financial liability.

The financial impact of billing for spam and auto-replies cannot be overstated, creating what is effectively a "spam tax" on your support operations. Even with advanced filters, a growing Shopify store can expect to receive dozens, if not hundreds, of unsolicited messages per month, ranging from phishing attempts to SEO service pitches. If your helpdesk automatically replies to these, each one consumes a billable ticket. For a store on a lower-tier plan facing overages, 100 spam emails could translate into an extra $40 charge for absolutely zero value. This problem extends beyond spam to any automated courtesy notification. A proactive message to a customer about a known shipping delay or a follow-up after a purchase, if sent from the helpdesk, also becomes a billable event, penalizing proactive and thoughtful customer service. From an operational standpoint, you are forced to choose between providing an ideal customer experience and controlling your software costs.

The complexity deepens with how conversations are timed and tracked across channels, creating more opportunities for costs to multiply. Most helpdesks thread conversations logically, but under a per-ticket model, time gates have direct financial consequences. If a customer replies to a conversation that has been closed for a set period, often just 72 hours, the system doesn't simply reopen the old thread; it generates an entirely new billable ticket. A single customer issue that spans a week, perhaps involving a slow-to-respond shipping carrier, can therefore be billed as two or even three separate tickets. For example, a customer emails on Tuesday about a lost package. Your agent replies that they are checking with the carrier. The carrier only responds on Friday, and your agent updates the customer, who replies with a thank you. If that final reply comes after the 72-hour window has closed, a second billable ticket is created to resolve one initial problem.

This multi-ticket problem is exacerbated by modern, multi-channel customer behavior. A customer sending an email and then following up via an on-site chat widget about the same order can easily create two distinct billable tickets, doubling the cost to resolve one underlying problem. Imagine a customer on their mobile phone initiates a chat to ask about return instructions but gets disconnected. Later that day, they send an email from their work computer to ask the same question. Because the system may not automatically merge these interactions from different channels and devices, your team has now spent two billable tickets on a single, simple query. From a store owner's perspective, this structure means your bill is not just a reflection of customer demand but a complex product of your automation settings, your team's response patterns, and your customers' communication habits, factors that make accurate budget forecasting a constant and frustrating challenge.

How Base Plans Create a Bottleneck for Growth

Gorgias offers a tiered structure that appears to provide a clear scaling path, moving from a Starter plan through Basic, Pro, and Advanced tiers, each with a larger billable ticket allowance for a higher monthly fee. For instance, the Basic plan might include 300 tickets for around $60 per month, while the Pro plan offers 2,000 tickets for approximately $360 per month. The problem is that for any Shopify store with real momentum, the chasm between these tiers is a financial trap. The price jump from Basic to Pro is a staggering 6x increase in monthly fixed cost, while the ticket allowance increases by about 6.7x. For a business experiencing steady, linear growth, such a massive leap is entirely misaligned with its revenue curve, forcing a premature and inefficient allocation of capital just to avoid punitive fees.

A successful TikTok campaign or a seasonal sales spike can easily propel a store on the Basic plan from 250 tickets one month to over 600 the next. This surge doesn't just mean you've outgrown your plan; it means you've plunged into the overage gap, where the platform's economics shift dramatically against you. With each extra ticket costing around $0.40, that sudden success would add $120 in overages (300 tickets x $0.40), more than tripling the base cost to $180 overnight. A store owner looking at this bill is faced with a terrible choice for the following month: risk another volatile overage charge, or upgrade to the $360 Pro plan, effectively pre-paying for 1,400 tickets of capacity they may not consistently need for another six months.

The ticket limits on the lower-tier plans are often too restrictive for a business with any real traction, while the price jump to the next tier represents a significant and often premature increase in fixed costs. A store consistently hitting 500-700 tickets a month is caught in an impossible position: staying on the Basic plan means incurring hundreds of dollars in volatile overage fees, yet upgrading to the Pro plan feels like pre-paying for 1,300 tickets of capacity they don't consistently need. This forces store owners to manage their business based on software limitations rather than market opportunities. One might even hesitate to run a promising flash sale, knowing that the resulting support volume could make the entire promotion unprofitable due to helpdesk overages. This creates a "growth ceiling" imposed not by the market, but by a key operational tool.

To make matters worse, many platform-native features that drive real value, such as revenue analytics and customer satisfaction surveys, are locked behind the more expensive Pro and Advanced plans. This forces an upgrade not for ticket volume but for essential business intelligence, effectively creating a "success tax" where the reward for growth is a disproportionately higher and more complex software bill. For a store owner, knowing which support interactions lead to sales (revenue attribution) or how customers feel about their service (CSAT scores) is not a luxury; it is fundamental data required to run the business intelligently. By gating these features, the pricing model compels you to pay for a massive ticket allowance you don't need just to unlock the analytics required to prove and improve your team's ROI, further cementing the financial inefficiency.

The AI Add-On: Paying Twice for the Same Conversation

The most confusing and costly layer of the Gorgias pricing structure is its approach to AI automation, marketed under its Automate features. The platform's AI Agent is positioned as a powerful tool to reduce manual workload by efficiently resolving common customer inquiries like "Where is my order?" However, it is a separate, usage-based add-on with a billing model that results in paying for the same customer interaction twice. This approach directly contradicts the primary promise of automation, which is to handle repetitive tasks at a lower cost than a human agent. Instead of creating efficiency, it adds another layer of metered billing that runs in parallel to the primary ticket counter, making cost forecasting even more difficult.

Gorgias charges a per-resolution fee for every conversation the AI handles autonomously, typically costing between $0.90 and $1.00 per successful resolution. The critical detail that many store owners miss in the fine print is that each of these AI-resolved conversations also consumes one billable ticket from your plan's monthly allowance. This "double-billing" mechanic means an automated resolution is not a cost-saving event; it is a separately metered transaction that is billed on two different meters simultaneously. A single "Where Is My Order?" (WISMO) question answered by the AI costs you one billable ticket from your plan *plus* an additional fee of nearly a dollar. This practice fundamentally undermines the value proposition of automation and creates a scenario where the true cost of an automated interaction can exceed that of a human-handled one.

Consider a store on the Pro plan, paying for its 2,000-ticket allowance. If its AI Agent successfully resolves 1,000 common customer questions in a month, the store owner pays not only for those 1,000 tickets as part of their helpdesk plan but also an additional fee of roughly $950 for the AI resolutions themselves. The financial incentive structure becomes completely inverted: the more effective your automation is at deflecting work from your human agents, the higher your bill becomes. This runs directly counter to the foundational promise of automation, which is to reduce operational costs as it handles more volume with greater efficiency. The helpdesk provider's revenue per automated ticket is now significantly higher than it is for a manually handled one, creating a clear conflict of interest with the store owner's goal of cost reduction.

Instead of celebrating the successful deflection of 1,000 manual tickets, the store owner must now account for a bill that is nearly $1,000 higher than anticipated, all while their primary ticket allowance has been halved. This leaves only 1,000 tickets for the month to be handled by human agents before the store starts incurring *additional* overage fees on top of the already-inflated bill. Every simple "WISMO" query that the AI resolves adds to two separate running tallies, one for the ticket and one for the AI's work. This makes the "true" cost of a single automated ticket significantly higher than either the base ticket cost or the AI resolution fee alone, creating a bizarre scenario where a store's investment in efficiency directly contributes to the unpredictability and inflation of its monthly costs.

Overages: The Unpredictable Charge That Breaks Budgets

The single element that introduces the most volatility into Gorgias pricing is the overage fee, a mechanism that can single-handedly derail a carefully planned budget. When a store exceeds its monthly allotment of billable tickets, the platform doesn't stop working or warn you in a meaningful way. Instead, it begins charging for each additional ticket at a predetermined, and often punishing, rate. For Starter and Basic plans, this rate is frequently around $0.40 per ticket, while for Pro and Advanced plans, it might be slightly lower at approximately $0.36. While these per-ticket costs may seem small in isolation, they accumulate with alarming speed, especially during periods of high customer activity like a new product launch or the Black Friday Cyber Monday (BFCM) holiday season. A store that is otherwise financially healthy can see its helpdesk bill double or triple in a single month due to an unanticipated, but welcome, surge in customer orders and inquiries.

The true danger of overages lies in their compounding unpredictability. A store on the Pro plan paying $360 for 2,000 tickets can feel secure in its budgeting. However, if a BFCM promotion drives a 65% increase in support volume, a typical surge for the period, to 3,300 tickets, the store is now liable for 1,300 overage tickets. At $0.36 each, that’s an extra $468, instantly more than doubling the base cost to $828. This penalty is levied for the sin of having a successful sales period, directly tying your highest revenue moments to your highest software costs and eroding the profitability of your most important campaigns. The lack of hard limits or clear, unavoidable warnings means that by the time you realize you've gone over your allowance, the financial damage has already been done.

Now, layer in the AI add-on, which also comes with its own overage system. If, during that same BFCM period, the AI handles 1,500 resolutions against an included allowance of, say, 1,000, that’s another 500 AI overage fees at approximately $1.00 each, adding another $500 to the bill. A predictable $360 monthly subscription has suddenly ballooned to over $1,328 ($360 base + $468 ticket overages + $500 AI overages). This is not a hypothetical edge case; it is the standard, painful experience for many successful ecommerce businesses whose tools punish them for the very growth they are striving to achieve. This forces finance teams to set aside large, inefficient cash reserves to cover potential software penalties, making a mockery of agile budgeting and turning a store's highest-revenue periods into its most expensive support months.

Calculating Your True Gorgias Cost: A Framework

To move past the advertised sticker price and understand what Gorgias will actually cost your business, you need a realistic framework that accounts for all three layers of its pricing model: the base plan, the AI automation add-on, and the ever-present threat of overages. First, start by ignoring the plan names and focusing exclusively on your actual monthly ticket volume. The only way to do this is to analyze your historical data. Pull support data from the last six to twelve months to find your average, but more importantly, you must identify your absolute peak month. Your support tool budget must be built to withstand your busiest periods, not just your quietest ones, because the peaks are what trigger financial penalties. Budgeting for your average volume is a guarantee that you will be hit with overage fees during your most critical sales events.

Once you have your peak month data, you must project it forward. If your peak volume last year was 900 tickets during BFCM and your business has grown 30% year-over-year, your new projected peak is nearly 1,200 tickets (900 x 1.3). This number, not your 400-ticket monthly average, is the true baseline for your calculation. A plan with a 300-ticket limit is not a viable option; it's a financial trap waiting to spring. You must select a plan tier that can comfortably contain your absolute highest projected volume. In this case, with a projected peak of 1,200 tickets, the Pro plan (2,000 tickets) is the only logical choice to mitigate the risk of extreme overage fees, immediately setting your base cost at $360 per month, not the $60 you might have hoped for.

Next, you must forecast your use of automation and its associated costs. To do this properly, perform a content audit of your last 1,000 support tickets and categorize them to find what percentage are simple, repetitive questions like "where is my order?" or "what is your return policy?" If you find that 40% of your tickets are these highly repetitive inquiries, you can estimate your automation potential. Applying this to your peak volume, you can expect the AI to resolve 40% of your 1,200 peak tickets, which equals 480 resolutions. You must now calculate the cost for those 480 automated resolutions (480 x ~$0.95 = $456) and add that to the cost of the Pro plan needed to cover all 1,200 tickets ($360). Your new, more realistic monthly cost is already $816.

Finally, you must factor in a buffer for overages, because even the best forecasts can be wrong. A single viral social media post, an unexpected mention from a major influencer, or a minor issue with a shipping carrier can cause ticket volume to surge beyond your projections. A conservative but prudent approach is to budget for a 15-20% variance in ticket volume for these unexpected events. For a 1,200-ticket peak projection, a 20% buffer means planning for an additional 240 tickets. Since your Pro plan covers the first 2,000, these would not incur overages unless the surge is truly massive. However, this framework reveals the true cost: by adding your peak-volume base plan ($360), your estimated AI resolutions ($456), and a contingency for variance, you arrive at a much more realistic figure of over $800 for your monthly support spend, a number vastly different from the advertised price.

Beyond Per-Ticket Pricing: The Flat-Rate Alternative

The inherent complexity and unpredictability in per-ticket and per-resolution billing models have led many frustrated store owners to seek a simpler, more transparent alternative: flat-rate pricing. This model completely decouples a store’s support costs from its daily or monthly fluctuations in customer conversations. Instead of paying for each ticket, each AI resolution, and each overage, you pay a single, fixed monthly price for a clear tier of service. This approach provides complete and total cost predictability, allowing you to budget with absolute certainty. A sudden spike in customer engagement from a viral post is celebrated as a pure business win, not dreaded as a pending financial penalty on your next software invoice. This shift in mindset from risk mitigation to growth enablement is transformative for a store owner.

This move toward predictability reflects a broader market correction in the software industry. According to the 2023 Pricing & Packaging Report from venture capital firm OpenView, while usage-based pricing has grown in popularity, its single greatest challenge is that "customers hate unpredictability". The report notes that the most successful companies are moving towards hybrid models that combine usage components with predictable fixed fees or, even better for customers, offering pure flat-rate plans. These models offer the "best of both worlds" for customers seeking budget certainty while still allowing them to access powerful tools that scale with their business. For a growing ecommerce brand, this stability is not a luxury; it is a strategic advantage that allows for more confident and aggressive investment in growth.

This is the model we've built at Arbyn, because we believe your helpdesk should be a fixed, predictable operational expense, not a variable cost that punishes your success. Arbyn offers three simple, flat-rate plans with no hidden fees, no overages, and no separate charges for AI. This aligns our incentives directly with yours; our goal is to help you resolve customer conversations as efficiently as possible, not to maximize the number of billable events. All AI and automation capabilities are included in the single monthly price, reflecting the true promise of automation: to reduce your costs and workload, not to create a new, confusing billing stream. Our success is tied to providing you with a stable, effective platform that you can rely on, month after month.

The Arbyn Starter plan is permanently free for up to 150 AI conversations per month, giving new and small stores access to a full-featured support and sales agent from day one without financial risk. For growing stores, Arbyn Growth provides 500 conversations per month for a flat $59. For stores with higher volume, Arbyn Agent offers unlimited conversations for a flat $99 per month, no usage calculations, no resolution fees, and no overages, ever. Every feature we offer, from analytics to advanced integrations, is included in every plan because we believe business intelligence is a necessity, not a premium add-on. If you reach your plan's conversation allowance, AI replies simply pause until the next billing cycle, guaranteeing you will never receive a surprise bill. This model aligns our success with yours, providing a powerful tool that supports your growth without penalizing you for it. If you're tired of complex invoices and unpredictable costs, you can install Arbyn for free on the Shopify App Store and experience the stability of a true flat-rate platform.
---
## Pricing

- **Arbyn Starter** - $0/month, permanently free. 150 conversations / month. Resets 1st of each month.
- **Arbyn Growth** - $59/month flat. 500 conversations / month. Resets 1st of each month. Or $600/year (just under two months free, saves $108, 15% off).
- **Arbyn Agent** - $99/month flat. Unlimited conversations. Or $990/year (two months free, saves $198, 17% off).
- **There is no trial.** Billing starts immediately on any paid plan. The free Arbyn Starter plan is permanent.
- The conversation cap is the only difference between plans. There is no feature gating.

## Channels

Live today: **support email** and **on-site live chat**. That is the complete list.

SMS, Instagram DMs, Facebook Messenger, WhatsApp and Voice are on the roadmap and are NOT live. Arbyn does not edit orders or change line items. Money-moving actions (cancel, refund, discount, gift card, reship, return) require the store owner's approval, and then Arbyn performs them. Running them fully autonomously is a beta authorization and is in development. Shipping address changes are already autonomous.

## What Arbyn does on a Shopify order

- **Change the shipping address**: Live. Arbyn does this on its own. Arbyn updates the shipping address on the Shopify order itself, inside the conversation, and writes the change to the order timeline.
- **Cancel an order**: Live. You approve it, then Arbyn cancels the order. Anything that moves money waits for the store owner's approval. That is a deliberate control, not a missing feature. Once you approve, Arbyn fires Shopify's order cancellation itself and confirms it to the customer.
- **Issue a refund**: Live. You approve it, then Arbyn issues the refund. Arbyn prepares the refund against the original payment method and sends it to you. On approval it files the refund in Shopify. You can cap the value it is allowed to prepare, per channel.
- **Apply a discount**: Live. Arbyn creates a real Shopify discount and applies it to the cart, handing the shopper a checkout with the code already on it. It can also issue a discount code on an order once you approve it.
- **Send a gift card, or reship an order**: Live. You approve it, then Arbyn does it. Arbyn creates the gift card, or raises the replacement order, in Shopify once you approve.
- **Start a return**: Live. You approve it, then Arbyn opens the return. Arbyn opens the return in Shopify on your approval.
- **Look up a gift card or store-credit balance**: Live. Arbyn does this on its own. "Do I have store credit left?" is a question most support tools answer with a human. Arbyn reads the balance itself, for a verified customer or from the code they give you, and reports the masked card, the balance and the expiry. If there is no card, it says so rather than guessing.
- **Handle a subscription question**: Live. You choose what it does. Arbyn knows which of your products are sold as a subscription, shows that on the product card in the conversation, and sends a subscriber to their subscription management page to pause, skip or cancel. It answers how your subscriptions work from your own knowledge, but it does not read an individual customer's contract, so it will not state their renewal date or status. Most cancels are a customer with product piling up, and the fix is getting them to the page where they can slow the cadence down. Reading the contract itself is on the roadmap.
- **Answer support email and live chat**: Live. Arbyn reads every inbound support email and every chat, works out the intent, pulls the live Shopify context, and replies in your brand voice.

Money-moving actions (cancel, refund, discount, gift card, reship, return) require the store owner's approval, and then Arbyn performs them. Running them fully autonomously is a beta authorization and is in development. Shipping address changes are already autonomous.