The short version.

• Gorgias pulls your WooCommerce orders onto the ticket. It will not touch your phone line.
• On WooCommerce the integration is view-only: agents see the order, then log into WordPress to refund, cancel, or edit it. The Gorgias AI Agent does not run on WooCommerce at all.
• Built for founders and CX leads at $10M-$100M DTC brands running WooCommerce with a visible phone number. If routine calls eat your reps' day, the phone is the part to fix.

You wired Gorgias into your WooCommerce store expecting the same thing the Shopify case studies show, and the order data does land on the ticket. Then a customer calls about a refund, your agent opens the ticket, sees the order, and still has to go log into WordPress to actually do anything. That is the integration working as designed, not a bug.

This guide walks the honest version: how you connect Gorgias to WooCommerce, what order data shows up on a ticket, and exactly where the WooCommerce integration stops compared to the Shopify one. I run AI phone support for DTC brands, and I connected a WooCommerce store to Gorgias, made a test call, and watched the phone channel fall straight through the integration. If you run customer experience at a WooCommerce brand doing $10M-$100M and your reps are drowning in the same order-status calls, book a 30-min call and we'll map where your calls are leaking.

Gorgias on WooCommerce vs Shopify vs adding a phone layer

Here's the whole thing in one table before the deep dive. The native integration does real work, but the depth gap between WooCommerce and Shopify is wide, and neither one answers a phone.

The pattern is simple. Gorgias is a strong email, chat, and social helpdesk, and on Shopify it is also a light order-management console. On WooCommerce it is the helpdesk minus the order actions minus the AI. And on every platform, including Shopify, it never picks up the phone.

How to connect Gorgias to WooCommerce

You can connect a WooCommerce store to Gorgias in about ten minutes, and the historical order sync runs on its own once you authorize. There are two paths you'll see referenced, and it helps to know which one you're on.

The current native path lives inside Gorgias, no plugin required:

• Open the app. In Gorgias, go to Settings, then App Store, then All apps.
• Find WooCommerce. Search for WooCommerce, select it, and click Connect App.
• Authorize. Click Authorize App, enter your full WooCommerce domain including the https:// prefix, then confirm on the Authorize App Page.
• Let it sync. Historical customers and orders import automatically once the connection is live.

You need an Admin role in Gorgias and Admin permissions in WooCommerce to do this, per the Gorgias WooCommerce documentation. You can connect more than one WooCommerce store to the same Gorgias account.

The older path, which still shows up in connector tools like Zapier and Pipedream, runs over the WooCommerce REST API. If you're building a custom workflow rather than the native connection, you generate keys yourself: in WooCommerce, go to WooCommerce, then Settings, then Advanced, then REST API, and add a key. Pick the user, set the permission level to Read, Write, or Read/Write, and generate it. WooCommerce hands you a Consumer Key and a Consumer Secret, which is how any external app authenticates into your store data, per the WooCommerce REST API docs. The native Gorgias integration handles this handshake for you. The manual key path matters only when you're wiring up something custom that the native connector doesn't cover.

Either way, what you've built is a read pipe from WooCommerce into the ticket. Keep that word in mind: read.

One setup note worth flagging before you go live. The native connection matches customers by email, so if a caller or emailer reaches out from a different address than the one on their order, Gorgias won't auto-link them and your agent is back to asking for an order number. It's a small thing, but it's the kind of friction that adds up across a few hundred tickets a week, and it's worth telling your team about during onboarding rather than letting them discover it mid-call.

What order data actually shows up on the ticket

Once connected, a WooCommerce customer's profile and order history sit in the ticket sidebar, so your agent stops asking "what's your order number?" on every call and chat. When a message comes in, Gorgias matches the customer by email and surfaces their record next to the conversation.

What lands on the ticket:

• Contact details. Email and phone number on file.
• Order info. Total order value, payment status, and fulfillment status.
• Line items. The exact products they bought.
• Addresses. Shipping and billing on the order.

The sync is live. Per Gorgias, "whenever an order or a customer profile is created or changed in WooCommerce, it's immediately updated in Gorgias as well." Their own framing on the WooCommerce helpdesk page is that you "view customer details like email address, order information, and fulfillment status right inside the ticket view." That part is genuinely useful. It kills the tab-switching your reps do a hundred times a day just to answer "where's my order", and it's the same context an order-status lookup needs to resolve a call on the first try.

So the context is there. The question is what your team can do with it.

Where the WooCommerce integration stops

This is the line that surprises most operators: on WooCommerce, Gorgias shows the order but can't change it. Per the Gorgias documentation, "you can't initiate any actions on WooCommerce orders (create, edit, cancel, refund)." Your agent sees the refund request, sees the order, and then opens the WooCommerce admin in another tab to actually issue the refund.

A few more ceilings worth knowing before you commit:

• No order actions in-ticket. Refunds, cancellations, edits, and address changes all happen in WordPress, not Gorgias.
• No store data in Rules. WooCommerce order data can't be used as a condition in Gorgias automation Rules.
• Automate isn't compatible. Gorgias states its Automate features don't work with the WooCommerce integration.
• No AI Agent. Per Gorgias, "AI Agent is not supported on BigCommerce, Magento or WooCommerce stores." The AI Agent requires a Shopify store. This is confirmed across third-party breakdowns like eesel's WooCommerce guide too.

That last one is the big one. The whole reason brands buy Gorgias in 2026 is the automation, and on WooCommerce you're paying for the helpdesk shell without the engine. You still get the inbox. You don't get the AI that's supposed to clear 30 to 40% of your routine WISMO tickets, because WISMO is 30-40% of tickets and over 50% at peak, per Salesforce. On Shopify, Gorgias plans run from roughly $10 to $750 a month with per-ticket overage, and the AI resolution fee sits on top at around $0.90 to $1.00 per resolved conversation. On WooCommerce you pay the helpdesk plan, and the AI resolution pricing is moot because the AI Agent won't run. If WooCommerce's own limits are part of why you're weighing this, a WooCommerce-to-Shopify migration is one route, but most brands at this size aren't replatforming just to unlock a helpdesk feature.

Operationally, the view-only ceiling changes how a ticket actually closes. On Shopify, an agent reads the refund request, clicks refund, and replies, all in one window. On WooCommerce, the same agent reads the request in Gorgias, switches to the WooCommerce admin, finds the order again, processes the refund there, switches back, and writes the reply. It's the same outcome with twice the clicks, and it's exactly the kind of repetitive motion that burns reps out on a busy Monday. The data sitting on the ticket helps them answer faster, but it doesn't help them act faster.

None of this makes Gorgias a bad choice for WooCommerce. It makes it a partial one. The routine load stays on your reps, and on the phone it stays unhandled entirely. If you want to compare that load against an AI that actually handles it, book a 30-min call and we'll do the math against your current setup.

"My customers also feel like it's a normal person. They feel like they can communicate if they have questions."
Claudia Droge, TechCraft Studio

The gap nobody mentions: your phone line

Every Gorgias integration, on Shopify and WooCommerce alike, has the same blind spot: it doesn't answer the phone. Gorgias routes email, chat, and social into one inbox. The calls that come into your WooCommerce store's number aren't in that picture at all.

For a lot of DTC brands, that's where the real money leaks. The order-status caller who can't get through doesn't open a ticket. They hang up. Businesses answer only 37.8% of their inbound calls, with another 37.8% rolling to voicemail, per AmbsCallCenter. And 85% of callers who can't reach a person never call back, with 62% switching to a competitor, per PCN. Your Gorgias dashboard never shows you that number because the call never became a ticket.

This is the part WooCommerce brands feel hardest after 6pm and on weekends. The phone backlog isn't visible in the helpdesk, so it doesn't get triaged. It just becomes a quiet stream of missed orders and a Trustpilot review that says "couldn't reach anyone." It's the exact case for 24/7 phone coverage, and it's why after-hours answering is usually the first thing brands fix once they can see the gap.

WashCo, a Shopify brand we launched, recovered $22,664 in its first 7 days on the phone. That revenue existed before. It was just walking into voicemail.

Ringly: the AI phone layer for WooCommerce calls

Ringly.io is AI phone support for ecommerce brands. The phone shouldn't be a tax on your support team, but on WooCommerce it usually is, because Gorgias never touches it and you can't justify a night shift to answer "where's my order" at 11pm. Acting as an AI receptionist for ecommerce, the AI takes the routine inbound calls so your reps can focus on the work that actually moves revenue.

The AI answers inbound calls 24/7. It finds orders in your store, checks order status, processes returns and exchanges, answers product questions from your knowledge base, and rescues abandoned carts with outbound follow-up. Across 50+ active brands, the AI resolves 73% of calls on its own at roughly $0.42 per resolved call, versus the $7 to $16 a human-handled call runs at a BPO. The calls that need a person escalate cleanly with a smart transfer, and the call gets logged so it shows up alongside the rest of your support history instead of vanishing.

Here's the part that matters for this guide: Ringly doesn't replace Gorgias. You keep your number, your WooCommerce store, your Gorgias inbox, and your team. Ringly sits in front of the phone line as an AI customer service phone agent, handles the routine calls Gorgias was never going to see, and hands off the hard ones. Plans run Grow at $349/mo and Pro at $799/mo (see full pricing), with a 65% resolution guarantee and setup live in under an hour.

The point isn't to swap your helpdesk. It's to plug the one channel your helpdesk leaves on the floor. If you'd rather keep the phone on your reps, that's a fair call too. But most WooCommerce brands at this size are paying people to answer the same five questions all day.

What this costs vs what it saves

Take a WooCommerce brand running a 6-rep CS team to cover the phone and the queue:

That's roughly 70% of repeatable calls, the order status, returns, and product questions your team answers over and over, routed to the AI. The other 30%, the genuinely complex calls, still go to your reps, who now have time to solve them. The numbers are illustrative, and your exact figure depends on call volume, but the shape holds across the brands we run.

Want to put your real call volume against this? Book a 30-min call and we'll do the math live.

Frequently asked questions

Does Gorgias support WooCommerce, or is it Shopify-only? Gorgias supports WooCommerce with a native integration that pulls customer and order data onto the ticket. It's real, but it's shallower than the Shopify version. The order actions and the AI Agent are Shopify-only.

Can my agents refund or cancel a WooCommerce order from inside Gorgias? No. The WooCommerce integration is view-only. Per Gorgias, you can't create, edit, cancel, or refund WooCommerce orders from the ticket, so agents do those actions in the WooCommerce admin.

Does the Gorgias AI Agent work on WooCommerce? No. Per Gorgias documentation, the AI Agent is not supported on WooCommerce, BigCommerce, or Magento, and requires a Shopify store. On WooCommerce you get the helpdesk inbox without the AI automation.

How do I connect Gorgias to WooCommerce? In Gorgias, go to Settings, App Store, All apps, search WooCommerce, click Connect App, then Authorize and enter your full store URL with https://. You need Admin roles in both Gorgias and WooCommerce, and historical orders sync automatically.

Does Ringly replace Gorgias? No. Ringly handles your inbound phone calls, which Gorgias doesn't touch on any platform. You keep Gorgias for email, chat, and social, and Ringly escalates and logs the calls that need a human into your existing workflow.

How fast can I get Ringly live on a WooCommerce store? Live in under an hour. You add your store, your docs, and your knowledge base, and the AI starts answering calls. There's a 65% resolution guarantee, so if it resolves under 65% of calls in 90 days, we refund the last 3 months.

Talk to us

If your WooCommerce store has a phone number and it goes quiet after 6pm, that's the leak. The Gorgias integration will never show it to you, because the call never becomes a ticket. A 30-min call is the fastest way to see what your store is leaving on the table after-hours.

The 3-layer guarantee.

1. Live in 14 days or it's free until launched.
2. 65% resolution in 90 days or we refund the last 3 months of subscription fees.
3. We keep working free until we hit 65%.

Ruben (Ringly co-founder) takes these calls personally.

Book a 30-min call