When a visitor wants a person, your team is one step away

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.

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.

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. 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.

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.

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.

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.

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. 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.

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.