Add an AI Chatbot to Your WooCommerce Store

What connecting WooCommerce gets you

A WooCommerce store gets three questions over and over, and each one costs money in a different way. Pre-sale questions — will it fit, is it in stock, when does it arrive — decide whether a full cart becomes an order. Policy questions about returns and shipping decide whether someone risks the first purchase. And "where is my order" arrives after the money is already yours, which makes it pure support cost.

An agent trained on your store answers the first two instantly, on the product page where the doubt actually happens, and takes the first pass at the third.

Where the snippet goes

WooCommerce runs on WordPress, so the install is the WordPress install: the snippet goes before the closing </body> tag, either through a header-and-footer plugin or your theme's footer. The full walkthrough, including the block-theme and child-theme routes, is on the WordPress integration page — there's no separate WooCommerce step, and one paste covers your storefront, product pages, cart, and checkout together.

What's different about a store isn't the install. It's what you train the agent on and which actions you turn on, which is the rest of this page.

Before you start

You'll need admin access to WordPress and your embed snippet from the Install tab, with your chatbot id already in it. New here? Create a workspace free at app.evoriqa.com, no credit card needed.

Then point the agent at the pages that answer money questions: crawl your store so it picks up product descriptions, your shipping and returns policies, and your FAQ. A store's answers live in scattered places, and the agent is only as good as what you gave it.

Pre-sale questions are the ones worth getting right

Deflecting support tickets is the obvious win, but it's the smaller one. A shopper asking "does this run small?" at 11pm is a sale in progress. Nobody is answering, so they close the tab.

The agent answers from your own product copy and sizing guidance, and when the question goes past what you've published — a bulk order, a wholesale enquiry, a custom request — it captures the lead with contact details instead of losing it. Those are the conversations worth a human reply the next morning.

Order lookups, and the honest limits

"Where is my order" is the highest-volume message any store gets, and it is worth being precise about what happens to it.

WooCommerce already gives customers a self-service answer. The My Account page shows each order's number, date, status, and total, with Pay and Cancel buttons on failed or pending orders and an Order again button on completed ones. But guests can't see any of it — WooCommerce shows a login prompt first — and a customer who checked out as a guest, or who can't remember which email they used, is exactly the customer who emails you.

So the agent does two things. It explains what each order status actually means and points a logged-in customer to their own order list. And where you've configured an order-lookup action, it can call your store to fetch the real status inside the conversation, with every run logged for you to audit.

That second part is a deliberate setup step, not something that happens on install. The widget does not read your orders database by default, and it shouldn't — a chat bubble that can enumerate customer orders without an allow-listed action behind it is a data-leak waiting to happen.

Confirming it's live

Open your storefront in a private window and look for the chat bubble on a product page, not just the home page. Ask it something only your store would know — a shipping cut-off, a specific product's material — to confirm it's answering from your content rather than generically.

WooCommerce-specific limits

Caching is the usual culprit. Stores run more aggressive page caching than blogs do, and a cached page will happily keep serving the version from before you added the snippet. Purge the cache and retest in a private window.

Checkout is a page too. The snippet covers checkout along with everything else. If you'd rather the widget not sit on top of a converting cart, that's a reason to think about page targeting before you paste, not after.