Obtain a BeAI Number
Reserve a Belgian number, track its assignment and Sophia feedback, and configure rates.
The BeAI number — no SIP configuration required option automatically assigns a Belgian landline number to your bot. You do not need a telephone switchboard (PBX) or SIP credentials. This feature must have been enabled by the platform administrator.
Calls in BeAI number mode automatically prioritise G.722 for HD voice, with fallback to PCMA, then PCMU according to the codecs offered by the carrier. No additional configuration is required, whether the bot is set up in the interface or via the API. HD quality also depends on the calling telephone and the carrier route: a call received solely in PCMA remains in standard telephone quality.
Reserve a number
- Click New bot, then select BeAI number. The annual price and any surcharges are displayed prior to configuration: no SIP account or server details required.
- Select Create with assistant or Configure manually, then configure your bot. From its details page or Telephony → Manage BeAI number, open the reservation to confirm the price for its organisation.
- Tick the confirmation box then click Reserve. The default price is 10 € excl. VAT per year; the displayed amount is authoritative.
- Wait for activation. The number is automatically selected from the available stock. If necessary, BeAI orders an additional number.
The comment visible in Sophia GO stock is populated automatically after a number is purchased or assigned, then updated upon assignment changes:
BeAI Number - Bot #XYZ: number linked to botXYZ; reassigning replaces this identifier with that of the new bot.BeAI Number - Reserved - Org #XYZ: number detached but still reserved for organisationXYZ, including during ongoing technical release.BeAI Number - Free: reservation ended and number available again in the pool.
The update runs in the background and may take a few seconds. A Sophia error is automatically retried, without placing a new order or charging again. Under Platform administration → BeAI numbers, the expected comment and its synchronisation status are displayed under the number; a scheduled retry indicates that Sophia has not yet confirmed the change. Numbers excluded from the pool are not modified. The historical resellerComment field in the Sophia API is distinct from the editable comment in the GO stock.
The interface and API use the same processing. Administrators can view the fields expected, confirmed, status (pending, synced, retry), and error in sophia_comment of GET /api/v1/platform/managed-sip/numbers. The comment is generated by BeAI: no free text or additional permissions are required.
Annual credit is reserved during provisioning. Charging and the paid year begin only once number routing is confirmed. A definitive failure refunds the reserved credit. In the event of an inconclusive provider operation, the reservation remains pending verification to prevent duplicate ordering.
Saving, duplicating, importing, or restoring a bot never reserves a paid number. If the price changes before your confirmation, reload the page and confirm the new amount.
Both configuration paths preserve the telephony selection. Reserving a paid number remains subject to explicit confirmation.
A configuration tailored to your telephony
The Telephony menu replaces the SIP menu. In BeAI number mode, it displays the number, price, reservation links, and options relevant to calls. SIP accounts, passwords, servers, codecs, and registration settings are hidden.
The Manage BeAI number button opens a modal within the form: price, credit, confirmation, status, and renewal are consolidated. Actions and monitoring update without leaving the form or discarding unsaved changes. Rates open in a new tab. If you have changed the bot's organisation, save this change before managing the number to ensure the correct price and wallet are used. Reusing an already paid number only appears when an eligible reservation exists.
In the bot list, a small green telephone identifies the BeAI Number mode instead of the SIP status dot. Its tooltip indicates whether the number is assigned or still pending. Green identifies this telephony mode; check the reservation to view its activation status.
The Reachable via column automatically displays the assigned BeAI number, beneath your custom label or on its own if none was entered. Your text remains unchanged: it never overrides the actual number. After detaching or reassigning, the number row disappears from the former bot upon the next list load; it appears on the bot to which the number is now assigned. A number currently being provisioned is displayed only after activation.
In GET /api/v1/bots and GET /api/v1/bots/{id}, reachable_via preserves your text and managed_number separately provides the assigned read-only number, for example {"reachable_via":"Accueil commercial","managed_number":"+3271123456"}. managed_number is null without an activated BeAI number or for a standard SIP bot. Bot access permissions apply identically in the list and in the API.
For platform administrators, the Runtime node column displays both nodes when the number is supported by both runtimes in the environment. Each badge indicates the availability of its node; an unavailable node remains visible in red. Filtering by node finds this bot under each of its nodes. Standard SIP bots retain their registration node.
The carrier distributes new trunk calls across the configured gateways. A call is handled by a single runtime, which remains responsible for that call until hang-up. Load balancing does not duplicate calls or their billing, nor does it transfer an ongoing conversation to another node. The badges indicate the runtimes' capability to receive an active number; they do not guarantee that the carrier has enabled its network routing. A bot in test mode, a template, a number without an active reservation, or a bot from another environment does not display this support.
The same information is available to platform administrators in GET /api/v1/runtime?bot_ids[]=138, under data.runtime.bot_assignments, with mode: shared and the nodes list (name, available). The runtime_nodes[] filter accepts each node. This new information and filter are restricted to the same platform permissions as the table column; bot access restrictions continue to apply.
The Switch to SIP button displays provisioning and manual configuration. Save changes to apply them. Conversely, Switch to a BeAI Number displays the configuration-free flow. Selecting this option alone does not reserve any number. When an administrator changes the bot's organisation, the displayed price updates; final confirmation always uses the paying organisation's pricing.
Understanding statuses
| Status | Meaning |
|---|---|
| Provisioning | BeAI assigns or orders the number and verifies its routing. |
| Active | The number can be used until the indicated expiry date. |
| Grace period | Renewal is awaiting a wallet top-up. |
| Release in progress | BeAI closes communications and removes previous assignments. |
| Released | The reservation has ended; the number can be assigned to another organisation. |
| Failed | Provisioning failed; the reserved annual credit has been refunded. |
The modal displays the number, expiry date, auto-renewal status, and alerts. A technical issue may delay activation or the release of the number back to the pool.
Renewal and grace period
Renewal is automatic on each anniversary date. BeAI announces the renewal amount thirty days before the expiry date, then sends an expiry reminder seven days before. This amount remains fixed for the announced renewal, even if your pricing schedule changes subsequently.
If credit is insufficient, the reservation is retained for one calendar month, with an immediate alert and weekly reminders. Top up promptly: BeAI regularly retries payment, as well as after a confirmed top-up. A payment made during the grace period preserves the original anniversary date.
At the end of the grace period without payment, the number is detached and returned to the pool. It can immediately be assigned to another organisation. Do not publicise or use this number once your reservation has ended. Retaining the number during the grace period does not waive the credit required for calls.
Expiry dates follow the Brussels calendar, including daylight saving transitions, month ends, and leap years.
Changing bots or cancelling renewal
You can disable renewal or detach the number. The period already paid for remains yours, with no pro-rata refund. The number remains reserved for your organisation until its expiry date and can be reassigned to another of its bots without an additional annual payment. After detaching, explicitly re-enable renewal if you wish to keep the number for the following year.
Leaving BeAI Number mode or deleting the bot detaches its reservation and stops its renewal. The reservation belongs to the organisation and remains viewable in its telephony pricing. Reassignment to another organisation is prohibited.
Outbound call and transfer costs
Outbound calls and external transfers routed via the BeAI trunk incur an additional telephony charge: connection fee and per-minute price. Check View pricing before use.
For each answered leg, the first minute is indivisible; thereafter, billing is calculated per second, rounded up. An initial Belgian call of 30 seconds costs 0,144 € excl. VAT in telephony charges; a call of 90 seconds costs 0,184 € excl. VAT, in addition to AI consumption.
Initial rates are based on the generic country line from the Beone public tariffs 2026, connection included. This rate applies to both landlines and mobiles. Territories sharing a dialling code may have distinct rates. Destinations without defined rates are blocked, as are premium, special, satellite, and short codes.
An unanswered attempt incurs no extra charge. If the callee answers but the AI fails to start, Beone covers the telephony cost.
During an external transfer, BeAI maintains both call legs. AI consumption stops once connected; telephony consumption continues until hangup, including for automatic redirects. A transferred outbound call may therefore involve two telephony legs billed simultaneously. Transfers that fail before being answered are not billed.
Number reservations and calls share the same available credit. The credit required for connection and the first minute is reserved prior to the call. A call is disconnected if its required budget can no longer be funded. History distinguishes AI, connections, and telephony minutes; a price change does not recalculate past calls.
Viewing and configuring pricing by country
View pricing opens a consultation page displaying the annual price, followed by countries and territories: a flag, name, dialling code, connection fee, and per-minute price. All amounts are in euros excl. VAT. Belgium appears first, followed by destinations in alphabetical order. Search for a country or dialling code and use the arrows to browse pages. Territories sharing a dialling code remain distinct.
With permission to edit the organisation, select Configure pricing, which is also accessible from organisation settings. Modify the annual price or the rates alongside each country. Rate to be defined indicates that a destination is blocked until both rates are entered; an empty amount is not treated as zero.
For resellers, the This organisation and New customers tabs separate the current pricing schedule from the values copied when creating new clients. Searching, pagination, and switching between tabs preserve pending changes. Save pricing saves changes from both tabs together; Discard changes restores the last saved values. Hierarchical pricing limits still apply, and consumption history remains unaffected.
A saving error preserves your input. If another user has updated the pricing schedule in the meantime, make a note of your changes, then reload the page to work on the updated pricing. The Number reservations panel at the bottom of the page allows you to locate the organisation's reservations.
Tracking provisioning
Following confirmation, the modal displays an animated progress bar and the stages Request received, Assigned number, then Ready to receive. The status text indicates whether BeAI is selecting the number, awaiting its routing, or completing activation. This bar indicates that processing is in progress, not a percentage of remaining time.
The request is handled continuously, without waiting for batch processing by the minute. An already routed number can be activated in a few seconds; routing or ordering depends on carrier confirmation and may take several minutes. Tracking updates every two seconds while the modal is open. You may close it: provisioning continues and your form edits are preserved.
Upon activation, a green card with a smile displays Your number is ready!, along with the number and its expiry date. The buttons then allow you to manage renewal or detach the number. If confirmation takes longer than expected, the modal indicates this: do not submit a second reservation. In the event of additional checks, your request is kept until the outcome is clarified.
Permissions and API
Reserving and managing a number requires permission to edit the bot. Managing a detached reservation and pricing requires permission to edit its organisation. Bot and organisation access restrictions also apply to these pages. Administrators can edit pricing within the limits of their organisation hierarchy.
The same operations are available in the public API: consultation and reservation via /api/v1/bots/{id}/managed-number, management via /api/v1/managed-numbers/{id}, reservation list and pricing under /api/v1/organisations/{id}. Retain the same idempotency key and quote version when retrying confirmation. The response also exposes created_at and, during provisioning, preparation.stage (allocation, routing, activation, or verification) and preparation.poll_after_seconds. After activation, preparation is set to null. The OpenAPI documentation provides details on permissions, fields, and examples.
Resellers also have a Default prices for new clients schedule. These prices are copied upon client creation; existing organisations retain their own pricing. The API uses the child_defaults field in the pricing schedule. Detailed breakdown of charges per call leg appears in billing_details of conversations.
RTP test mode does not permit reserving or using a BeAI number. Disable it before confirming a reservation.
Pool administration
In Platform administration → BeAI numbers, each row displays the number, its status, organisation, linked bot, expiry date, and renewal status.
- Unlink from bot retains the paid reservation within its organisation and stops renewal.
- Link to a bot or Reassign suggests eligible bots. A paid reservation remains restricted to the same organisation, with no new annual charge.
- For an available number, select a bot and then confirm the annual price and any add-ons. The credit is held, then charged upon activation. The selected number is locked: if it has already been taken, the action is rejected, without replacement or implicit ordering.
- Renewal can be stopped or reactivated from this page when a bot is linked.
These actions are restricted to platform administrators. The API exposes the same assignments with GET /api/v1/platform/managed-sip/numbers, eligible bots with GET /api/v1/platform/managed-sip/assignment-bots, and actions with POST /api/v1/platform/managed-sip/numbers/{id}/assignment. Send bot_id:null to unlink. For an available number, include confirmation, the bot quote version, and an idempotency key; a 202 response indicates a pending activation.
If the reservation page indicates that assignment is not enabled, the administrator must use Enable new bookings in this administration after carrier verification. The presence of available numbers in the pool does not supersede this activation. The same setting is available with PATCH /api/v1/platform/managed-sip and enabled:true. Once enabled, the reservation button appears when reopening the window; price confirmation and sufficient credit remain required.
The price preview before creation is available with GET /api/v1/organisations/{id}/managed-number-offer. Bot creation uses sip.configuration_mode: managed_beai without SIP credentials and does not trigger a reservation.
New provider orders use Beone, Rue de Trazegnies 218, 6180 Courcelles, Belgium, with the geographical postcode 6180. The town or city indicated on a reused stock number may reflect its original order; it does not mean a new order was placed for this bot.
Remove a number from the BeAI pool
In the platform administration BeAI numbers, a platform administrator can select Remove from pool for a number with no current reservation. The number leaves the pool list and appears in the collapsed Numbers excluded from the pool section, along with its reason. It can no longer be assigned automatically or manually, even if a Sophia synchronisation still marks it as available.
This exclusion is local to BeAI: it does not cancel the number with the carrier, nor does it delete past reservations or their billing. It is particularly suitable for a number where carrier cancellation has been requested but is still pending or has been refused. Unlinking a bot is not sufficient to exclude its number: any retained reservation period must first be completed. An ongoing provider operation temporarily blocks modifications; try again once it finishes.
Return to pool cancels the exclusion. Then run Sync pool: only availability confirmed by Sophia allows for a new assignment.
The public API uses PATCH /api/v1/platform/managed-sip/numbers/{id}/pool with {"excluded":true,"reason":"Résiliation fournisseur demandée"} or {"excluded":false}. Permissions and checks are identical to the interface. Inventory GET /api/v1/platform/managed-sip/numbers also includes the exclusion history: pool_excluded identifies them, pool_exclusion_reason specifies the reason, and eligible remains false for these numbers.
For outbound calls and transfers, see Choose the outbound caller ID.
Identity and zone for Sewan orders
New numbers are ordered in the name of BE ONE GROUP (Beone), Rue de Trazegnies 218, 6180 Courcelles, Belgium. Postcode 6180 corresponds to the Sewan zone 064 / Anderlues. The BeAI client billing address never replaces this carrier address.
Before each purchase, BeAI reviews the organisation and site in Sewan and verifies their identity, address, and postcode zone. Any discrepancy blocks preparation, without ordering in another zone. The geographical category is sent explicitly. Automatic assignment from the pool also uses zone 064; already active reservations are retained.
An uncertain provider response must still be reconciled: do not recreate a request in an attempt to bypass it. The same checks apply to reservations made via the GUI, API, and website registration.
A former cancelled reservation can also be reconciled by the platform admin: following verification with Sewan, confirming the absence of a purchase removes the block without reactivating the reservation. If a number was genuinely purchased, linking it to the operation leaves it free in the pool; it is not assigned to the former bot. The same check exists in the GUI and via the reconciliation API.
Sewan API access uses a service account, with its own application credentials and profiles limited to BE ONE GROUP. The profile displayed in Sophia is not sufficient proof of purchasing rights: the account must actually have the OrderPhoneNumber authorisation on this organisation. Inventory reading or trunk management may function while purchasing remains prohibited.
If Sewan rejects the order due to insufficient permissions (number_order_permission_denied), the platform admin must have the ordering rights corrected for the Sewan service account, then reserve the number on the bot again. No purchase is retried automatically after this rejection; the subscription payment remains valid and must not be restarted. A truly uncertain provider response remains blocked for reconciliation.