Get a BeAI Number

BeAI Number — no SIP configuration required automatically assigns a Belgian fixed number to your bot. This service must first be enabled by the platform administrator.

Calls in BeAI Number mode automatically prefer G.722 for HD voice, falling back to PCMA, then PCMU, depending on the codecs offered by the carrier. No additional setting is required, whether the bot is configured in the interface or through the API. HD quality also depends on the caller’s phone and carrier path: a call offered only in PCMA retains standard telephone quality.

Reserve a number

1. Choose BeAI Number in your bot's SIP connection settings and open its reservation dialog.
2. Read the annual price and telephone rates. The default annual price is €10 excluding VAT; your organisation's displayed price applies.
3. Confirm the charge and select Reserve. Sufficient wallet credit is required.
4. Wait for activation. BeAI selects an available number or orders one when necessary.

The visible Sophia GO stock comment is set after purchase or assignment and kept up to date: BeAI Number - Bot #XYZ for the current bot, BeAI Number - Reserved - Org #XYZ while detached but still reserved (including technical release in progress), and BeAI Number - Free only once released and available in the pool. Reassignment changes the bot ID.

Synchronization runs in the background and normally takes a few seconds. Provider errors are retried without another purchase or debit. Platform administrators see the expected comment and pending/retry status below each number. Excluded numbers are not modified. Sophia's legacy resellerComment field is distinct from the editable GO stock comment.

GUI and API use the same process. GET /api/v1/platform/managed-sip/numbers exposes sophia_comment with expected, confirmed, status (pending, synced, retry) and error under the same platform permissions. No free-text input or additional permission is required.

The annual amount is held during provisioning and debited once routing is confirmed. The paid year starts at activation. A definitive failure releases the hold; an uncertain provider operation waits for reconciliation to avoid duplicate purchases. Saving, duplicating, importing or restoring a bot never implicitly reserves a paid number. A changed quote requires fresh confirmation.

Track preparation

In the bot list, Reachable via automatically shows the assigned BeAI number below your own label, or on its own if the label is empty. Your text is preserved. After detachment or reassignment, the number disappears from the previous bot when the list reloads and appears on its current bot. Pending numbers appear only after activation.

GET /api/v1/bots and GET /api/v1/bots/{id} keep your text in reachable_via and return the assigned number separately in read-only managed_number, for example {"reachable_via":"Sales reception","managed_number":"+3271123456"}. This field is null without an activated BeAI number or in ordinary SIP modes. The same bot access permissions apply to the GUI and API.

The bot form's dialog shows an animated progress bar and the observed steps: request received, number assigned and ready. It refreshes every two seconds while open. The bar does not estimate time remaining. Requests are processed continuously; an already routed pool number can be ready within seconds, while operator routing or a new order can take several minutes. Closing the dialog does not cancel preparation or discard unsaved bot edits.

When activation is confirmed, a green card with a smile shows that your number is ready, its number and expiry, followed by renewal and detach controls. A delayed or uncertain confirmation remains pending: do not submit another reservation. The public API exposes the same progress through created_at, preparation.stage (allocation, routing, activation, verification) and preparation.poll_after_seconds; preparation is null outside the pending state.

Reservation states and renewal

The reservation page shows provisioning, active, grace, release pending, released or failed states, together with the number, expiry, renewal setting and alerts. Technical problems can delay activation or release.

Renewal occurs on the activation anniversary. Its price is announced 30 days before expiry, with a reminder seven days before. That announced price stays fixed for the upcoming renewal.

Insufficient credit starts a one calendar month grace period. BeAI alerts you immediately, sends weekly reminders and retries regularly and after a confirmed recharge. Payment during grace preserves the original anniversary. Calls still require sufficient credit during grace.

If grace expires unpaid, BeAI detaches the number and closes its calls before releasing the reservation. Stop advertising or using a released number: it may immediately be assigned to another organisation. Provider restrictions and technical issues may delay reuse. Dates follow the Brussels calendar, including daylight saving, month ends and leap years.

Reassign or stop renewal

You can disable renewal or detach the number. The paid period remains available to your organisation, with no prorated refund. Reassign the reservation to another bot in the same organisation without another annual charge. After detaching it, explicitly re-enable renewal if needed.

Leaving BeAI Number mode or deleting its bot detaches the reservation and disables renewal. Detached reservations remain accessible from the organisation's telephone rates page. Moving a reservation to a different organisation is prohibited.

Outbound telephone charges

Outbound calls and external transfers through the BeAI trunk incur an additional connection fee and per-minute price. Use View rates before calling. Each answered outgoing leg has a minimum of one minute, followed by per-second billing rounded upward. Initially, a Belgian call costs €0.144 for 30 seconds or €0.184 for 90 seconds, excluding VAT and AI usage.

Initial rates use each country's generic row in the Beone 2026 public rate plan, including its connection fee, for both fixed and mobile numbers. Territories sharing a calling code can have different rates. Destinations without configured rates are blocked, as are special, premium, satellite and short numbers.

Unanswered attempts are not charged. If the operator answers but AI startup fails, Beone absorbs the telephone cost. During an external transfer, BeAI keeps both call legs until hangup. AI consumption stops when connected; telephone consumption continues, including automatic redirects. An outbound call transferred externally can therefore have two simultaneous chargeable telephone legs.

Number reservations and simultaneous calls share available wallet credit. Connection and first-minute credit are held before dialing; a call ends when further credit cannot be funded. History separates AI, connections and telephone minutes. Later rate changes never recalculate past calls.

View and configure country rates

View rates opens a read-only catalogue with the annual price and each destination's flag, name, calling code, connection fee and per-minute price, all in euros excluding VAT. Belgium appears first, followed by countries alphabetically. Search by country or calling code and use the pagination arrows. Territories sharing a calling code keep separate rows.

Users who can edit the organisation can select Configure telephone rates, also linked from the organisation configuration. Edit the annual price or the amounts next to each country. Rate to define means the destination remains blocked until both prices are configured; a blank price is not zero.

Resellers have separate This organisation and New customers tabs. Search, pagination and switching tabs retain pending edits. Save rates saves changes in both tabs together; Cancel changes restores the last saved values. Organisation hierarchy price limits still apply and historical usage is never repriced.

Errors preserve your input. If someone else has changed the grid, note your edits before reloading to obtain the current rates. Expand Number reservations at the bottom to access the organisation's reservations.

Permissions and API

Reserving or managing an attached number requires permission to edit the bot. Managing detached reservations or rates requires permission to edit the organisation, subject to existing tariff hierarchy rules. The same organisation and bot boundaries apply in the GUI and public API.

Use /api/v1/bots/{id}/managed-number to quote and reserve, /api/v1/managed-numbers/{id} to manage a reservation, and the organisation endpoints for reservation lists and telephone rates. Retain the same idempotency key and quote version when retrying a confirmed reservation. OpenAPI documents request fields, permissions and examples.

Resellers also have a Default rates for new customers grid. These prices are copied when a customer is created; existing customers retain their own prices. The API exposes this grid as child_defaults. Conversation billing_details exposes the AI and telephone charges for each outgoing leg.

RTP test mode cannot reserve or use a BeAI number. Disable it before confirming a reservation.

Telephony setup and platform assignments

Before creating a bot, choose BeAI number for zero setup with the annual organisation price displayed, or SIP connection with your own account, server and credentials. The Telephony menu shows either the managed number workflow or the two SIP methods (provisioning and manual setup). Switching modes requires saving; reserving a paid number still requires separate confirmation after creation. SIP server, authentication, codecs and registration settings are hidden for managed numbers.

Platform administrators can see each number's organisation, assigned bot, expiry and renewal in BeAI numbers. They can unlink, reassign within the same organisation without a second annual charge, and manage renewal. Unlinking retains the paid reservation until expiry and disables renewal. Assigning a free number requires confirmation of the destination bot's annual price and telephone surcharges; funds are held until routing is confirmed. Concurrent assignment of the same number is rejected.

API parity: GET /api/v1/organisations/{id}/managed-number-offer previews the price before creation. Use sip.configuration_mode: managed_beai to create a bot without SIP credentials; this never reserves a number. Platform inventory and candidates are available at /api/v1/platform/managed-sip/numbers and /api/v1/platform/managed-sip/assignment-bots. POST /api/v1/platform/managed-sip/numbers/{id}/assignment accepts bot_id:null to unlink, or a bot ID to reassign. A free number additionally requires confirmed:true, quote_version and idempotency_key, returning 202 while routing is pending.

New provider orders use Beone, Rue de Trazegnies 218, 6180 Courcelles, Belgium, with geographic postal code 6180. Existing stock numbers can retain their original order's city.

In the bot list, a small green telephone identifies BeAI number mode instead of the SIP status dot. Its tooltip distinguishes an assigned number from a pending reservation. Green identifies the telephony mode; the reservation page shows its activation state.

Available pool numbers still require the platform administrator to enable new reservations after provider verification. Use Enable new reservations in the number administration or PATCH /api/v1/platform/managed-sip with enabled:true. Refresh the bot's reservation page afterwards to see the confirmation button. Price consent and sufficient wallet credit remain required.

Manage BeAI number opens a compact dialog inside the bot form, with price, credit, consent and reservation status. Actions refresh the dialog without reloading the form or discarding unsaved changes. Rates open in a new tab. Save an organisation change before opening number management so the correct price and wallet apply. Paid-number reuse appears only when an eligible reservation exists.

Excluding a number from the BeAI pool

In platform administration, Retirer du pool excludes a number with no current reservation. Excluded numbers appear in a collapsed history section, cannot be assigned manually or automatically, and stay excluded after Sophia synchronization. This does not cancel the supplier number or remove billing history. An ongoing supplier operation temporarily prevents the change.

Platform administrators can re-include a number, then synchronize the pool. A fresh supplier confirmation is required before allocation. The equivalent public API is PATCH /api/v1/platform/managed-sip/numbers/{id}/pool with {"excluded":true,"reason":"Supplier cancellation requested"} or {"excluded":false}. Inventory responses retain excluded entries with pool_excluded:true, pool_exclusion_reason, and eligible:false.

For outbound calls and transfers, see Choose your outbound caller ID.