Identity and instructions
Define the bot's role, greeting, language, phone number country, time zone, and general behaviour; understand quiet voice detection, single announcements, and errors during a tool sequence.
Save a copy of a bot
You can edit the name, voice and organisation of a previously created copy before completing its telephony connection. These changes preserve existing SIP settings. As soon as you modify the manual SIP connection, its mandatory fields must be completed before saving.
If a field prevents saving, an alert at the top of the form indicates its label and the reason. Click the field within this alert to open its section. Entered values remain available for correction; they are only saved once validated.
Navigating the form
The form starts with identity, displaying the avatar, tags and the Accessible via label when required by your connection. The Language, time zone and voice fields occupy a single line on large screens and stack on mobile devices. Greeting and context follows these fields. Technical configuration is managed by BeAI. Advanced voice settings directly contains parameters compatible with the bot, as well as speech speed when available.
Open these panels when you want to fine-tune the bot's behaviour. Collapsing them preserves your values, including previously saved custom settings. An error within a panel opens it to allow correction.
Phone number country
Under Language, time zone and voice, the optional Country for phone numbers field specifies how to interpret a number without an international dialling code. Leave Automatic (organisation) to use values in this order:
- the country explicitly selected on the bot;
- otherwise, the country in the Billing details of the organisation directly linked to the bot;
- otherwise, Belgium.
The form displays the country actually applied and its source. This selection is independent of the bot's language, the interface language and the time zone. Select a country from the list, then use the form's shared Save button. The same bot modification permissions apply.
For example, with France, 07 12 34 56 78 is interpreted as +33712345678. With Belgium, 0475 12 34 56 becomes +32475123456. A number starting with + or 00 retains its international dialling code; its format can be normalised with +. Internal extensions and technical messaging identifiers are not converted into public numbers.
This country is used for future national numbers used for calls, callbacks, SMS and contact searches. Updating the organisation's billing country recalculates the country for bots in automatic mode for their future uses. History and recipients already recorded in a call or SMS request are not rewritten.
Recipient permissions and existing protections against special or premium-rate destinations continue to apply. For SMS, the actual country of the normalised recipient continues to determine the rate. An invalid or withheld number does not become an allowed destination through this setting.
The API offers the same configuration with phone_country_code in POST /api/v1/bots or PATCH /api/v1/bots/{id}/identity. For example:
{"phone_country_code":"FR"}
To revert to the automatic choice, send {"phone_country_code":null}. GET /api/v1/bots/{id} and GET /api/v1/bots/{id}/identity return the choice, effective_phone_country_code, and phone_country_source (bot, organisation, or default). Example of a bot inheriting its organisation's country:
{"phone_country_code":null,"effective_phone_country_code":"FR","phone_country_source":"organisation"}
Effective fields are calculated by BeAI and cannot be forced via write operations. An unknown country code is rejected; values in the form remain available for correction.
Change the avatar
Click the bubble or its pencil icon to select a JPG, PNG, or WebP image of maximum 5 MB. The cross icon lets you remove the image; Cancel restores the saved avatar. The preview is local: the change is applied using the form's common Save button. A rejected image displays an error and must be corrected before saving.
Save a copy of a bot
You can edit the name, voice and organisation of a duplicated bot before completing its phone connection. These changes preserve existing SIP parameters. As soon as you edit the manual SIP connection, its mandatory fields must be completed before saving.
If a field prevents saving, an alert at the top of the form indicates its label and reason. Click the field in this alert to open its section. Entered values remain available for correction; they are only saved after validation.
Assigning a specific role
Describe what the bot represents, what it can do and what it must never do. Prefer short, observable rules prioritised by importance.
A well-designed configuration specifies, in particular:
- how to introduce itself;
- information to collect;
- situations where an action or transfer should be offered;
- topics to decline or hand over to a human;
- how to confirm sensitive data before using it.
Welcome message and additional information
The welcome message is spoken or sent at the start of the conversation. It should remain natural and avoid promising actions that rely on unverified integrations.
Additional information is used to provide consistent context: opening hours, covered services, emergency procedures or specific vocabulary.
Language and time zone
The bot’s language guides its conversations. Chat summaries follow the language configured for the organisation, regardless of the interface language. The time zone is used to interpret ‘tomorrow’, ‘this afternoon’ or an appointment date.
Italian can be selected as the main language under Language, time zone and voice. Luxembourgish is disabled because its spoken quality is not validated. It is no longer offered for new settings or voice previews. Its definition and historical test configurations are retained without automatically changing existing bots’ language. The API rejects new selections of lb and its variants. Changing your account language does not change existing bots’ language.
Custom texts already saved are not rewritten in the configuration. The bot is instructed to start in the selected language; review and adapt your welcome message and prompts to keep full control over phrasing. Place a test call to hear the pronunciation and verify comprehension and actions. Voice previews provide an example voice; they do not guarantee the exact accent or behaviour during a live conversation. If a preview is missing, it is indicated as unavailable.
The configuration is also accessible via PATCH /api/v1/bots/{id}/prompting with default_lang: "it" or default_lang: "lb". Enabled codes and languages are detailed in your account’s API catalogue. The same bot modification permissions apply. Custom settings for a previously managed language are preserved.
Upon creation, the user’s time zone is suggested by default. Change it if the bot operates for another country or region.
Technical configuration and pricing
Customers and resellers configure their assistant without selecting an engine. The voice price is single and uniform for the organisation. Only a platform administrator can change the engine from a restricted technical panel on the bot. Other users cannot change it via API either; an explicit attempt returns 403. Modifying other parameters preserves the bot’s technical configuration.
Protection and inactivity
The configuration can limit anonymous, repeated or abusive calls. The inactivity timeout first warns the caller, then ends the conversation if no speech is detected. Choose a duration suited to your callers’ typical response times.
Faint voices and short responses
BeAI automatically applies a limited gain boost to low-volume voices before transmitting them to the voice engine. This helps detect short confirmations such as ‘yes, that’s me’. Silence and very low background noise remain untouched; this processing adds no waiting latency and does not alter the original recording. It applies to inbound and outbound calls, for bots configured via the UI or the API. It is not a substitute for good microphone quality and does not guarantee model or external tool response times.
Responsiveness and tool announcements
The default end-of-speech silence detection delay is 300 ms. A custom advanced value always takes priority. Increase this delay if the bot cuts off hesitations; reduce it with care. This is the detection delay, not a guarantee of total response time. Compatible parameters are grouped under Advanced voice settings; closing this panel preserves the values. See conversation settings and resumption and consumption limits.
The equivalent API for voice and its settings is PATCH /api/v1/bots/{id}/voice. The schema available to your account outlines the permitted parameters. Modification permissions and bot scope are identical across both interfaces.
The standard instruction directs the bot to utter a short, relevant announcement before the first lookup or business action for the same request: ‘Let me check availability’, ‘I am booking your appointment’. Follow-up lookups, detail reading and authorised actions related to the same request run in sequence without repeating this announcement or giving the same summary again. This includes checking a schedule followed by adding a note. If action parameters are invalid, it is rejected before execution; the bot receives the error to correct it or explain the issue. The bot speaks again with the results, an issue to explain or essential clarification to request. The system check for date and time (get_time) and number formatting (pronounce_phone_number) remain silent and do not count as a business announcement. If a calendar lookup follows, the bot announces that lookup after obtaining the time. Required confirmations remain mandatory, and success is only announced after the result. A goodbye is sufficient before hanging up; the post-call internal report remains silent. The execution of business tools no longer blocks the reception of audio or interruptions by the voice engine.
While a tool is running, BeAI automatically plays a subtle hold tone during periods of silence. It is generated by the telephony engine without requiring additional tools or model decisions, and stops as soon as the AI voice resumes speaking. It never overlaps with speech and is not triggered for hang-ups or the internal post-call report. This tone appears in the call recording, but is neither added to the transcript nor sent as model input.
During a campaign, identity confirmation should allow the conversation to proceed normally. The bot can use references, amounts and due dates already provided in the campaign context without redundant lookups. If it needs to explain billed services, it inspects invoice line items using authorised tools; a header reference alone is not sufficient. These guidelines apply to calls initiated from both the interface and the API.
The advanced voice configuration uses the neutral key voice_advanced in the API. For example:
{"voice_advanced":{"enabled":true,"silence_duration_ms":300}}
Legacy transport technical fields remain accepted for backwards compatibility; new responses and examples use neutral labels. The same values and permissions continue to apply.
Organisation and modification permissions
Creating and modifying a bot requires a manager, administrator or organisation owner role, or platform administrator permissions. A read-only account cannot create a bot, even when impersonating.
Before creating or modifying a bot, select the relevant organisation in the selector at the top of the page. The Organisation field maintains the bot’s assignment and only offers the currently open scope. Direct access allows you to manage the assigned organisation without granting access to its subsidiaries. If only one organisation is available, it is selected automatically without an empty option. Saving a modification retains the bot’s current owner.
The API uses the same permissions: specify organisation_id in POST /api/v1/bots or PATCH /api/v1/bots/{id}/identity to target an authorised organisation, including direct access. An organisation outside your scope will be rejected; no additional permissions are granted by the form.
If a field is incomplete or invalid, the save alert indicates its name. Click this name to open the relevant section and correct the field; values already entered remain in the form.
Duplicating via API (POST /api/v1/bots/{id}/duplicate) preserves web chat settings, but generates a new integration embed code specific to the copy. The original bot’s code remains unchanged.
The preview catalogue GET /api/v1/integrations/enreach/voices?lang=lb preserves the requested spoken language, independently of interface languages. Any voice without a sample in that language returns sample_url: null; no French recording replaces it. A malformed language code is rejected.