Menu

Guides

Guides are longer than a blog post and meant to stay useful. Each one carries the date it was last read through, because a guide nobody has checked in two years is a liability dressed up as a resource. They are written for the person who runs the assistant day to day, not for the person who bought it.

  • How to add an AI chatbot to a WooCommerce store

    Install the plugin, connect your store, sync the catalogue and allow your domain. What each step does, and what to check when a sync finds no products.

    WooCommerce store owners and the people who set up their sites 6 min reviewed 4 November 2026

  • Why a WooCommerce chatbot gets price or stock wrong

    A chatbot that quotes a stale price or offers a sold-out product is reading a snapshot. Four causes, and how to tell which one your store has.

    WooCommerce store owners comparing or debugging a shopping chatbot 5 min reviewed 4 November 2026

  • Choosing a RAG similarity threshold, by measurement

    How to measure the right retrieval threshold for your own content instead of copying a number, with the method and our own results.

    Whoever tunes the assistant 11 min reviewed 5 August 2026

  • How to choose an AI chatbot platform: 10 questions

    The questions that separate AI chat platforms in a trial, including the ones we would rather you did not ask us. Useful whoever you choose.

    Anyone running a trial or a procurement 12 min reviewed 5 August 2026

  • Preparing your content for an AI assistant

    What to crawl, what to upload and what to rewrite so a RAG assistant finds the right passage. Most wrong answers start here.

    Whoever owns the website content 9 min reviewed 5 August 2026

Shorter articles on building and running an assistant are on the blog, and the vocabulary is defined in the glossary.

Three questions every store eventually asks

Is the assistant answering from the right material? “Preparing your content” covers what to crawl, what to upload, what to leave out, and how the structure of a page changes what the assistant can find in it. Most wrong answers are created here, long before a model is involved, and most of them can be fixed by rewriting a page rather than changing a setting.

Where should the line be? “Choosing a retrieval threshold, by measurement” explains the single setting that decides whether the assistant answers or declines, and how to find the right value for your own content instead of copying someone else's. It includes the measurements we made, and the ones that did not transfer from one store to another.

Which platform should we choose? “Evaluating AI chat platforms” is the list of questions that separate vendors during a trial, including the ones we would rather you did not ask us. It is written to be useful even if you choose someone else.

How we write them

Every figure in a guide comes from a measurement we can reproduce, and every recommendation says when it does not apply. Where our own product has a gap relevant to the guide, the guide names it. We would rather you trusted the guide than finished it with the impression that there is only one possible answer.

Who reads them

Store owners setting up the assistant for the first time, developers putting it on a custom site, and agencies deciding how to run it for several clients. Each guide says at the top who it is for and how long it takes to read, so you can tell in a few seconds whether it is the one you need. None of them needs a technical background to follow, and where a step needs a developer, the guide says so.

Suggest a guide

If there is a question you have had to answer for yourself that deserves a guide, tell us. The most useful guides here started as support conversations.

Then try it on your own catalogue

The guides are about what to check. The trace is where you check it.