Skip to main content
Belcenter AIHelp center
Configure a bot

Choose the outbound CLI

Validate a custom number, understand restrictions, and switch back to the BeAI number.

A bot in BeAI number mode displays its reserved number by default during outbound calls, callbacks, campaigns, and external transfers. This setting alters neither its inbound number nor the Accessible via entry.

Use a custom number

In the bot form, open Telephony → Outbound caller ID → Use another number. You must be able to edit this bot and have an active or grace-period BeAI reservation.

  1. Select Belgium or France and enter the number. BeAI verifies its format, category, and carrier compatibility before offering a call.
  2. Read and then tick the declaration of right of use. The box is never pre-ticked; the text version, timestamp, and user are recorded.
  3. Click Receive my code by phone — free. The window displays the preparation, call placement, and then the announcement playback.
  4. Answer the call. The BeAI announcement reads out a six-digit code twice, digit by digit. This call displays the bot's reserved BeAI number, never the number yet to be verified.
  5. Enter the code and click Verify and use this number. The change applies solely to this bot. Its previous outbound number remains active during verification.

A number already validated in your organisation can be selected directly in this window, without a new call. To revert to the reserved number, click Use my BeAI number. Validations are not shared with other organisations.

Permitted numbers and responsibilities

Belgium accepts standard landline and mobile numbers. Special, toll-free, premium rate, short, satellite, and M2M numbers are excluded.

For Metropolitan France, mobile numbers are unavailable on this fixed-line connection. Only verified multipurpose numbers (NPV) for which Sewan has confirmed authentication and automated usage can be offered. Other French numbers remain unavailable, with an explanation shown before the call. Contact Beone if carrier authorisation is required. Low-volume exceptions are not supported.

The code verifies access to the line; it does not replace usage rights or carrier obligations. You must hold the right to present this number, maintain this right, and report any change. The client declaration does not exempt Beone from its obligations. Consult the BIPT CLI principles, the Arcep authentication rules, and its numbering plan.

Time limits, thresholds, and incidents

The code is valid for 15 minutes from creation, even if the call is delayed, and can only be used once. Leading zeros count. A new call can be requested after 60 seconds: it generates a different code and immediately invalidates the previous one. Tick the declaration again if you closed the window.

Thresholds are shared across bots and users: five code errors per number per fifteen minutes, three call requests per number per fifteen minutes, ten per number per twenty-four hours, and twenty per organisation per twenty-four hours. An accepted request counts towards these limits even if the line is busy or unanswered.

Ringing and the announcement each last a maximum of thirty seconds. If the outcome is uncertain, BeAI does not call back automatically. A new call waits for the confirmed closure of the previous one; Beone may need to investigate the incident. An expired or replaced code can no longer validate the number.

Validation does not expire automatically. An administrator of your organisation or of the platform can revoke it for the entire organisation. Affected bots revert to their BeAI number and display the reason in Telephony. An operator incompatibility results in the same fallback. Without an active or grace-period reservation, outbound calls are prohibited. A call that has already started retains its identity until it ends.

The verification call is handled by Beone, at no charge to your wallet. It creates neither an AI conversation, nor a transcript, nor a recording. The code is never returned by the public API. Standard calls retain their usual pricing.

Duplicating, importing, or restoring a bot does not copy proof of validation and initiates no calls. A new bot uses its BeAI number by default.

Administration and API

The Outbound caller IDs administration section provides control of the trunk, pilot bots, French operator authorisations, and recent verification calls. Custom numbers are only made available to customers after successful acceptance testing with Sewan. If the provider imposes a shared number or if its verification is no longer up to date, affected outbound calls are blocked. An uncertain call should only be closed manually after verification on both the operator and runtime sides.

The same permissions and validations apply across the interface and the API:

  • GET/PATCH /api/v1/bots/{id}/outbound-identity: effective number and selection (identity_id: null to revert to the BeAI number).
  • GET /api/v1/organisations/{id}/outbound-identities: organisation identities.
  • POST /api/v1/bots/{id}/outbound-identity/inspect: compatibility without placing a call.
  • POST /api/v1/bots/{id}/outbound-identity/verifications: explicit request with attestation and idempotent key.
  • GET /api/v1/outbound-identities/verifications/{id}: status, expiry, and timestamp of the next permitted resend.
  • POST /api/v1/outbound-identities/verifications/{id}/resend or /confirm: new call or code confirmation.
  • DELETE /api/v1/outbound-identities/{id}: revocation by an administrator.
  • GET/PATCH /api/v1/platform/outbound-identities and POST /api/v1/platform/outbound-identities/verifications/{id}/reconcile: platform administration.

Following an uncertain network response, reuse exactly the same idempotent key and request. Responses never expose the code or the provider’s secrets.

Documentation updated with the application