USE CASE

WooCommerce AI chatbot from one script tag in your footer

One script tag in your WordPress footer puts Deacon on a WooCommerce store. It answers shoppers from your published pages, with no plugin to install.

Published

The WooCommerce Marketplace has a live chat category. It listed 14 extensions on 19 September 2026, every one from another company. Deacon is not among them. It answers pre-sale questions from your store’s own pages, and it goes in as a single script tag.

Two routes into WordPress

WordPress itself has no setting for a site-wide script, so the tag goes in through one of these.

  • A header and footer plugin. WordPress.com’s guide to adding code uses the free Insert Headers and Footers plugin by WPCode, then Code Snippets, then Header & Footer. On WordPress.com it needs the Personal plan or above.
  • The wp_footer hook, which prints scripts before the closing body tag if your theme calls it. WordPress’s reference for wp_footer says not every theme does. WooCommerce’s docs point to the Code Snippets plugin for hook code like this, since a theme update overwrites edits made in theme files, and WooCommerce’s page on code snippets has the steps.

Whichever you pick, the snippet from Deacon’s Install page goes in the footer. List your store’s domain there first. Our guide to adding an AI chatbot to WordPress goes further into the WordPress side.

A new store starts hidden

WooCommerce puts a new store into Coming soon mode once setup finishes. Visitors see a landing page. Only people you have given access, or a private link, see the store, per WooCommerce’s page on Coming soon mode. The switch is under WooCommerce, then Settings, then Site visibility.

Deacon reads your pages the way a visitor does. While the whole site is hidden, the Coming soon page is all it can reach. Until you go live it can learn from files and pasted text, and the install guide shows how to add both. You can test on the free plan, which stops at 50 answers a month.

The returns page WooCommerce leaves as a draft

Setup creates your Shop, Cart, Checkout and My Account pages. It also writes a Refund and Returns Policy page, but leaves it as an unpublished draft with sample text, WooCommerce’s list of store pages says.

A draft is not on your live site. Shoppers cannot read it, and nor can Deacon. Rewrite the sample text in your own terms, publish it and link it from your footer. WooCommerce’s docs call the page strongly recommended.

Questions about one shopper’s order

Deacon cannot look up an order. It cannot see your WooCommerce admin, so a question about one customer’s parcel is beyond it. It says so, asks for the shopper’s email address, and hands you the conversation. Your reply reaches them by email.

Signed-in customers can see their own orders under My Account, at /my-account/orders/ on your store, per WooCommerce’s list of endpoints. A line saying so on a page Deacon has learned lets it send shoppers there.

Try it on your own documentation

Add your help pages, ask it the question you know your docs cannot answer, and watch it say so.

The free plan covers 50 answers a month on one seat, and the paid plans are on the pricing page.

Start free

Free plan, no card.

READ NEXT