Install chat on your website
Add the skill, customise the bubble, and embed the chat script.
The Website chat skill displays a compact bubble on your website. Your visitors can chat with the bot, send voice notes, attach images or documents, and react to messages. They do not need a BeAI account.
Install and customise the chat
- Edit the bot and add the Website chat skill.
- Specify the authorised domains, for example
https://www.exemple.be. Add test site domains separately. A domain only authorises that specific address:www.exemple.beandexemple.beare two distinct origins. A page path is not required. - Choose the title, welcome message, colours and bubble position (left or right). The avatar matches the bot's. You can add the HTTPS link to your privacy policy.
- Click Save in the top right. The floating Unsaved changes reminder preserves your settings until the save is confirmed.
- Copy the installation code provided in the skill and paste it into your website pages, ideally just before the closing
bodytag. Your webmaster can also add it to your global page template. - Open your website, click the bubble and send a message to test that it works.
The code uses your console address and the public widget ID. It contains no passwords or API keys. Visitors do not need to configure any server or AI provider. The chat rejects unauthorised websites, and each visitor can only access their own conversation.
Colours and positioning remain specific to this bot. On mobile phones, the panel adapts to the screen. Messages support paragraphs, links and lists. Received content cannot execute HTML code.
Invitation beside the bubble
After 5 seconds, the closed chat shows “Besoin d’aide ?” beside its bubble. Customise Invitation beside the chat bubble in the skill (up to 160 characters), or leave it blank to disable the invitation. This is separate from the welcome message inside the chat.
The cross dismisses only the invitation; the chat bubble stays available. Clicking the text opens the chat. Dismissing the invitation or opening the chat prevents it from returning across pages and visits on the same site, in that browser and for that widget, while site data is retained. If browser storage is blocked, the preference may last only for the current page or visit. Displaying the invitation alone does not open a session or create a billable exchange.
The same setting is available through PATCH /api/v1/bots/{id}/skills/web-chat:
{"invitation_text": "Une question ? Parlons-en !"}
Changes use the shared Save button and the same bot editing permissions and validation as the other skill settings.
Messages, files and voice notes
Visitors can send text messages, choose emojis, react to messages or add attachments. For a voice note, they must grant microphone access, record, and then listen to the preview before confirming sending. Denying microphone access does not prevent sending text messages. Closing the bubble does not send a draft.
| Content | Limit |
|---|---|
| Text message | 8 000 characters |
| Images JPG, PNG, WebP or GIF | 10 MB and 40 million pixels per image |
| 10 MB and 100 pages | |
| DOCX or ODT documents | 10 MB; text extraction only, without reading embedded images |
| TXT, CSV or JSON in UTF-8 | 100 000 bytes of text |
| Voice message MP3, M4A, OGG, WAV, FLAC, AAC or WebM | 10 MB and 3 minutes |
| Video MP4, WebM or MOV | 10 MB and 1 minute |
A message can contain up to 5 files and 18 MB in total. Files remain private to the conversation. Unsupported, protected or oversized files are rejected. If AI parsing fails, the file remains available in the history; the bot reports the limitation without inventing its contents.
A visitor's reactions are passed immediately to the bot during an active AI session. After closure or during a human takeover, they remain in the history without triggering an AI response. An ambiguous emoji alone does not confirm a booking, payment or any other action.
While generating a reply, the chat indicates that the bot or agent is typing. Read receipts reflect message display in the chat. They do not guarantee that the content was understood.
If sending or generation is interrupted, BeAI preserves its state without automatically re-executing a business action. The chat interface allows you to review a message before resending. If the connection drops, the draft remains available as long as the page stays open. An expired session requires reopening the chat.
Follow-up question and silent closure
The web chat uses the same timers as WhatsApp and Messenger, located in system settings reserved for platform administrators. They are also available via PATCH /api/v1/system-settings/whatsapp: reminder_enabled, inactivity_reminder_minutes and close_after_reminder_minutes.
After the first timeout, the chat asks once: "Do you have any other questions?". A reply continues the session. With no reply, it closes silently after the second timeout, without any warning or Session ended banner. By default, the question appears after 5 minutes and closure occurs 5 minutes later. If the visitor has already answered the question, a subsequent period of inactivity closes the session after the sum of both timeouts, with no further follow-up. Disabling the question preserves this silent closure after the sum of the timeouts.
The visitor can write again at any time, which opens a new session with the bot. Closing does not delete their draft. The BeAI history and GET /api/v1/conversations/{id} retain the closed state under standard permissions. Automated messages incur no extra charges and do not affect voice calls or human takeover rules.
Offer a human agent with "Chat human handover"
Also add the Chat human handover skill if the bot should be able to offer a human agent. Select authorised users from the same organisation: their name and avatar appear in the selection list. Specify the escalation guidelines for handing over to a human and set the Inactivity before return to bot timer between 1 and 10 080 minutes.
This skill covers written messages and voice notes across WhatsApp, Messenger and Website chat. It does not support phone calls, WhatsApp calls or Messenger calls. Without this skill, the AI does not have the human takeover request tool.
Selected team members open the Human takeover menu and turn on browser notifications using the dedicated button. The browser prompts them for permission. A red warning flags missing activation; administrators can check team members' status. Notifications require a supported browser and an HTTPS connection. On certain mobile phones, installing the web app and adjusting system settings may also be required.
When the bot requests a human agent, the conversation enters the queue and a notification is prepared for selected team members who have enabled notifications. Its contents do not reveal the visitor's messages. Clicking it opens the inbox.
As soon as a takeover is requested, the AI pauses. A message prompts the visitor to wait. Team members receive a notification, repeated every 15 seconds until handled or the timeout expires. A team member selects Take over conversation to assign it to themselves; their name is announced to the visitor. If no one takes the request within the timeout configured in Chat human handover, an apology message announces the return to the bot. New messages, voice notes, files and reactions continue to be recorded; attachments received during the takeover are not analysed by the AI.
The assigned person can type, record a voice note, attach a file or react to messages. They can transfer the conversation to an authorised colleague or use Return to bot. Each human exchange extends the inactivity timeout. Once this timeout is exceeded, the visitor's next genuine 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. They are located in system settings reserved for platform administrators. A new reply from the visitor cancels the reminder and restarts the inactivity period. Reminders and closure notifications do not use AI. After closure, sending a new message starts a new exchange.
Conversations appear in history under the Website chat channel. After the AI session closes, BeAI prepares the summary, language and sentiment, just like for other chats. Attachment scanning and processing already completed follow the organisation's messaging rates, even if a human assignment subsequently interrupts the response. During a human takeover, the summary covers the AI portion; human exchanges remain in the history.
Permissions and API
Modifying the widget and its domains requires permission to edit the bot. Takeover recipients must be authorised users from the same organisation. The queue and messages apply the same permissions in the console and public API; a team member cannot assign themselves a conversation already taken or send messages on behalf of another colleague.
Settings are available under /api/v1/bots/{id}/skills/web-chat and /api/v1/bots/{id}/skills/chat-human-takeover. The queue and its actions use /api/v1/chat-inbox. The widget uses a separate public transport, protected by a private session unique to the visitor: the installation code does not grant access to the organisation's API. Consult the API documentation for formats and permissions.