Add and configure skills
Choose useful capabilities, distinguish silent tools from announced searches, and limit actions.
A skill adds a capability to the bot: sending a message, checking a calendar, querying a CRM, or triggering an automation.
For webhook automation, the name, URL, description, usage instructions, and activation status remain directly accessible. Open Technical request settings to modify the HTTP method, authentication, and the schema of the information sent. Closing this panel preserves the parameters and does not disable the automation. Any missing mandatory schema must still be completed before saving.
Choose a skill
In the bot configuration, use Add a skill. The picker displays available capabilities, their description, and their current status. Search for a name or need, then select the desired skill.
Already selected skills remain visible to avoid duplicates.
Principle of least privilege
For each skill:
- only activate useful actions;
- restrict recipients, templates, or resources;
- clearly instruct the bot when to trigger the action;
- ask the caller for confirmation whenever an action has a significant impact;
- test both a successful outcome and a failure case.
Common skills
| Need | Suitable skill |
|---|---|
| Send a recap | Email or SMS |
| Book an appointment | Microsoft 365, Google, or Progenda calendar |
| Create a ticket or look up a customer | Odoo, HubSpot, or Zendesk |
| Call a department or schedule a callback | Outbound call or contact callback |
| Run an external scenario | Webhook automation |
Send data to an automation
Under Webhook automation, open Technical request settings and describe the information to send. The schema uses the BeAI format: each field contains label, type, required, and optionally example. Types string, number, integer, boolean, object, and array are supported. For a nested object, example describes its fields using the same structure. Examples clarify the expected format: they are never used as default values.
{
"motif": {"label": "Motif de la demande", "type": "string", "required": true},
"a_rappeler": {"label": "Faut-il rappeler ?", "type": "boolean", "required": true},
"nombre_personnes": {"label": "Nombre de personnes", "type": "number", "required": false}
}
The bot receives these fields and their types in its tool description. Before sending the request, BeAI validates mandatory fields and types. A missing or invalid field results in invalid_automation_payload: no HTTP request is sent. A boolean false or numeric 0 value remains an actual value; strings "false" and "0" are not automatically converted. An optional field may be omitted. If an optional object is supplied, its mandatory fields are still validated. An unreadable legacy schema results in invalid_automation_schema, without sending.
The recipient receives the values of the payload field, directly at the root of the JSON body for a POST request. Additional fields continue to be passed to preserve existing integrations. BeAI does not silently inject conversation IDs, caller numbers, or other metadata. The HTTP status code and response payload are returned to the bot during the session. An HTTP 200 confirms technical receipt; the payload must confirm the business outcome. An HTTP error or timeout is not a success. Following an ambiguous result, check the recipient service before retrying an action that could run twice.
An instruction to trigger "at the end of the call" executes the tool during the conversation, before hanging up; it does not guarantee execution if the caller hangs up early. A server-side post-call event is a separate mechanism. Technical diagnostics restricted to platform administrators show the names and types of sent fields, the JSON payload size, and a request ID, without copying their values or authentication secrets.
The same contract applies to calls, WhatsApp, Messenger, and web chat. Configuration via GET/PATCH /api/v1/bots/{id}/skills/automations uses the same schemas and checks as the console; bot edit permissions are still required. The patch does not re-enable any removed automation.
Automatically receive call summaries
In the Email skill, enable the automatic summary after each conversation, add recipient email addresses, and save the bot. This option is separate from emails sent by the bot under specific circumstances during a call. Call recording is optional; you can choose to attach the recording when available.
After a call ends with an AI session and a summary, BeAI prepares the email for the configured recipients. This trigger works regardless of the call's billing mode. A retry of the call wrap-up does not resend an already queued summary. Test simulations, calls filtered by antispam, and calls without a summary do not trigger this email. Queuing may precede receipt: an email delivery issue can delay receipt, and a summary visible in the call history does not alone prove that the email has been delivered.
The same bot edit permissions and the same settings are available with GET/PATCH /api/v1/bots/{id}/skills/emails, via enabled and summary_email (enabled, recipients, attach_recording). For example:
{"enabled":true,"summary_email":{"enabled":true,"recipients":["accueil@exemple.be"],"attach_recording":false}}
If you stop receiving emails, verify that the skill and automatic summary remain enabled, that the email addresses are correct, and that the call does indeed have a summary in the history. Also check your junk/spam folder, then provide support with the IDs of the affected conversations if the issue persists.
Configure a call transfer
Open the Transfers skill, add a Destination, and describe when the bot should route to it. On a classic SIP connection, a destination can be an internal extension such as 611, or an external landline/mobile number written in explicit international format, for example +32475123456. On a SIP connection managed by BeAI, use a reachable international landline/mobile number: the call leg is subject to applicable rates and available credit. The bot announces the transfer before executing it; it only routes to saved destinations.
Number format guidance is displayed once beneath the destination list. Each line contains the destination and its description.
Internal extensions contain between 2 and 6 digits. A two-digit extension may start with zero: 01, 02, 03, or 04, for example. The leading zero is preserved when saving and during the transfer; always enter the destination as text in the API ("extension":"01"). For extensions longer than two digits, a leading zero is rejected in classic SIP to prevent confusion with a public number or an outside line prefix. Emergency numbers 112, 911, 999 and directory enquiries 118… are rejected. An extension is treated as internal to your PBX: your telephony administrator must reserve this range for internal extensions and prevent it from routing to public numbers, outside prefixes, or premium-rate services. The software cannot verify your carrier's dial plan. In particular, a short public number must never be added as an extension.
An external number must begin with +, without spaces, separators, suffixes, or SIP URIs. National formats and 00 prefixes are rejected. Only valid numbers classified as landline, mobile, or fixed/mobile are accepted; special, premium-rate, toll-free, shared-cost, personal, VoIP, non-geographic, or unknown types are excluded. In particular, Belgian ranges 070 and 090… are premium-rate services, as outlined by the BIPT. The Dutch range +3197… is also excluded because its mobile classification may cover M2M services.
This check uses libphonenumber metadata. It proves neither number assignment, nor availability, nor the price actually billed: classification has limitations detailed in the libphonenumber FAQ. Your carrier or PBX fees and restrictions still apply. A missing tariff, insufficient credit, or a carrier rejection can prevent the transfer.
Enreach Picapp accepts a mixed list: choose an extension from the company directory or add an international external number validated by the same allowlist policy. Names, types, and presence rules for internal extensions remain managed by Enreach. No contact or presence status is created for an external party; transfer permissions, rejections, and carrier charges still apply. See the Picapp walkthrough.
The same bot editing permissions and validation apply in the console and in PATCH /api/v1/bots/{id}/skills/transfers. Example for a standard or managed SIP connection:
{"enabled":true,"destinations":[{"extension":"+32475123456","description":"Joindre le service commercial lorsque l’appelant le demande."}]}
The historical API field extension also contains the external number; no free-form URI field is accepted. An invalid destination is rejected upon saving (API: HTTP 422). The check is also re-run before the transfer: an outdated invalid configuration or a removed destination cannot be used to bypass restrictions. Anti-spam redirections follow the same number restrictions; a URI to the bot's own SIP domain remains usable only with a safe destination. An outdated invalid redirection causes a rejection or a hang-up after a message depending on the chosen action. If external number validation does not load in the browser, reload the page; server-side checking remains active without JavaScript.
In the Antispam skill, select the action that plays a message before hanging up or transferring, then upload the announcement. If the custom file is unavailable or silent, the system uses the default recording when configured. Silent uploads are rejected when saving, and the existing announcement is kept. Listen to your file before uploading it again.
Send an SMS after hang-up
In the SMS skill, open Post-call SMS, enter the validated text, and enable the option. It remains disabled on existing bots. The delay is an integer from 1 to 120 seconds; shortcuts offer 1, 5, 15, 30, 60, and 120 seconds. The recipient number remains that of the caller and standard skill permissions continue to apply: this option does not automatically authorise other recipients.
Choose After each eligible conversation or When the scenario is confirmed during the call. In the latter case, specify in the instructions when the scenario is completed; the bot has the prepare_post_call_sms tool to confirm this, without sending during the call. The minimum duration excludes calls that are too short; it is 5 seconds by default. A closing or credit announcement alone, a failed call, silence without caller participation, and a conversation without AI initiation are not eligible.
The text accepts only {{ bot_name }} and {{ centre_name }}. Enter confirmed dates and times directly into the text; no transcript or summary is required. Settings and the message are locked at the start of the call. Subsequent changes apply to future calls; disabling prevents unsent tasks from being dispatched.
The delay begins upon confirmed SIP termination, including when the caller hangs up. It controls submission to the provider, not delivery on the handset. The target is rounded up to the nearest second to prevent any premature dispatch. The scheduler checks tasks every second; rounding and this check add up to approximately two seconds, excluding server load and network latency. If credit or the spending cap is still reserved for the call upon hang-up, tracking remains pending and re-checks availability without submitting an SMS. It keeps its original target and expires ten minutes after it to prevent stale dispatch.
A withheld, missing, landline-identified, or incompatible number, recipient restrictions, insufficient credit, or reaching the number cap will block sending. If the rejection is known during the call, the bot must convey the information verbally and must not ask for another number to bypass the restriction. A failure after hang-up remains a failure, with no claim to a verbal fallback.
The conversation details show the status, due time, and actual submission. Submitted is not Delivered. A definite rejection releases reserved credit; an uncertain provider acceptance retains the reservation for diagnostic purposes and is never resent blindly. An identical SMS content already accepted or with uncertain acceptance for the same recipient cancels the deferred sending. Tasks are not replayed upon duplicate hang-up notifications. Deleting a bot or conversation with active or uncertain tracking is prevented to preserve auditability; ask your administrator to verify an uncertain result before deletion.
Users authorised to edit the bot will find the same settings and validations via GET/PATCH /api/v1/bots/{id}/skills/sms:
{"post_call":{"enabled":true,"delay_seconds":15,"recipient":"caller","trigger_policy":"scenario_confirmed","minimum_duration_seconds":5,"centre_name":"Centre A","message_template":"Retrouvez-nous au {{ centre_name }} aux dates validées : …"}}
A delay of 0, 121, or a fractional value is rejected; a PATCH retains omitted fields. GET /api/v1/conversations/{id} also exposes tracking post_call_sms, subject to conversation permissions.
Understanding action errors
An external action can be rejected even if the bot is operating correctly. The tool result appears in the conversation. Check the connection, the external account permissions, and the authorised parameters before modifying the prompt.
The Create your first bot walkthrough shows a minimal configuration with email, calendar and call transfer.
During a search
The bot uses the necessary tools without repeating "I'm checking" at every step. When it announces a search, a single announcement is sufficient for the request. A discreet tone plays during the wait and remains active between tool results and the actual resumption of speech. The bot then delivers the verified response, indicates if something is not possible, or asks for necessary clarification or confirmation. A new request can start a new sequence. Confirmations required before a write operation remain mandatory.
A search can also continue in the background while the bot continues speaking, listens to you, or answers another independent question. No systematic waiting announcement is required in this mode. The result is presented during a natural pause; an action is never announced as successful before confirmation by the relevant service. Steps that depend on a result wait for that result.
Silent system tools, such as get_time (date and time) or formatting a number to be spoken, do not count as an announcement and do not reset an already announced sequence. For example: silent calculation of "tomorrow" → calendar search → additional reading → verified answer, with a brief announcement if helpful. If only technical tools are required, the bot answers directly without a search announcement.
This operation is common to bots configured in the console and via the API. Avoid adding an announcement before every tool or retry in your instructions.
Messenger
The Messenger skill replies to written messages on your Facebook Page, independently of WhatsApp. First save a new bot, then use Connect Messenger and select a Page in the Messenger walkthrough. The connection is activated only after server confirmation.
Analyse calls with self-improvement
Enable the Auto-improvement skill, choose the percentage of calls to analyse, and save the bot. BeAI analyses the audio of selected calls after they conclude, then displays its recommendations under Auto-improvement on the bot details page. These suggestions do not automatically amend the bot's instructions.
A call may remain temporarily pending during processing. Analysis requires a usable recording: missing or silent audio cannot yield suggestions. If analyses fail repeatedly, provide support with the relevant conversation IDs; no technical token needs renewing in the bot form.
The same permissions and settings are available via GET/PATCH /api/v1/bots/{id}/skills/auto-improvement, with enabled and sample_rate. For example: {"enabled":true,"sample_rate":50}. The post-call processing outcome is identical for bots configured in the interface and via the API.