It answers
The question matches a help-centre section closely enough. The reply is that section's text, with the source printed underneath.
The rota your team
actually reads.
Shiftbloom plans shifts for cafés and restaurants. Its support assistant answers from the company help centre — and only from there.
Tue 22 Sep
- PetarKitchen08:00–16:00
- LenaFloor11:00–19:00
Shiftbloom is an invented company, written for this demonstration. Every fact the assistant states comes from the 33 help-centre sections published on this page.
Shiftbloom support
Answers from the help centre, updated 18 Sep 2026
Three answers, three honest outcomes
Most complaints about support bots come from one habit: inventing an answer rather than admitting a gap. In this demo the assistant has no generative step, so it can only do one of three things. In a real project the same rules wrap a language model, so answers stay grounded in your documents.
It asks which topic you mean
The topic is in the help centre but the exact question is not — there is nothing about commission. Rather than pass off a nearby page as the answer, it offers the closest topics and lets you choose.
It says it does not know
Nothing in the help centre covers the question. It says so, names the word it did not recognise, and offers a human.
Checked, not promised
A fixed set of questions runs against the assistant on every change: real phrasings for things the help centre covers, plus questions it must not answer. Run it here, in your browser.
Not run yet.
What the assistant was given
Nothing else. Pick any line to ask it.
What this looks like as a project
Build
Your help centre, PDFs, policies and past support replies become the knowledge base. The assistant is embedded on your site and in your help centre, in your own colours.
Proof
You get the question set as a file you can read: what it must answer, what it must refuse. It runs on every content change, so a new price never leaves an old answer behind.
Every month after
A short report of the questions it could not answer — the gaps in your own documentation — plus the content updates and a re-run of the test set.