Every answer shows where it came from

Yes. Every reply quotes a published entry and names it underneath, so visitors can see where the answer came from and open the page or entry it used. There is no reply without a source.

A source on every reply is part of every plan, including Free. If nothing published covers the question, the assistant does not make up a reply to fill the gap. It hands the question to your team instead.

No. Replies quote your published entry word for word. Kuuba does not paraphrase, summarise, make up wording around your content, or fill gaps with generated text. What visitors read is what you approved when you published the entry.

If you want different wording, edit the entry, preview the reply, and republish. Until you do, the live reply stays tied to the published text and its source cite. If nothing published covers the question, the assistant hands it to your team instead of making something up.

Yes. Each conversation shows the entry and the version behind every reply, so your team can see exactly what was published when the visitor asked.

That record sits alongside flags, enquiry status, and version history in your dashboard. Visitors see the source cite on the reply; your team sees the fuller version detail behind it.

A reply is as accurate as the entry behind it. That is why each one names its source, and why you can flag any reply that needs correcting. Kuuba does not make up wording around your content to sound more helpful.

When something is wrong, flag it, fix the entry, preview, and republish. Until the fix is live, related questions can be handed to your team rather than repeating the wrong published answer.

It does not pick one, and it does not make up a blend of the two. When published entries conflict on the same question, Kuuba hands the question to your team so a visitor never reads two different things from your site in the same chat.

You can then fix or archive the entry that is out of date, preview the reply, and republish. Until the conflict is resolved, related questions continue to go to your team rather than to a guessed answer.

Only the fees you have published, as written. If a visitor asks about a price that appears on a published entry, the reply uses that entry and cites it underneath so the visitor can open the source.

Kuuba never makes up a price or works one out for someone's own situation. Quotes that need judgement, personal circumstances, or a tailored figure go to your team as an enquiry. Visitors are told that a person will follow up rather than given a number the assistant made up.

No. Advice, and anything about a visitor's own circumstances, goes to your team. Kuuba answers only from firm-approved published knowledge. It does not give legal, medical, financial, or other professional advice, and it does not apply your published material to someone's personal case.

Questions that need judgement are collected as enquiries with the visitor's permission to be contacted. Your team replies in its own time, with the context from the conversation so far, from the dashboard or from Slack, email, or another tool you have connected.

Yes. Two topics are set aside from day one: quotes for someone's own situation, and advice about their own case. Questions on those topics always go to your team, even if you have published general fee tables or process guides elsewhere. The assistant does not make up a personal answer from general material.

You can add your own topics at any time. Anything you set aside is never answered from published knowledge. Visitors are told that a person will follow up, and the enquiry reaches your team with the conversation context and contact details they agreed to share.

Your AI assistant tells the visitor that a person on your team is the right next step and offers choices, such as speaking to someone on the team or booking an appointment. If someone is free, they join the chat and carry on the conversation. If not, once the visitor agrees, it sends your team a clear enquiry with the conversation so far and how to reach them. It does not make up a reply to fill the gap.

The enquiry waits in your Kuuba dashboard and in any tools you have connected, such as Slack, email or your CRM. Your team replies in its own time, with enough context to continue without digging through a full chat transcript first.

Yes. Ask your own questions in Try your assistant in your dashboard, including the ones you expect it to hand to your team. Check the reply and its source, then publish and paste the snippet when you are happy.

You can also paste the snippet on a staging or draft page first, try your questions there, and add it to the live site when you are ready. Drafts never reach visitors until you publish them.