Install chat on your website

The Website chat skill adds a small chat bubble to your website. Visitors can write to the bot, send a voice message, attach an image or document, and react to messages. They do not need a BeAI account.

Install and personalise the chat

1. Edit the bot and add the Website chat skill.
2. Enter the allowed domains, such as https://www.example.be. Add your test website separately. Each entry authorises that exact origin: www.example.be and example.be are different origins. A page path is unnecessary.
3. Choose a title, welcome message, colours and the side of the screen for the bubble. The avatar comes from the bot. You can add an HTTPS link to your privacy policy.
4. Use Save at the top right. The floating Unsaved changes reminder keeps your edits until saving is confirmed.
5. Copy the installation code from the skill and paste it into your website pages, preferably before the closing body tag. Your website administrator can also place it in the shared page template.
6. Open the website, click the bubble and send a message to check the connection.

The snippet contains your console address and the widget's public identifier. It contains no password or API key. Visitors do not configure a server or AI provider. The chat refuses unauthorised websites, and each visitor can only access their own conversation.

Colours and position are specific to this bot. The panel adapts to phone screens. Messages can contain paragraphs, links and lists. Received content cannot execute HTML code.

Messages, files and voice notes

Visitors can send text, choose an emoji, react to a message or attach a file. To send a voice note, they must authorise the microphone, record, listen to the preview and explicitly confirm sending. Refusing microphone access does not prevent text chat. Closing the bubble does not send a draft.

A message can contain 5 files and 18 MB in total. Files remain private to the conversation. Unsupported, protected or excessively long content is refused. If AI analysis fails, the file remains in history; the bot explains the limitation without inventing its content.

Visitor reactions are passed to the bot immediately during an active AI session. After closure or during human support, they remain in history without generating an AI reply. An ambiguous emoji alone does not confirm a booking, payment or another business action.

The chat shows when the bot or agent is preparing a reply. Read receipts reflect messages displayed in the chat; they do not guarantee that their contents were understood.

If sending or generation is interrupted, BeAI keeps its state and does not automatically repeat a business action. The chat can check delivery before an explicit retry. A draft remains available while the page stays open if the connection is unavailable. An expired session requires reopening the chat.

Offer an agent with “Chat human handover”

Add the Chat human handover skill when the bot should be able to offer a colleague's assistance. Search for authorised users from the same organisation by name or email, then select the suggestions: their names and avatars appear as tags in the field. Use a tag's cross to remove a colleague. Set the circumstances for requesting a person and Inactivity before returning to the bot, between 1 and 10,080 minutes.

This skill covers text and voice messages on WhatsApp, Messenger and Website chat. It excludes telephone calls and WhatsApp or Messenger calls. Without this skill, the AI has no tool for requesting human handover.

Selected colleagues open Human support and explicitly enable browser notifications. Their browser asks permission. A red warning indicates that notifications are disabled, and administrators can check each colleague's activation status. Notifications need HTTPS and a compatible browser. Some phones also require installing the web application and allowing notifications in system settings.

When the bot requests a person, the conversation enters the queue and a notification is prepared for selected colleagues who have enabled notifications. Its contents do not expose visitor messages. Clicking it opens the inbox.

The AI pauses as soon as it requests a handover. A message asks the visitor to wait. Colleagues receive a notification, repeated every 15 seconds until the request is claimed or its deadline expires. A colleague selects Take this conversation to claim it; their name is announced to the visitor. If nobody claims the request within the timeout configured in Chat human handover, an apology announces that the bot is available again. New messages, voice notes, files and reactions remain in history; files received during human support are not analysed by the AI.

The assigned colleague can write, record a voice note, attach a file or react. They can transfer the conversation to an authorised colleague or Return to the assistant. Each human exchange extends the inactivity deadline. Once it expires, the next genuine visitor message can open a new AI session. Reloading a page or receiving a read receipt does not reactivate the bot.

Session closure and history

Website chat uses the same reminder and closure settings as WhatsApp and Messenger. Platform administrators manage them in system settings. A new visitor response cancels the reminder and restarts inactivity. Reminder and closure messages do not use the AI. Writing after closure starts a new exchange.

Conversations appear in history with the Website chat channel. After AI-session closure, BeAI prepares the summary, language and sentiment as for other chats. Attachment analysis and work already performed follow the organisation's messaging rates, including when human assignment subsequently interrupts a reply. During human support, the summary covers the AI portion; human exchanges remain in history.

Permissions and API

Changing the widget and its domains requires permission to edit the bot. Handover recipients must be authorised users of the same organisation. The console and public API apply the same permissions to the queue and messages. A colleague cannot claim an already assigned conversation or send as another person.

Configuration is available under /api/v1/bots/{id}/skills/web-chat and /api/v1/bots/{id}/skills/chat-human-takeover. The inbox and its actions use /api/v1/chat-inbox. The widget has a separate public transport protected by a private visitor session: the installation snippet does not grant access to the organisation's API. See the API documentation for formats and permissions.