Skip to main content
Belcenter AIHelp center
Administer the platform

Pricing and future customers

Set voice, text, and SMS defaults in the organisation, with supplier minimums and without affecting existing customers.

Each organisation has a single voice rate in EUR/min excl. VAT, regardless of the technical engine. Rates already applied to the standard engine are preserved during this simplification. Past conversations, wallet debits, and provider costs are not recalculated.

Recording and automatic enhancement options, telephony, SMS, written messages, and BeAI numbers retain their own rates. Subscriptions retain their included minutes and contractually defined overage charges.

Manage organisation rates

A platform administrator or authorised provider can modify the voice rate for an organisation within their scope. Resellers can view their provider rate, but cannot modify their own rate, that of a sibling, or that of a grandchild organisation.

The price must be strictly positive. A missing rate means new calls are unavailable. It is never replaced with zero, catalogue pricing, or any other implicit rate. The actual price recorded for the parent is the floor, including for children of the root organisation. The default for future clients is used solely to prepopulate their rate.

For example, with a parent rate of 0,10 €/min and a client default of 0,40 €/min, an authorised administrator can set a client to 0,20 €/min. They cannot drop below 0,10 €/min. This change preserves the default and rates for other clients.

Set rates for future clients

Open your provider organisation under Organisations, then select Edit. The Future client rates section groups defaults within the same form. An authorised reseller can also access this section under My organisation.

The rate card distinguishes between:

  • Voice: an amount per minute, regardless of the technical engine.
  • Call options: recording and automatic enhancement.
  • Written conversations: session opening and processing of text, images, audio or video, cache, and responses. Processing prices are expressed per million tokens.
  • SMS: a price per configured country.
  • Numbers and telephony, under advanced settings: annual rental of BeAI numbers and per-country rates for call connection and duration in minutes. Pre-configured rate pairs remain available.

WhatsApp and Messenger written conversations use the same text rate card. WhatsApp voice calls use voice rates and call options; they do not require a separate rate card configuration.

Expand the required categories, enter the amounts, then use the single Save button at the top of the page or its floating reminder once you have scrolled down the form. Collapsing a category preserves your values. Provider minimums remain enforced upon saving.

This rate card is copied when creating a child organisation if no explicit pricing is provided. Existing clients and subscription terms retain their prices. If the provider price exceeds a saved default, correct this default explicitly; no prices are increased automatically. Defaults do not propagate to grandchildren or to the resale defaults of a child reseller.

The legacy links Initialize the voice rate and Pricing for future clients now open this section. They do not perform any batch initialisation.

Removing pricing

Clearing the voice pricing blocks new calls for the sales branch. Descendants' rates remain saved for subsequent reactivation. Calls already admitted retain their prices and can finish. Billed conversations are not recalculated. Picapp uses the parent commercial organisation, without creating an additional pricing schedule on each technical node.

Public API

Modifying the organisation in the portal corresponds to PATCH /api/v1/organisations/{id}. Its voice pricing is held by billing_rates.voice.minute. Defaults use child_billing_default_rates, with sections voice, features, text, sms, managed_numbers, and telephony. managed_numbers.annual is the annual fee per number; telephony contains keys such as BE.connection (per call) and BE.minute (per minute). Omitted key = keep; null removes a voice or phone pricing schedule; zero or negative value for voice = reject. The same permissions and minimums apply.

{"billing_rates":{"voice":{"minute":0.20}},"child_billing_default_rates":{"voice":{"minute":0.40},"text":{"session":0.10},"sms":{"BE":0.12},"managed_numbers":{"annual":12.00},"telephony":{"BE.connection":0.05,"BE.minute":0.10}}}

Consultation and compatibility operations remain available:

  • GET /api/v1/organisations/{id}/voice-pricing: organisation pricing and availability.
  • POST /api/v1/organisations/{id}/voice-pricing/preview: legacy initialisation preview for direct children, preserved for compatibility and deprecated.
  • POST /api/v1/organisations/{id}/voice-pricing/initialize: legacy batch application with the received revision, preserved for compatibility and deprecated.
  • GET then PUT /api/v1/organisations/{id}/voice-pricing/defaults: voice pricing for future children.

Batch initialisation remains a compatibility API route; it has been removed from the graphical interface. It only populates missing prices for direct children and saves the default. Existing rates remain unchanged. Archived organisations are excluded from the count of children without pricing.

Example of a legacy preview, with an exception for the direct child 42:

{"default_price":0.50,"exceptions":{"42":0.60}}

To apply, send back the same object with "revision":"révision reçue". An outdated revision returns 409. An unauthorised scope returns 403. An invalid price or a price below the minimum is rejected.

For future clients' pricing, send the current revision and the full voice object:

{"revision":"révision reçue","voice":{"minute":0.40}}

The legacy initialisation routes remain aliases of this single pricing schedule. The legacy per-engine rate cards no longer allow creating distinct prices. The amounts above are operational examples, not commercial recommendations.

Purchase estimates

Provider costs are independent of client pricing. They are restricted to platform administrators and hidden by default. From the avatar, enable Purchase estimates to display them temporarily. This setting is stored neither in a cookie nor in the database, and is reset to disabled once the browser is closed.

The conversation breakdown can then display processing steps, their quantities, unit price, and estimates. A partial or missing estimate does not mean zero cost. Different currencies are never implicitly added together. Locked historical prices remain unchanged.

Documentation updated with the application