Gorgias alternative for stores beyond Shopify

By the Onsites AI team · Last updated August 28, 2026 · 5-minute read

Gorgias built the best-known e-commerce support desk by optimizing for one platform: order data beside the thread, refund and edit actions inside the ticket, macros that pull the Shopify context automatically. For a Shopify store with high ticket volume, it works — and this guide says so plainly. The market it leaves behind is wider than it looks: WooCommerce runs a large share of the web's stores, Etsy and other marketplaces carry their own enormous seller ecosystems, and custom stacks power the rest. For all of those, the Shopify-first desk degrades into an integration exercise while still billing its distinctive meter: per-ticket pricing on top of per-seat tiers — the volume meter this pricing guide spends a full walkthrough on, because busy months are exactly when a store's support bill spikes. The alternative examined here is platform-neutral and unmetered by ticket: orders and customers in the thread from WooCommerce, CSV or API, three seats free, $15 beyond, and the commercial loop — quotes to invoices — native to the desk.

What e-commerce support actually needs

Strip the vendor names and the list is short. Order context in the thread: "where is order #1041?" answered without a tab switch — status, items, address. Agent actions: resend, refund, adjust — the fewer places a reply ends, the fewer the errors. Channel spread that matches buyers: email and widget certainly, but also WhatsApp and Instagram-era messaging where purchase questions actually arrive. Macros and automation that know commerce: "where is my order" flows that read the order, not just the phrase. Seasonal elasticity: Black Friday multiplies tickets 5–10×; a desk that meters per ticket turns your best month into your most expensive one. Every e-commerce desk claims this list; the differences are which platforms get native depth, which get integrations — and what the meter does in November.

Beyond Shopify, honestly compared

WooCommerce: the Shopify-first desk connects via integration; order lookups degrade to a secondary panel and agent actions (refunds especially) leave the thread. A platform-neutral desk treats Woo as first data: orders and customers join the thread by API or CSV, and commercial follow-ups — requote after a size swap, amended invoice — happen where the question landed. Etsy: marketplace sellers live inside Etsy's rules; what they need is a desk that reads Etsy's exports and answers across email and messaging without pretending to refund inside Etsy. Custom stacks: API-first order sync beats any prebuilt connector. The deeper difference is structural: the Shopify-first product's CRM ambitions end at the store; the metered desk is itself a CRM with conversations attached — accounts, pipeline, order threads — which out-of-platform stores need the moment sales runs anywhere other than the storefront.

The per-ticket meter, at retail volume

Gorgias prices by ticket count inside tiered plans — a model tuned for stores with steady, high volume, where it reads as simple. The strain is the shape of retail itself. A store doing 800 tickets monthly in February may do 6,000 in November; under per-ticket tiers, November's bill climbs the tier ladder precisely when margins are thinnest from ad spend and discounts — and support cost becomes a function of success. The unmetered desk refuses that trade: no ticket meter at any volume, seats at three-free-then-$15, storage at $1 a gigabyte beyond 100 MB, AI at prepaid credit prices. The honest comparison asks one question: plot your 12-month ticket curve, then price both meters on it. Stores whose curve is flat may be fine either way; stores whose curve is a holiday spike — most of them — find the flat meter buys the same busy month for the same seat price. The models guide works the full derivation.

A retail season, on both meters

One worked month makes the pricing conversation concrete. A mid-size store's November: 6,000 tickets against 800 in February, four agents answering across email, widget and WhatsApp. On the per-ticket desk: the tier ladder climbs — the flood moves the plan up (or adds an overage line), the month's support bill roughly triples alongside ad spend and discount erosion, and the finance review asks why success cost so much. On the seat-metered desk: the same flood arrives to four seats (one free, three paid — $45) with storage inside its band for text-first commerce mail, AI drafts and summaries prepaid at credit prices that add single-digit dollars for the month. Same tickets, same humans, same outcome times on the response benchmarks. The seat bill stayed flat through the store's best month: that inversion — cost ignoring volume — is the structural difference no feature list conveys, and it is the reason retail support budgets drift platform-neutral as they mature.

Migrating the storefront team

The move is a week, staged. Data: tickets and customers export; orders sync or import from Woo/CSV; the widget snippet swaps. Macros: Gorgias macros translate well — their variables re-bind to the desk's fields in an afternoon, and the commerce-conditioned ones ("WISMO" flows) re-express against real order data. Channels: reconnect email first (IMAP keeps history — the setup guide), then add WhatsApp or the messenger your buyers actually use; most stores discover 20–40% of "email volume" was buyers being funneled to the channel the desk preferred. Habits: the thread becomes the place refunds follow up and requotes happen; a week of hands settles it. The check-in at day 30 is usually the November memory: the flood arrived, the seat bill didn't.

When Gorgias deserves to win, honestly

Keep the fair-loss column full: a pure-Shopify store with heavy ticket volume, deep Shopify workflow needs (partial refunds from the ticket, native product edits, Shopify Flow integration) and a flat ticket curve is Gorgias's exact customer — its order-side actions are genuinely native and its macros are built for the job. Teams whose entire support identity is Shopify admin will feel the platform-neutral desk as less "inside" their store. The case for switching is the negative space: stores beyond Shopify, curves that spike seasonally, desks that need CRM and invoicing in the thread rather than beside it, and any team that wants the meter priced in seats rather than smiles. Run your own ticket curve against both meters; the desk whose bill ignores November is usually the one worth renewing.