Most Shopify merchants on per-ticket support billing discover the overpayment by accident — usually when November’s invoice arrives. This article gives you the formula to know in advance, a worked 12-month cost example, and a concrete checklist to switch cleanly.
Per-ticket billing was designed for a world where every support ticket required a human agent to read, think, and reply. That model made sense in 2015. In 2026, 50–70% of Shopify support tickets are queries that a well-configured AI can resolve in seconds: “Where is my order?”, “Can I return this?”, “What size should I get?”
Per-ticket billing does not care whether a human or AI resolved the ticket. You pay the same rate either way. That asymmetry is the problem. As AI handles more tickets automatically, your resolution cost per ticket drops toward zero — but your billing cost per ticket stays fixed.
AI resolution cost: near zero per ticket. Per-ticket billing cost: $0.18–$0.40 per ticket. The gap widens with every ticket AI handles that you are still paying human-era prices for.
The second problem is variance. Shopify order volume is not flat. BFCM, product launches, and supplier issues create ticket spikes that can triple a typical month’s volume. On per-ticket billing, those spikes land as surprise invoices. On flat-rate billing, they cost nothing extra.
Before running a full 12-month analysis, use this formula to get a quick signal:
Your “effective cost per ticket” is not the advertised per-ticket rate. It is (total support spend last 12 months) divided by (total tickets last 12 months). Pull both numbers from your helpdesk dashboard. The effective rate is usually higher than the nominal rate because plan base fees increase the cost of lower-volume months.
Consider a Shopify apparel store doing 600–800 orders per month in steady months, with a 20% contact rate (typical for a store with an established FAQ and smooth fulfilment). They are on Gorgias Pro at $360/month, which includes 2,000 tickets per month. Overage is charged at $0.36 per ticket above that limit.
Here is their ticket volume at a 20% contact rate, with a BFCM surge in November and a post-holiday returns spike added into January:
| Month | Orders | Est. tickets | Overage tickets | Monthly cost |
|---|---|---|---|---|
| Jan (returns) | 700 | 360 | 0 | $360 |
| Feb | 650 | 130 | 0 | $360 |
| Mar | 680 | 136 | 0 | $360 |
| Apr | 720 | 144 | 0 | $360 |
| May | 760 | 152 | 0 | $360 |
| Jun | 780 | 156 | 0 | $360 |
| Jul | 800 | 160 | 0 | $360 |
| Aug | 820 | 164 | 0 | $360 |
| Sep | 860 | 172 | 0 | $360 |
| Oct | 1,100 | 220 | 0 | $360 |
| Nov (BFCM) | 4,200 | 840 | 0 | $360 |
| Dec | 3,100 | 620 | 0 | $360 |
| Annual total (20% contact rate) | $4,320 | |||
At 20% contact rate, ticket volume stays under 2,000 in every month. The store pays $4,320 per year with zero overage. Gorgias Pro is a reasonable value at this volume.
Now change one variable: their contact rate rises to 30% after a batch of products with quality issues arrives in Q3 and persists through the holiday season. This is a common scenario — a single supplier problem or carrier outage can double contact rates for 4–8 weeks.
| Month | Orders | Tickets (30%) | Overage tickets | Overage cost | Monthly cost |
|---|---|---|---|---|---|
| Jan–Aug | ~710 avg | ~213 avg | 0 | $0 | $360 each |
| Sep (issue starts) | 860 | 860 | 0 | $0 | $360 |
| Oct (issue ongoing) | 1,100 | 1,100 | 0 | $0 | $360 |
| Nov (BFCM + issue) | 4,200 | 4,200 | 2,200 | $792 | $1,152 |
| Dec (returns + issue) | 3,100 | 3,100 | 1,100 | $396 | $756 |
| Annual total (30% contact rate — stressed scenario) | $5,268 | ||||
Two months of elevated contact rate — a realistic scenario for any Shopify store with a supplier hiccup or carrier failure — add $948 above the base plan. This is the per-ticket billing trap: costs spike precisely when your operation is already under stress and you have the least bandwidth to deal with a budget surprise.
A flat-rate AI support plan at $149/month would cost $1,788 per year regardless of contact rate — saving $2,532 in the baseline scenario and $3,480 in the stressed scenario.
Switching support platforms carries real risk if done carelessly. Customers mid-thread get confused. Response times can slip. Here is a staged process that keeps service quality intact throughout the transition.
Before switching anything, download a full 12-month export from your current helpdesk: ticket count by month, average first-response time, CSAT score if tracked, and a breakdown of ticket types if you use tags or categories. This data serves two purposes: it gives you the numbers for the break-even formula, and it teaches the new system what your real support patterns look like.
Most Shopify stores find that 3–5 query types account for 60–70% of all tickets: order status, return and exchange requests, shipping delays, product sizing questions, and discount code issues. Write out the ideal resolution for each in plain language. This becomes the AI’s initial knowledge base. Skipping this step is the most common reason AI resolution rates disappoint during onboarding.
Do not cut over immediately. Route a portion of new tickets to the new system — start with 20–30% — while keeping your existing helpdesk active for the rest. Monitor AI resolution rate, escalation rate, and spot-check 10 AI-resolved tickets per day for accuracy. Widen the percentage as confidence builds. Only decommission the old system when the new one is handling 100% of volume with acceptable metrics.
Export all saved replies, macros, and canned responses from your current tool. These represent accumulated knowledge of what works for your customers. Port them into the new system as AI-accessible response templates. Shopify-specific macros that pull order numbers, tracking codes, or return label links need to be remapped to the new integration. Test each one manually before going live.
Never switch support platforms in October, November, or December. The safe window for most Shopify stores is February through August. If you are already approaching BFCM season, wait. A support platform switch during peak is a customer-experience risk that no annual cost saving justifies. Plan the switch now; execute it in a quiet month.
Not all flat-rate plans are equivalent. Confirm these capabilities before signing up:
Flat-rate AI support is not right for every store. Per-ticket billing remains the better choice when:
One flat monthly rate. AI handles routine Shopify queries around the clock. Human escalation when it matters. No per-ticket surprises, ever.
See the Founding Support plan →Per-ticket billing made sense when every ticket needed a human. Today, AI resolves the majority of routine Shopify support queries at near-zero marginal cost — but per-ticket plans charge you full price regardless. The economics are straightforward: run the 12-month analysis with your real ticket data, calculate your break-even, and check whether your peak months are generating overage you are absorbing quietly.
If the math shows savings, the five-step playbook above gives you a staged, low-risk path to switch. The mistake merchants make is waiting until a bad BFCM invoice forces the decision under time pressure. Do it in a quiet month.