Skip to main content
Belcenter AIHelp center
Chat and human takeover

Take over a chat conversation

Enable notifications, take over a conversation, reply, and hand control back to the bot.

The Chat human handover skill allows your team to take over WhatsApp, Messenger, and website chat messages, including voice notes. It does not apply to audio calls.

In the bot configuration, add this skill. Click inside Colleagues available for handover, type a name or email address, then click on a suggestion. Each selected person appears in the field as a tag with their avatar; the small cross lets you remove them. People already selected are not suggested a second time. Only active collaborators in your organisation who have access to the bot are available.

Specify when the assistant should suggest a person, then save in the top right. All takeover settings are consolidated in this skill: the WhatsApp, Messenger, and Website chat skills are used solely to configure their channel. The Inactivity before return to bot timeout is shared across the three channels, between 1 and 10 080 minutes. Reminder and session end settings remain the platform's shared settings.

Bot behaviour and existing settings

In Bot behaviour, Allow AI to request a human handover is directly visible alongside instructions and the return-to-bot timeout. Disable this option to keep manual takeovers only, without removing the team or instructions. Open the inbox, in the panel header, provides access to conversations and notifications. Save your changes with the bot button in the top right. The skill retains its configuration when removed from the bot; it must be active to provide the takeover tool to the AI. Instructions accept up to 10 000 characters.

Legacy teams, instructions, and durations configured in WhatsApp or Messenger are migrated into the dedicated skill. An already saved shared configuration retains priority; no duration remains editable separately in a channel.

WhatsApp takeover uses the same queue and browser notifications as Messenger and website chat. Legacy WhatsApp alerts, group decisions, and device confirmations have been removed; no WhatsApp notification numbers or templates need to be configured. Takeovers already in progress and their history are retained in the shared mechanism.

If the number is shared with the WhatsApp Business app on a mobile phone, a reply sent directly by the team in WhatsApp also triggers human takeover. BeAI retains messages forwarded by Meta in the history and the AI stops responding. Each new human exchange extends the shared inactivity timeout; the next message after this timeout can start a new session with the bot. This detection requires Meta to forward Business app messages for the connected number.

Waiting for a team member

Maximum wait time for a collaborator sets the duration between the request and the automatic return to the bot: from 1 to 60 minutes, 2 minutes by default. The AI no longer sends responses and no longer runs tools during this wait time. The holding message is sent by BeAI. New exchanges are kept in the history and do not extend the wait time.

Selected collaborators who have enabled browser notifications are alerted immediately, then every 15 seconds. Reminders stop as soon as someone takes over the conversation or the waiting time expires. The browser and device operating system must allow notifications; an expired or deleted subscription no longer receives alerts.

If no one takes over the conversation within this timeframe, BeAI sends: “I'm sorry, no available team member was able to take over your conversation. I'm resuming your request to help you.” The bot becomes available again for new messages, without re-running interrupted tools. This timeout is separate from Inactivity before returning to bot, which applies only after an actual takeover by a human.

Enable notifications

Open Chat human handover in the menu, then Enable notifications. Your browser will prompt you for permission. This must be enabled on each device. A red warning indicates that the browser is not enabled; the Team panel displays a green or red dot for each collaborator. If you have blocked notifications, allow them in your site settings. Notifications require HTTPS and a compatible browser.

Only selected collaborators who are still authorised receive the notification. It includes access to the queue, with no conversation text. Receiving a notification does not mean the conversation has already been taken over.

Take, reply, and transfer

The assistant creates a request in Unassigned, pauses immediately and sends a message inviting your contact to hold on. Click Take over conversation: it is assigned to you and the AI stops responding and running tools for this session. If someone else was faster, the queue updates.

Your contact receives “Camille has taken over your conversation.”, with the name of the collaborator who has just taken it over. This message is kept in the history, on WhatsApp, Messenger and the website chat widget. A transfer to another colleague also announces their name. A request that is still pending does not send this announcement. If no name is provided, the message states “A member of our team”; the email address is not published. The announcement uses the conversation language (French or English), or the bot's language.

The announcement follows the same delivery rules as your replies: its status in the history indicates any rejection or uncertain outcome. The assignment remains effective even if the channel rejects the announcement. Repeated clicks do not resend it; the announcement is not resent automatically after an interruption.

You can type, attach a file, listen to or record a voice note and use emojis. Listen to your voice note before sending it. Exchanges remain in the BeAI history. Reactions are available in the web chat and WhatsApp; Messenger retains incoming reactions, but its messaging interface does not allow BeAI to publish a remote reaction.

Transfer to a colleague keeps the conversation and changes the assignee. Return to bot prepares the assistant's return on the next incoming message, without sending a message or re-running an action. Each exchange during a takeover extends its inactivity timeout. After expiry, the next incoming message starts a new AI session; the previous history is retained.

Close chat

The collaborator to whom the conversation is assigned, or an administrator with access to the bot, can choose Close chat under Details and team. An administrator can also close a request that is still Unassigned, without assigning it to themselves. A confirmation announces that a closing message will be sent and warns you if an unsent draft will be deleted. Cancel keeps your draft and the conversation.

During closure, you can no longer reply, transfer the conversation or return it to the bot. Once Closed, it remains viewable in All, with its attachments and access to the complete history. The next message from your contact will open a new session with the bot. In the website chat widget, input typed during the brief closing phase is preserved and can be sent once closure is complete.

History closure and sending the closing message have distinct statuses. Provider accepted closing message indicates its acceptance by the channel; this does not guarantee it has been read. In the event of rejection or uncertain delivery, the conversation is still closed and the interface explains this without advertising delivery. Check closure status refreshes its status and does not send a second message. If the request was not confirmed and the server does not yet show closure, Retry this closure only restarts the same operation, with the same reference. No resend is automatic.

Limits and errors

WhatsApp and Messenger maintain their provider reply window. A visible conversation may therefore be too old to send a reply. Files are limited to five, 10 MiB each and 18 MiB per upload; voice notes to three minutes and videos to one minute. Any rejection is explained. When the outcome of a delivery is uncertain, check the history rather than resending the message with a new attempt.

Users who are locked, removed from the team or deprived of access to the bot can no longer take over, reply or receive new notifications.

API

The same commands are available under /api/v1/chat-inbox: reading, messages, assignment, transfer, return to bot, closure, reactions, presence and browser subscriptions. Decisions send the current version. Outgoing messages retain a stable client_id. Closure sends this reference with version to POST /api/v1/chat-inbox/{id}/close; retrying the same reference retrieves its result without sending a duplicate. The skill is configured under /api/v1/bots/{id}/skills/chat-human-takeover. Refer to the API documentation for formats, permissions and multipart files. The legacy WhatsApp field human_takeover and whatsapp_compatibility options are rejected: use the dedicated skill. The Messenger field inactivity_timeout_minutes remains a deprecated alias of the common timeout for existing API clients.

A platform administrator belonging to the Beone root organisation may also select Beone members who already have access to the bot. They keep their current account and permissions. These bots’ conversations appear in their inbox and notifications are available even if the bot belongs to another organisation. Other administrators remain limited to the bot’s organisation. A colleague with read-only access may handle assigned chats without editing the bot.

Human takeover hours

In the Chat Human Takeover skill, enable Restrict requests to the hours below. Enable the days when your team is available, then enter one or two time slots per day. The second is optional, for example for a lunch break. Disabled days are closed. Apply Monday to other weekdays copies only to Tuesday through Friday; weekends stay unchanged.

Hours follow the bot’s time zone, displayed in this section. Start times are included and end times excluded: with 09:00–12:00 and 13:00–17:30, no new AI request starts at noon or from 17:30. Slots must be ordered, non-overlapping and within the same day. At least one slot is required when restrictions are enabled.

Outside these hours, the assistant continues helping and explains that the team is unavailable if a person is requested. It does not announce a transfer or send a new alert. Assigned conversations are not interrupted. Agents’ manual actions and existing pending-request deadlines remain available.

Without this restriction, requests remain possible at any time. Click Save at the top; the unsaved-changes reminder also covers these hours.

Through the API, use PATCH /api/v1/bots/{id}/skills/chat-human-takeover : availability.enabled, availability.weekly_hours. The seven keys 1 — 7 represent Monday through Sunday. Each day contains zero, one or two slots { "start": "09:00", "end": "12:00" }. The form’s permissions and validation also apply. Updating only availability.enabled preserves existing slots. Copying is a local input helper; the API saves the complete week.

Documentation updated with the application