Schedule, announcements, and number cap
Schedule inbound calls, prepare versioned announcements, and monitor a usage cap with alerts.
In the bot editor, open Telephony, then Schedule, announcements, and number cap. These settings apply to inbound telephone calls. They are initially disabled and do not alter existing bots until you enable them.
Users authorised to view the bot can view this information and listen to saved versions. Making changes requires the same management permissions as editing the bot. The same organisation limits apply to API calls.
Prepare announcements
Prepare the calendar closed message and the service unavailable message separately. You can also create a dedicated message for an exception, such as an exceptional presence at a centre.
- Open Generate or import a new version under the desired message.
- Enter the text, language, and voice, or upload a WAV, MP3, or OGG file under 10 MB and two minutes long.
- Click Prepare a version to listen to.
- Listen to the result.
- Click Activate this version once you are happy with the content.
A successful generation never automatically replaces the active message. A generation error or new text does not alter the version already in use.
Each message retains up to five versions, including the active version. Upon the sixth successful generation, the oldest inactive version is removed from the history. The active version is never removed by this rotation. A preserved version can be reactivated without new synthesis; its text, audio, and date remain identical. Versions removed from the history can no longer be restored from this screen.
A call that has started playing an announcement keeps its audio file until the end. The service does not regenerate audio on every call.
Define the standard week
Add open slots under each day. Multiple slots allow you, for example, to close during lunch breaks. Uncovered hours are closed; a day with no slots is therefore fully closed.
- For round-the-clock availability, use 00:00–24:00 across all seven days.
- A slot spanning midnight must be split between the two days.
- Two overlapping slots are rejected; two adjacent slots are permitted.
- Times are interpreted in the specified time zone, including during daylight saving time changes.
You can duplicate a slot or use Copy day…. Overwriting existing slots requires an explicit confirmation. These actions prepare a draft; they do not save the settings immediately.
Add an exception
An exception has a label, a start, an end, and an open or closed status. It can cover a few hours or several days. A closed exception can use its own custom message; otherwise, the standard closed message is played.
The exception takes priority over the standard week. Its start time is inclusive and its end time is exclusive: at the end time, the standard week or the next exception resumes automatically. Two overlapping exceptions are rejected. A non-existent local time during daylight saving time transitions is also rejected, without silent shifting.
Duplicate prepares a new exception, whose dates you must review before saving.
Copy the schedule from another bot
Select Copy from another bot, choose an authorised source, and specify whether exceptions should be included. The preview indicates what will be overwritten.
Announcements and caps are never copied. If an exception used a specific message on the source bot, explicitly choose to revert to the destination's closed message before applying the copy. Copies are independent: editing the source does not modify destinations. The destination schedule's enabled/disabled state is preserved.
Set a spending cap
The cap limits usage of a number over a specified period. It does not top up the organisation wallet and does not trigger any payments.
- Prepare and activate the unavailability message.
- Enable the cap and enter its amount in euros excluding VAT.
- Set the start and end of the period.
- Optionally configure alerts and their recipients.
- Save at the top right.
Tracking breaks down the budget, billed amounts, holds for in-progress operations, available balance, and percentage consumed. A hold prevents multiple calls or SMS messages from simultaneously using the same available funds. It is reconciled against the actual recorded cost without a second wallet debit.
The spending base includes voice billed by BeAI, recording and analytics options, phone connections billed by BeAI, and SMS associated with the number. Third-party carrier invoices and included minutes without wallet deductions are not included in the consumed amount. Technical purchase costs are not used.
An organisation top-up does not increase the number's spending cap. Renaming the bot does not reset its usage to zero. Tracking remains tied to the number and its organisation.
The dates of a saved period are preserved. Explicitly start a new period creates another non-overlapping period and keeps the history. Changing the amount does not rewrite previous expenditure or alerts. No automatic renewal or reset takes place.
An enabled cap blocks new conversations outside its periods, both before their start and after their end. Explicitly disable it or set up a new period to restore service. A period too close to its end to fund the minimum processing time of a new call is also unavailable.
In-progress calls use bounded holds that are renewed during the conversation. When funding can no longer be extended, the service initiates a controlled termination playing the unavailability announcement within the already authorised time. We recommend keeping this announcement brief. Signalling times, roundings to the millionth of a euro, and potential final SMS costs differing from estimates remain limits to verify during acceptance testing; the counter retains the recorded cost.
A deferred SMS retains its reservation and the period of its original call: simply executing it after the period ends does not allocate it a new budget.
Email alerts
The proposed thresholds are 50 % and 80 % consumed. You can modify thresholds and recipients. Each threshold is logged only once per period, even if multiple operations cross it together. A progression that exceeds both thresholds prepares both alerts.
The history distinguishes between pending, queued, confirmed sent and failed. Failures are retried by the sending mechanisms; changing an amount or restarting does not recreate an already prepared alert. A new period has its own thresholds.
These emails contain the number, period and amounts, without any voice recording, transcript or caller message. The organisation's previous low balance alerts remain independent.
Understand how a call is handled
Existing security rejections and anti-spam continue to take precedence. For an authorised call, BeAI then applies this order:
- Insufficient usable credit or cap: unavailability announcement, then hang up.
- Schedule closed: announcement of closure or the applicable exception, then hang up.
- Otherwise: the bot's usual greeting and conversation.
An announcement alone does not start the conversational engine and does not collect a message. It does not trigger SMS messages from the standard scenario. Its audit trail is distinct from a conversation that took a request.
Telephony may still incur charges even without a conversational engine. Playing an announcement with a zero balance depends on telephony admission and the carrier: this must be verified for your connection before promising it. If audio is missing, the service uses the fallback technical announcement when available, then terminates the call; it never falls back to the bot. An error in calculating the decision rejects the call rather than opening an unauthorised conversation.
The preview for a selected date and time indicates the reason and the announcement version selected. It uses the saved settings and currently available credit; it does not predict future expenditure. Saved changes apply to new calls and do not replace the audio of a call already in progress.
Saving and API
The configuration change history keeps the last 100 effective changes: authenticated author, date, revision and modified fields, including audio version activations. When intervening while logged in as another user, the author remains the original operator. It contains neither caller content nor consumption counters. This history can be viewed on the same screen and in configuration_history via API read; it cannot be modified by the client.
There is a single Save button in the top right. After a change, the floating Unsaved changes reminder allows you to trigger this same action. An error preserves the draft. Preparing or activating an announcement is a separate command; it does not save your other changes.
The versioned API exposes the same permissions and validations:
GET /api/v1/bots/{id}/telephone-policy: settings, announcements, status, counters and history;PATCH /api/v1/bots/{id}/telephone-policy: partial modification of the schedule or cap;POST .../telephone-policy/preview: preview at an ISO date 8601;POST .../telephone-policy/copy-preview: independent copy for review, without implicit saving;POST .../telephone-policy/announcements/{key}/versions: generation or import with an idempotency key;POST .../versions/{version}/activateandGET .../versions/{version}/audio: activation and listening of an authorised version.
To copy a day or duplicate a time slot via the API, read the schedule, prepare the new slots, then send the full calendar.week array via PATCH. To duplicate an exception, copy its object without its id, adjust the dates, and send calendar.exceptions. Validations and conflicts are the same as in the console.
Counters are calculated by the server and are rejected on write requests. Provide the previously read revision to detect concurrent modifications. Following a conflict, re-read the configuration before submitting your draft. Refer to the detailed examples and formats in your account's API documentation.