Kuuba FAQs

Kuuba is your firm's AI assistant on the website: a chatbot that replies to visitors only from the knowledge your firm has approved and published. Every reply quotes that information as you wrote it and shows the source underneath, so visitors can see where the answer came from and open the page or entry it used.

It also handles what visitors ask it to do, such as booking a meeting or requesting a callback. It takes their details, passes the request to your team and confirms back to the visitor. When a question is not covered by what you have published, or when it needs a person's judgement, it hands the conversation to your team. Someone on your team can join the chat and carry on. If no one is free, it explains that someone will follow up, collects the visitor's contact details with their permission, and passes a clear enquiry into the tools you already use, such as Slack, email or your CRM, as well as your Kuuba dashboard.

Kuuba is for service firms everywhere, in any industry, who want their own AI assistant on the website for the questions visitors ask again and again. Typical topics include fees, process, documents to bring, opening hours, how to book, and similar practical questions that already appear on your site or in your knowledge base.

Owners decide what the assistant can say by reviewing and publishing entries. Your team gets clear enquiries when a visitor needs a person rather than a published answer, in the places you already work. We support many firm types on our Industries page, each with a ready knowledge pack you edit in your own words before anything goes live.

Most website chatbots try to answer everything they can generate. Kuuba is built as your firm's AI assistant the other way round. It replies only from firm-approved published knowledge, shows the source on every reply, and hands a question to your team when nothing published covers it. Anything outside that knowledge is handed to your team.

Visitors get answers you have approved, in the words you approved, with a cite they can check. Your team gets the questions that need judgement, advice, or a quote for someone's own situation, in Slack, your inbox, or the other tools you already use. For a side by side view, see Compare.

Yes. Every conversation opens by saying so, so visitors know they are talking to your firm's AI assistant rather than a person on your team. That disclosure stays in place even when you brand the chat with your firm name, logo, and colours.

We think firms should be clear with visitors about who or what is answering. Kuuba does not pretend to be a member of your team, and branding does not remove that opening statement.

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.

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.

No. Kuuba does not make up answers. It only repeats fees you have published, never estimates a price for someone's own situation, and never gives professional advice. Anything that needs judgement, a personal quote, or advice about a visitor's own case is handed to your team as an enquiry.

Replies stay tied to firm-approved published knowledge and show the source underneath. When nothing published covers the question, the assistant explains that a person will follow up, collects contact details with permission, and passes a clear enquiry into Slack, email, the tools your team already uses, or your Kuuba dashboard.

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.

No. Visitors see the reply and its source, nothing more. There are no confidence percentages, star ratings, match scores, or similar figures on the chat.

We keep the visitor view simple on purpose. The cite under the reply is how they check what was used. If nothing published covers the question, the assistant hands it to your team rather than showing a score and guessing. Your team sees flags, versions, and enquiry status in the dashboard.

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.

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. 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 assistant answers only from sources you choose and then approve: pages from your website, entries you write in your own words, documents you upload, and articles from Notion and your help centre. You decide which sources to connect and which drafts to keep.

Everything from those sources arrives as a draft for you to review. Nothing reaches visitors until someone on your team publishes it. Kuuba does not make up answers from outside that published knowledge. You can edit drafts, set them aside, or archive them without ever putting them on the live assistant.

No. It reads only the pages you choose to add. Importing a page creates a draft for your team to review. Nothing from that import reaches visitors until someone publishes it.

You stay in control of the published set. Pages you leave out are never used in replies, and the assistant does not make up answers from the rest of your site or from the open web.

No. Only published entries are used in replies. Drafts stay in your workspace until someone on your team reviews and publishes them. Importing a page, uploading a document, or loading a knowledge pack never puts that content in front of visitors on its own.

Publishing is an explicit step. Until you take it, the assistant continues to use only what is already live. Questions that are not covered are handed to your team as enquiries rather than answered from a draft or from made-up text.

The people you give permission to approve and publish. Others on your team can write drafts, but drafts stay inside your dashboard until someone with publish permission makes them live.

That split keeps day to day editing open while protecting what visitors see. Publishing remains an explicit step after the entry has been reviewed and previewed.

Yes. Choose pages to bring in as drafts, then review them in your own words before you publish. Importing never puts that content in front of visitors on its own.

After you publish, replies that use those entries quote the published text and show the source underneath. Pages you do not import are never used in answers.

Upload documents or connect Notion and your help centre. Everything arrives as a draft for you to review. You edit it in your own words and publish only what you are happy with.

Nothing from an upload or a connected source reaches visitors until someone on your team publishes it. The assistant does not make up answers from unpublished material.

Yes. Every firm type on our Industries page has a ready knowledge pack to start from. The pack arrives as draft entries covering the practical questions firms in that industry hear most often, such as fees, process, documents, and booking.

You edit those drafts in your own words and publish only what you are happy with. Nothing from a pack reaches visitors until you publish it, and the assistant does not make up answers from unpublished pack material. See Industries for the firm types we support.

Yes. Edit it, preview the reply, and republish, or archive it so it is no longer used. Changes take effect for new conversations once you publish. Visitors who start a chat after you republish see the updated entry and its cite.

Every earlier version stays in your history, so you can see what was live before, who changed it, and when. If you need to undo a change, you can roll back to an earlier version in one step. Until a replacement is published, related questions that no longer have a live entry are handed to your team.

Once its review date passes, Kuuba holds that entry back and hands related questions to your team. Visitors are not left reading information you marked as due for review, and they are not given a silent guess from an expired entry.

Your team gets those questions as enquiries in the dashboard and in any tools you have connected, while you update or archive the entry. After you publish a fresh version, new conversations use it again with a clear source cite.

Yes. Every version of every entry stays in your history, with who changed it and when. You can compare what was live before, and roll back to an earlier version in one step if you need to.

Past conversations keep what was said at the time. New questions use the version that is published when the visitor asks. The assistant never fills a gap with made-up wording while you decide.

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.

An enquiry includes the visitor's question and the conversation so far, how to reach them, and their permission to be contacted. Your team gets enough context to reply without digging through a full chat transcript first.

The visitor chat itself does not display the internal summary your team receives. On the visitor side they see a short handoff message from your AI assistant. On your side you see the structured enquiry in the dashboard and in any tools you have connected, such as Slack, email or your helpdesk.

Only what your team needs to follow up: a name, how to reach them, and permission to reply. Contact details are collected as part of an enquiry handoff, not scraped from the chat without permission.

Once the visitor agrees, the enquiry reaches your dashboard and any tools you have connected. Your team replies in its own time, with the conversation context included.

Every enquiry waits in your Kuuba dashboard until someone marks it handled. That is the default, and it works whether or not you connect another tool.

You can also send enquiries into the tools your team already uses. Connecting Slack, your inbox, or a help desk does not remove the copy in Kuuba. It adds a path so the same enquiry reaches the place your team already checks.

Your AI assistant can send enquiries to your Gmail or Outlook inbox, by SMS, and by WhatsApp. It can post to a Slack or Microsoft Teams channel you choose. It can create a contact in HubSpot, or open a ticket in Zendesk or Freshdesk. See Integrations for the full list.

Google Calendar, Outlook Calendar and Calendly let your assistant book a meeting when a visitor asks for one, and help your team book follow-up calls. What each plan includes is listed on Pricing. Every enquiry is still kept in Kuuba even when it is also sent into the tools you already use.

No. Every enquiry waits in your Kuuba dashboard whether or not you connect anything. Connecting a tool means the same enquiry also reaches the place your team already checks, such as Slack, your inbox, or your help desk.

Firms often start with the dashboard alone and add a channel later so the handoff feels like part of how they already work. See Pricing for what each plan includes and which connections are available on Starter and Professional.

No. Every enquiry waits in your Kuuba dashboard whether or not you connect anything. Slack is one of several places an enquiry can also go, alongside Microsoft Teams, your Gmail or Outlook inbox, SMS, WhatsApp, HubSpot, Zendesk and Freshdesk.

Most small firms start with email, because everyone already checks it, and add Slack or Teams later if the team lives there. See Integrations for how each one works.

Yes. You can send the same enquiry to a Slack or Teams channel and to an inbox at the same time, or add a text alert for whoever is on duty. Each copy carries the visitor's question, the conversation so far and their permission to be contacted.

The enquiry also stays in your Kuuba dashboard, so when someone marks it handled there, everyone can see it has been picked up.

Google Calendar, Outlook Calendar (including Microsoft 365) and Calendly. Your assistant only offers times that are free in the calendar you connect, and the booking appears there straight away with the visitor's name and the conversation so far.

You choose which calendar or event type it books into and how long a first meeting lasts. Your team can still move or cancel a booking in the calendar as usual.

Yes. Every enquiry arrives in the same list in your dashboard, where anyone with access can open it, reply in their own words, and mark it handled. You do not need to route each enquiry to a named person up front.

If you also send enquiries into Slack, email, or a help desk, the people who already watch those channels can pick them up there. The copy in Kuuba stays available either way.

No. When someone on your team is free, they can join a visitor's chat and carry on the conversation. When no one is free, your team works from the enquiry and replies in its own time. Kuuba does not expect someone to sit in a live chat window all day.

If no one joins the chat, the visitor is told that a person will follow up. Your team picks up the enquiry from the dashboard or from a connected tool such as Slack or email, and continues the conversation outside the automated chat.

No. Once it hands over, the next reply comes from your team. A team member joins the chat, or if no one is free, the visitor is told that a person will follow up and the thread is handed to your team. Your AI assistant does not keep answering that conversation, and it does not make up more replies while your team is taking over.

That keeps the handoff clean. Visitors are not left half talking to the assistant and half waiting for a person, and your team is not racing an automated reply that continues after the enquiry was already sent.

Flag it from the conversation with a note, fix the entry it came from, preview the new reply, and republish. Anyone on your team who can read conversations can raise the flag so problems do not wait for a single owner.

After you publish the fix, Kuuba asks the flagged question again and shows you the result, so you can check the correction before visitors see it. Until the fix is live, related questions can be handed to your team rather than repeating the wrong published answer. The old version stays in history if you need to compare or roll back.

Anyone on your team who can read conversations can flag a reply. That way a wrong answer can be marked as soon as someone notices it, without waiting for a specific role.

Only the people you allow to approve and publish can publish the fix. Drafts still cannot reach visitors by mistake, and publishing remains an explicit step after the entry has been corrected and previewed. Until then, the assistant stays limited to what is already published, or hands the question to your team when nothing published covers it.

Yes. Any reply drawn from that entry uses the new version from the moment you publish. The re-check confirms the question you flagged, and later visitors who ask related questions get the updated wording and its cite.

Past conversations keep what was said at the time. Only new questions use the published fix. If you need to undo the change, roll back to an earlier version in one step.

Yes. Edit the entry yourself whenever fees, hours, or wording change, then preview and republish. You do not need a visitor flag to keep your knowledge current.

After you publish, new conversations use the updated entry and its cite. Earlier versions stay in your history, and you can roll back in one step if you need to.

Yes. Roll back to any earlier version in one step. Your history keeps prior versions of each entry, including who changed them and when, so a bad edit does not lock you in.

After a rollback, new conversations use the restored version and its cite. You can still keep the later draft in your workspace if you want to rework it and publish again later. The assistant never fills the gap with made-up wording while you decide.

No. Past conversations keep what was said at the time, including the entry version that was live then. That record stays available for your team to review.

New questions get the updated entry once you publish. The re-check after a flagged fix confirms the question you corrected before visitors see the new wording.

Yes. Flag, fix, preview, publish, and re-check come with every plan, including Free. The correction loop is part of how Kuuba protects your firm, not an upgrade.

Plans differ in allowances and features, not in the ability to correct a reply. See Pricing for a full comparison, and Corrections for how the loop works.

Usually not. Your AI assistant goes on any site that accepts a snippet. Copy it from your dashboard and paste it into your site, or send the snippet to whoever already runs your website.

That is the whole install for most firms. There is no custom integration required to get the chat live, answer only from firm-approved published knowledge, and send enquiries into the tools you already use. See Embed for the steps.

One paste. Copy the snippet from your dashboard and add it to your site: your homepage, a footer include, or your site builder's custom code block. That is the whole install for most firms.

You can try it on a staging or draft page first, then add it to the live site when you are ready. If someone else runs your website, send them the one-line snippet. See Embed for detail.

On any page that can take a script tag: your homepage, a footer include, or your site builder's custom code block. One snippet per website is enough for the pages you want the assistant on.

Copy it from your dashboard and paste it, or send it to whoever already runs your site. See Embed for the steps.

Yes. The chat panel resizes to fit narrow screens, so visitors on phones get the same replies, sources, and handoffs as visitors on a desktop.

Branding, suggested questions, and AI disclosure work the same way on mobile. You do not need a separate mobile install.

The snippet is small and loads your assistant when a visitor opens it. It does not block the rest of the page from rendering.

Firms add Kuuba to the sites they already run, including WordPress, Squarespace, and Wix, without a separate performance project. Contact sales if you want help with a less common setup.

Yes, on any site that lets you add a script tag. Kuuba works with WordPress, Squarespace, Wix, Webflow and Shopify, and the same one-line snippet from your dashboard is what you paste on each.

Contact sales if you want help with a less common builder or a multi-site arrangement. See Embed for the install path.

No. Kuuba works with all of them through one short snippet that you paste once, usually in the footer or custom code settings. There is nothing extra to install or keep updated.

If someone else looks after your website, you can send them the snippet from your dashboard. See Embed for the steps on each platform.

One snippet per website. Multi-site plans get a snippet for each site you manage, so each site loads its own assistant and published knowledge.

You copy each snippet from your dashboard. There is no separate mobile snippet. See Pricing for Multi-site, or contact sales.

Each Starter and Professional plan covers one website. Groups and partners with several sites can use the Multi-site and partners plan, which starts from £299 a month and includes a snippet for each site you manage.

Contact sales if you want help sizing a Multi-site plan, or see Pricing for what each plan includes.

Yes. Paste the snippet on a staging or draft page, try your questions, then add it to the live site when you are ready. The same snippet works on any page that can take a script tag.

Inside your dashboard, Try your assistant lets you ask questions against published entries before anything is on a public page. See Embed for install steps.

Yes. Delete the snippet from your site and your assistant no longer appears for visitors. Your published knowledge and enquiry history stay in your Kuuba account until you decide what to keep.

You can add the snippet again later on the same site or on a staging page. Removing the snippet does not delete your entries or past conversations on its own.

Yes. On every plan you choose the assistant's name, add your logo, and write the welcome message and suggested questions visitors see when the chat opens, so it feels like your firm's AI assistant rather than a generic bot.

Professional and above add full branding controls: brand colours and removing the Kuuba badge. Every conversation still opens by saying it is an AI, so visitors know they are talking to an assistant. See Branding for what each plan includes.

Your assistant introduces itself as AI, in the name and branding you chose, with a short welcome and any suggested questions you set. Visitors know from the first message that they are talking to your firm's AI assistant rather than a person on your team.

Branding does not remove that opening disclosure. On every plan you can set the name, logo, welcome, and suggested questions. Professional and above add full brand colours and the option to remove the Kuuba badge. See Branding.

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.

No. Your assistant replies from what you publish in your dashboard, and the snippet adds the chat to the site you already have. You do not need a redesign or a new site builder to get started.

Most of the work is deciding what you want published. Creating the account, writing a few entries, and pasting the snippet usually takes an afternoon. See How it works.

No. You write entries in plain words, and the snippet is one line to copy from your dashboard. If someone else runs your website, send them that line.

Connecting Slack, email, or another tool is optional and guided from the dashboard. Every enquiry still waits in Kuuba whether or not you connect anything.

Most of the work is deciding what you want published. Creating the account, writing a few entries, and pasting the snippet usually takes an afternoon for firms that already know their common visitor questions.

If you want help preparing and reviewing your first entries, contact sales about a guided start. A one-off setup fee may apply, and we agree it before you start.

Yes. We can help prepare and review your first entries and add the snippet. A one-off setup fee may apply, and we agree it before you start. Contact sales to arrange a guided start.

Many firms set up on their own in an afternoon: create an account, publish a few entries, and paste the snippet. Help is there if you want a hand with knowledge packs, branding, or connections into Slack and your inbox.

Starter is £35 a month and Professional is £125 a month, and you can try Kuuba on the Free plan with no payment details required. Multi-site starts from £299 a month for firms that need more than one site.

Plans differ in allowances and features, not in the rules about published knowledge, sources, and handovers. Every plan answers only from what you publish, and passes visitor requests and questions nothing published covers to your team as enquiries. See Pricing for a full comparison.

Free is a way to try your assistant on your own website, with no payment details needed. It shows a Kuuba badge and has a lower monthly allowance. When you are ready to go live for real, Starter or Professional gives it room to grow.

Free still replies only from firm-approved published knowledge, shows a source on every reply, and passes requests and other questions to your team. Those rules are never an upgrade. See Pricing.

Every plan replies only from what your firm publishes, shows a source on every reply, and passes requests and other questions to your team. Flag, fix, preview, publish, and re-check are included too. Those rules are never an upgrade.

Plans differ in allowances and features such as reports, full branding, and which connections are included. See Pricing for a full comparison.

A conversation is one visitor's chat with your assistant, however many questions they ask in it. Opening the chat and asking several follow-ups in the same thread still counts as one conversation.

Plans include a monthly conversation allowance. We let you know as you get close to the limit, and you can move to a larger plan at any time. See Pricing for what each plan includes.

We let you know as you get close. Your assistant keeps handing questions to your team as enquiries rather than making up replies to stay within a cap, and you can move to a larger plan at any time.

Enquiries handed to your team are not charged one by one. Contact sales if you want help sizing a plan for the volume your site sees.

No. Enquiries handed to your team are not charged one by one. They are part of how Kuuba works on every plan: when a question needs a person, your team gets a clear enquiry.

Plans differ in monthly conversation allowances and features, not in a per-enquiry fee. Contact sales if you want help sizing a plan for the volume your site sees.

Yes. You can move between plans as your needs change. Contact sales and we will explain the terms for your plan, including how a change or cancellation works for your billing period.

Moving up gives you more allowance and features. The rules about published knowledge, sources, and handovers stay the same on every plan. See Pricing.

Not without notice. We will always tell you before anything changes for your plan, so you are not surprised on a renewal or invoice.

Prices on the site are in pounds sterling, excluding VAT. We will always tell you the total before you pay. See Pricing or contact sales if you have a question about your plan.

Prices are in pounds sterling. The amounts on Pricing are the plan prices we publish for Starter, Professional, and Multi-site.

If you need a conversation about invoicing for your firm, contact sales and we will walk through what we can support.

Prices are shown excluding VAT. We will always tell you the total before you pay, so you see the plan price and any VAT that applies to your firm.

The same notice rule applies if anything about pricing changes for your plan. See Pricing or contact sales.

Tokens are used each time the assistant answers or processes knowledge. When this period's tokens are used up, the assistant pauses answers and shows a clear message until you add tokens or the allowance renews.

We also warn you when the balance is low, so you can top up or move plan before answers pause. See Pricing or contact sales if you want help sizing allowance for your firm.

Whether unused tokens roll into the next period has not been confirmed yet. Plan allowances renew on their billing cycle, and top-up packs are available when you need more during a period.

When the product rule is settled, we will state it clearly on Billing and on this page. Until then, treat unused allowance as applying to the current period only, and contact sales if you need a written answer for procurement.

You can set a balance threshold in Billing and tokens so your team sees when the balance is low. Taking payment for an automatic top-up pack has not been confirmed yet.

Until automatic payment is available, add a pack yourself when you need more tokens, or move to a plan with a larger monthly allowance. Contact sales if you want help choosing.

Kuuba is hosted in UK and EU data centres. Firm knowledge, conversations, and enquiries stay in those regions as part of how the product is run.

We do not make broader compliance claims on this page. If you need detail for your own security or procurement review, contact sales and we will walk through how we handle firm and visitor data in practice.

Only your firm, and only after the visitor agrees to be contacted. Contact details are collected as part of an enquiry handoff, not scraped from the chat without permission.

Each firm's records are kept separate from other firms on Kuuba. Visitor contact details are not shared across customers, and they are not used to answer questions for another firm's site. When an enquiry is sent into Slack, your inbox, or another connected tool, it still belongs to your firm alone.