Configure through conversation

The browser timezone is also proposed when starting the first interview for a bot created through a subscription or the regular form. Resuming a session preserves its decisions.

Create a bot with the setup assistant, or open it after a normal creation or a website subscription. No configuration form or text chat is needed. The assistant uses the standard voice configuration Live and proposes decisions during an audio conversation. Only users allowed to edit the bot, within their organisation and tag scope, can access its session and documents.

In My assistants → New bot, first choose BeAI Number or SIP Connection, then Create with the assistant or Configure manually. The chosen telephone mode is kept in either path; no number is purchased at this stage.

Browser or telephone

The assistant starts in your interface language (French or English), including telephone callbacks, and adapts if you speak another language. This interview language is independent of the language you choose for your future bot.

Choose a browser call and explicitly allow your microphone. A headset is recommended. WebRTC audio is full duplex: you can interrupt the assistant. Mute or end the call at any time. The waveform shows your actual microphone level; opening the page never enables it.

Alternatively, enter your own Belgian landline or mobile number to request a callback. Keep the tracking page open for decisions and document uploads. Special and premium numbers are excluded. Ringing lasts up to 30 seconds and is never retried automatically. Requests are limited to three per hour per user and number, with an additional shared capacity limit. The telephone option appears when callbacks are available. A call already answered on your phone continues if you close the page; closing a browser call page disconnects it.

If the microphone or network blocks browser audio, check permissions, change network or use the callback. If playback is blocked, click the enable-audio button. Ending from the tracking page is applied at the next checkpoint, normally within five seconds. Hanging up your telephone also ends the call.

Understanding your business

The assistant asks one question at a time, uses examples relevant to your work and follows up on vague descriptions. It reuses information you already provided. You do not need to understand AI or write instructions yourself.

It explores:

• Company or trading name, actual products/services and customers, separately from your BeAI organisation and the bot's name.
• Public premises, such as a shop, office or practice, their location, useful access details and appointment requirements. Without public premises, relevant questions concern service areas, remote services or delivery.
• Opening days and times, breaks, exceptions and appointment availability, followed by what the assistant should do outside those hours.
• Practical information for callers: public contact details, frequent questions, preparation for visits, quotation requests, lead times and permitted prices. Questions depend on your activity. Providing a website link does not automatically read it.
• The telephone role and limits, using a typical call to establish what to explain, collect or leave to a person. Choosing a bot type does not activate calendar bookings or call transfers.

Company details, practical information, hours and the mission appear as separate decisions; Voir opens their full text. After confirmation, their synthesis is saved in the bot's Additional information and becomes context for future calls.

You can say you do not know, that something is irrelevant or that you will provide it later. The assistant records the missing information and an agreed cautious fallback. Practical information and hours must be addressed before confirmation, even when explicitly deferred. Previously completed interviews keep their original checklist.

Decisions and documents

The assistant gathers the bot name, infers its type from the intended use, confirms its language and browser-detected timezone, and narrows down the voice through conversational preferences. It asks about the greeting, call behaviour, useful documents, email recipients and sending conditions, call recording and its announcement. The setup assistant keeps its own voice during the interview; it is not a preview of each proposed bot voice.

Decisions appear read-only. Say any corrections during the call; the last 500 changes remain in the decision history. Advanced settings, transfers, model selection, credentials and ERP/CRM/calendar connections are preserved and remain outside this interview. No email is sent during setup.

Upload documents while speaking. The assistant receives the upload and asks what each file means and how the bot should use it. Every uploaded file needs an explanation before confirmation. Up to five files are supported, with the same 200 MB (200,000,000 bytes) limit as the Documents skill: PDF, DOC/DOCX, XLS/XLSX, PPT/PPTX, ODT/ODS/ODP, HTML, TXT, Markdown, CSV, JSON and XML. There is no extracted-text length limit at upload. Scanned PDFs are accepted, subject to the document service’s OCR capabilities. Identical files are ignored. The conversation receives an optional preview of at most 8,000 characters; a missing preview does not reject the upload. The complete original file is stored privately and passed to the normal document processing pipeline after confirmation. Removing a draft or closing without applying removes pending files; expired draft files are cleaned automatically. Removing a draft file does not delete existing bot documents.

Confirm and continue

The assistant reads back a summary and waits for a new explicit agreement, such as “yes”, “okay” or “go ahead”, without requiring a fixed phrase. A correction or upload requires a new summary. You can also confirm using the tracking-page button once the summary is ready. Application is versioned and idempotent; concurrent changes to the bot cause a conflict rather than overwriting someone else’s work. Document preparation is asynchronous and its status appears in the tracking page. Failed documents can be replaced through the bot’s document management.

Before ending, the assistant explains how to add advanced skills for ERP, CRM or calendar integrations and how Beone can help with an AI consultant. Finish the bot’s telephone connection if needed and make a test call.

Free session, then explicit pricing

New eligible bots receive one Beone-sponsored session, started within 30 days of creation: up to 30 minutes in total with no exchange-count limit, resumable for 30 days after opening. Closing or applying the session consumes this entitlement. There is no automatic paid continuation. Later sessions require acceptance of the displayed price; subscription minutes are consumed first, then contractual overage, otherwise the organisation’s the standard voice configuration euro rate applies.

Connected time includes silence and muted time, billed by the second. Ringing is excluded, and Beone pays for the telephone transport. A connection lasts at most 30 minutes subject to remaining credit or free time. Technical recap finalisation is excluded. Unused credit reservations are released. Connections that never start are not billed; interrupted calls are settled from their saved checkpoint. Paid usage appears in the billing history. Audio is not retained; transcripts, decisions and document previews are kept for resuming. The chosen recording setting concerns future bot calls.

Choosing the main language

The assistant asks a question and waits for your answer before saving the language. When the context suggests French, it offers Belgian French, standard French, Canadian French or another language. Your location or the language used during the interview does not automatically select a variant. If you only answer “French”, the assistant asks which variant you prefer. This affects regional usage and vocabulary, separately from voice selection. The timezone is confirmed in a separate question.

Public API

Sessions expose catalog.languages with the enabled language codes and names from the normal bot settings. draft.language uses the exact chosen code, such as fr_be or fr_ca; the tracking page displays its name.

The same authorised operations exist under /api/v1/bots/{id}/setup-assistant: sessions, /voice, WebRTC /rtc, /stop, live document uploads, decisions and confirmation/application. Guided creation accepts an optional timezone at /api/v1/organisations/{id}/bot-setup. Legacy /messages and /draft writes return HTTP 410; historical records remain readable. OpenAPI describes schemas, idempotency keys, revisions and WebRTC events. activity, knowledge and hours each require their checklist topic and a nonempty synthesis, including any explicit deferral. Confirmed business information is added to extra_infos through the same application service as the GUI.

The callback comes from Beone’s 071 96 07 69, displayed in the phone option before requesting a call. The overview API exposes phone_caller.number (+3271960769) and phone_caller.display (071 96 07 69). Customers cannot override this caller identity.

Guided completion and compact live view

The assistant covers every required topic before the recap. A natural fresh answer such as “yes”, “okay” or “go ahead” confirms it; no fixed phrase is required. Missing items and configuration errors appear in the live view, rather than requiring repeated confirmations.

You can request an automatic summary email after every completed conversation, independently of conditional emails or audio recording. The assistant collects and confirms the recipient addresses. No email is sent during setup.

When you have documents to upload now, the assistant waits. For each uploaded file it asks what it is and how the bot should use it, saves that purpose, then asks whether you have another. Continue until you explicitly say there are no more, or that you will add others later. Each retained file still needs a purpose. Waiting counts as connected time. The purposes become bot instructions and the complete original file is processed after confirmation.

On desktop, call controls and uploads stay beside the compact decisions panel. Open “Voir” for longer values and “Voir les étapes” for the checklist. Phone calls have a connection animation, not a simulated waveform; reduced-motion preferences are respected. Mobile uses stacked panels.

Public session data includes checklist (steps, missing topics, next topic, pending documents), guidance_error, draft.summary_emails and draft.document_collection (unasked, collecting, complete, deferred). The same authorization and validation apply to GUI and API.

Platform administrators retain the setup history when a bot is deleted, with its last known identity and a deleted-bot label. Deleting the bot does not erase this administration history.