Monitor guided setup sessions

Administration → Platform → Autoconfigurations gives unlocked platform administrators read-only access to guided bot setup sessions across all organisations. Customer and reseller administrators cannot access this screen; their existing permissions on their own bot's setup remain unchanged.

Search by bot or organisation name, or exact session ID. Filter by bot ID, organisation ID, status, creation dates, or the presence of a pending/failed connection attempt. Date filters include whole UTC days; displayed times use Europe/Brussels. Results are paginated, with up to 100 sessions per page. Resumed connections remain grouped under their original session.

Open a session to review available automatic transcripts, decisions by revision, current draft, completed topics, document names and their intended uses, and accepted or rejected configuration tools. A successful configuration shows its saved version, separately from any spoken agreement in the transcript. Charges shown are finalised customer euro debits and subscription seconds, not provider costs. Sponsored sessions are marked as paid for by Beone. Pending seconds remain provisional.

Use Refresh, or enable automatic updates every ten seconds while the tab is visible. Errors stop automatic updates and preserve the last displayed data, which may be stale. Reading this history never closes a connection, modifies the bot, places a call or settles billing.

An open session can be resumed; an active connection is an unfinished attempt. Interrupted monitoring means no update for over three minutes, not proof that a call remains active. Applied, closed and expired sessions remain readable. Expiring the thirty-day resume window does not delete history. Deleting the bot retains its sessions, with its last known name and organisation.

Existing sessions are included. This feature exposes automatic text transcripts, not audio recordings. Recognition errors and missing final words after an interruption are possible. Older sessions may lack tool timestamps or topic checklists; these are not reconstructed. Up to the latest 500 decisions and 100 tool results per connection are retained. Extracted document text, connection tokens and internal callback parameters are not returned.

Public API

Use a personal API key belonging to an unlocked platform administrator:

GET /api/v1/bot-setup-sessions?bot_id=192&status=open&page=1&limit=25
GET /api/v1/bot-setup-sessions/{sessionId}

Collections return data, pagination meta and normalised filters; detail uses a data envelope. Filters: search, bot_id, organisation_id, status (open, applied, closed, expired), activity (pending, failed), from, to, page, limit. IDs must be positive; dates use YYYY-MM-DD, with the end on or after the start. Invalid filters return 400, insufficient privileges 403, missing sessions 404. Keys follow the owner's current permissions. Responses use no-store; poll no faster than every ten seconds. See the API documentation for the complete schema.

Estimated AI provider cost

After temporarily enabling Purchase estimates from the avatar, the Estimated AI cost column shows voice token costs for each session, including sessions sponsored by Beone. Session and attempt details show input/output tokens, text/audio categories, purchase prices per million tokens and each line cost. Prices use the conversation purchase rate settings and are frozen at the first provider report of each attempt.

These are provider-reported token estimates, not supplier invoices. Input counts include context billed again on later exchanges. The purchase currency is displayed explicitly (for example USD), without automatic EUR conversion. Telephony, storage and document indexing are excluded.

A partial estimate is the known subtotal for an ongoing/interrupted session, missing counters or prices. Tokens unavailable means counters were not retained, including older sessions; a dash never means a zero cost. Different currencies across attempts are shown separately, without adding them together. Customer charges and free-session rules remain unchanged.

With include_purchase_estimates=true, the platform-admin API returns the same provider_cost object on each session and attempt: status (estimated, partial, unavailable), model, currency, nullable total, nullable tokens, reports, items (key, tokens, nullable unit_price and cost) and calculated_at. For example, 1,000 input audio tokens at 3 USD/million plus 500 output audio tokens at 12 USD/million produce a total of 0.009 USD. amount_eur remains the customer debit. Organisation owners and resellers cannot access provider costs.

Deleted bots

Deleting a bot retains its setup sessions, transcripts, decisions, document descriptions and provider costs. Bot supprimé (deleted bot) replaces the link to its settings. The last known bot ID, name and organisation remain searchable. No configuration or document ingestion can resume for a deleted bot. The public API exposes bot.deleted and preserves the original bot.id. Sessions erased before this change require a backup to recover.