Support answers your customers can trust.
Cited answers from your help centre, footnotes every answer with its source, and hands the rest to your team.
Try a question it can't answer, too.
Most support bots guess. Customers notice.
A confident wrong answer about pricing or refunds costs more than no answer at all. Cited is built to be right or to step aside.
A typical chatbot
- Makes up policies that sound plausible
- No way to tell where an answer came from
- Customers repeat themselves when they reach a person
- No idea which questions it gets wrong
Cited
- Answers only from your published help articles
- Shows the article and section behind each answer
- Hands off with the full transcript in your inbox
- Reports why it hands off, so you know which docs to write
What happens when a customer asks a question.
Five steps, in about two to five seconds. The last check is done in code, not left to the model.
- 01
Customer asks
A question in the chat widget on your site, in their own words.
- 02
Search your docs
The most relevant sections of your help centre are found, including context from earlier in the chat.
- 03
Draft the answer
Claude writes a short reply using only those sections, and lists the ones it used.
- 04
Check the draft
Code verifies every citation points to a real, retrieved section. No citation, no answer.
- 05
Answer or hand off
The customer gets a sourced answer, or a ticket is opened for your team with the full transcript.
Built for support teams, not just for the chat window.
The widget is what customers see. The console is where your team runs it.
Every answer shows its source
Customers see which help article an answer came from, and can open it. Your team can check any answer against the original in one click.
It doesn't guess
If the answer isn't in your docs, Cited says so and hands over. Answers that don't cite a real section are blocked before the customer sees them.
Handoffs arrive with context
When a person is needed, a ticket lands in the support inbox with the question, the reason and the full conversation, so nobody asks the customer to repeat themselves.
See what it handles
Track how many conversations the assistant resolves on its own, why it hands off, and which articles customers rely on most.
Your docs stay the source of truth
Write help articles as you do today. Re-index after an edit and the assistant answers from the new version. There's no training step.
One line to install
Add a single script tag to your site or help centre. The widget works on desktop and mobile and only runs on the domains you allow.
For teams where a wrong answer costs a customer.
SaaS support teams
Deflect repeat questions about plans, billing and setup, and spend agent time on the issues that need a person.
E-commerce and subscriptions
Answer delivery, returns and subscription questions straight from your policy pages, accurately.
IT and internal helpdesks
Point it at your internal wiki so staff get sourced answers about tools and processes.
Small teams without 24/7 cover
Customers get answers out of hours; anything else is waiting in the inbox in the morning, with context.
Live on your site in minutes.
Load your help articles, allow your domain in Settings, then add one line before the closing body tag. The widget picks up your assistant's name, greeting and brand colour.
<script src="https://support.yourcompany.com/widget.js" defer></script>Questions support leads ask.
Which AI model does it use?
Claude, by Anthropic, through the official API. Answers are generated from your help articles only; the model is told to treat everything else as reference, not instructions.
What happens when the docs don't cover a question?
The assistant tells the customer it doesn't want to guess and opens a ticket for your team. The ticket shows the question, why it was handed off and the conversation so far.
Can it issue refunds or change accounts?
No, by design. Cited answers questions. Anything that needs a person, such as refunds, account deletion or identity checks, is explained from your policy and handed to your team.
How do I update what it knows?
Edit your help articles and re-index from the Knowledge base page. Answers use the new content immediately.
Where is data stored?
Cited is self-hosted: conversations and tickets live in your own PostgreSQL database. Questions and the relevant help sections are sent to the Claude API to draft each answer.
Ask it something it can't answer.
Then open the console to see the ticket it created, with the whole conversation attached.
Try the demo