Choose your outbound caller ID

A bot using a BeAI Number presents its reserved number by default for outbound calls, callbacks, campaigns and external transfers. This setting does not change its inbound number or the Accessible via information.

Use a custom number

In the bot form, open Telephony → Outbound caller ID → Use another number. You must have permission to edit this bot and an active BeAI reservation, including a reservation in its grace period.

1. Select Belgium or France and enter the number. BeAI checks its format, category and carrier compatibility before offering a verification call.
2. Read and accept the declaration of your right to use the number. The checkbox is never selected in advance. Its version, date and user are retained.
3. Click Receive my code by phone — free. The window shows preparation, dialing and announcement playback.
4. Answer the call. The BeAI announcement reads a six-digit code twice, digit by digit. This call presents the bot’s reserved BeAI number, never the unverified candidate.
5. Enter the code and click Verify and use this number. Only this bot changes. Its previous caller ID remains active during verification.

You can select a number already verified by your organisation without another call. Use my BeAI number restores the reserved number. Verifications are not shared across organisations.

Eligible numbers and responsibilities

Ordinary Belgian fixed and mobile numbers are accepted. Special, freephone, premium-rate, short, satellite and M2M numbers are excluded.

For metropolitan France, mobile numbers cannot be presented through this fixed access. Only verified multipurpose numbers (NPV) with prior Sewan confirmation of authentication and automated use are eligible. Other French numbers remain unavailable, with an explanation before any call. Contact Beone if carrier authorisation is needed. Low-volume exceptions are not supported.

The code proves access to the line. It does not replace usage rights or the carrier’s obligations. You must have and maintain the right to present the number and report changes. Your declaration does not remove Beone’s legal obligations. See the BIPT CLI principles, Arcep authentication rules and numbering plan.

Timing, limits and failures

A code is valid for 15 minutes from creation, even if the call is delayed, and can be used once. Leading zeros count. Resending is allowed after 60 seconds. It creates a different code and immediately invalidates the previous one. Accept the declaration again if you closed the window.

Limits are shared between bots and users: five incorrect codes per number in fifteen minutes, three call requests per number in fifteen minutes, ten per number in twenty-four hours and twenty per organisation in twenty-four hours. Accepted requests count even if the line is busy or unanswered.

Ringing and announcement playback each last at most thirty seconds. An uncertain result never triggers automatic redial. A new call waits until the previous call is confirmed closed; Beone may need to investigate. Expired or superseded codes cannot verify a number.

Successful verification does not expire automatically. An organisation or platform administrator may revoke it for the whole organisation. Affected bots fall back to their BeAI number and show the reason in Telephony. Carrier incompatibility also causes fallback. Outbound calls are blocked without an active reservation or grace period. An existing call keeps its frozen identity until it ends.

Verification calls are paid by Beone, with no customer wallet debit. They create no AI conversation, transcript or recording. The public API never returns the code. Ordinary calls retain their usual billing.

Duplicating, importing or restoring a bot does not copy verification evidence or initiate calls. New bots use their own BeAI number by default.

Administration and API

Outbound caller IDs administration shows the carrier check, pilot bots, French carrier authorisations and recent verification calls. Custom numbers are enabled for customers only after live carrier acceptance testing. Outbound calls are blocked if the provider forces a common caller number or its check is stale. Manually reconcile an uncertain call only after confirming closure with the carrier and runtime.

GUI and API use the same services and permissions:

• GET/PATCH /api/v1/bots/{id}/outbound-identity: effective caller ID and selection (identity_id: null restores the BeAI number).
• GET /api/v1/organisations/{id}/outbound-identities: organisation identities.
• POST /api/v1/bots/{id}/outbound-identity/inspect: compatibility without calling.
• POST /api/v1/bots/{id}/outbound-identity/verifications: explicit request with declaration and idempotency key.
• GET /api/v1/outbound-identities/verifications/{id}: progress, expiry and resend time.
• POST /api/v1/outbound-identities/verifications/{id}/resend or /confirm: request another call or confirm a code.
• DELETE /api/v1/outbound-identities/{id}: administrator revocation.
• GET/PATCH /api/v1/platform/outbound-identities and POST /api/v1/platform/outbound-identities/verifications/{id}/reconcile: platform administration.

After an uncertain network response, reuse the same idempotency key and identical request. Responses never expose the code or provider credentials.