answerrails.com / docs
Documentation
Everything about running AnswerRails on your own site: getting it answering, how it decides what to say, what to do on each screen, and what to check when something isn’t behaving.
Came here from the Documentation link inside the plugin? You’re in the right place. The four sections below are the whole map; start with Start if the assistant isn’t answering yet, or Help if it was and stopped.
The four sections
docs/start/
Start
Installing AnswerRails, connecting it to a provider, and getting the first question answered.
docs/how-it-works/How it works
Plain-language explanations of how the assistant decides what to answer, what it refuses, and where your data goes.
docs/guide/Guide
Running it day to day: the knowledge base, consent and retention, data requests, escalations, and uninstalling.
docs/help/Help
Troubleshooting when the assistant isn’t answering, and what each connection test is telling you.
The fastest answers
- The plugin’s own health screen is usually quicker than any page here: it names which model is answering, whether knowledge search is healthy, and what happened at each stage — with a one-click test of every service the assistant depends on.
- Ask the assistant on this site. It is grounded in these pages and cites what it used, so you can check its working. If the answer isn’t in them, it will say so rather than improvise.
- Support is a person, by email. If your question should have had a page, tell us and we will write it; accessibility problems are treated as bugs rather than requests.
These docs are the assistant’s knowledge base on this site. That is deliberate: the demo and the documentation are the same corpus, so anything the assistant tells you here can be traced back to a page you can read yourself — and anything the docs don’t cover, it will decline to answer. Open the assistant →
