Picapp Enreach and partner rates
Configure and retain partner rates, synchronise companies, and archive legacy Enreach subscriptions.
The BeAI Picapp is an AI receptionist for businesses equipped with a compatible Enreach platform.
Simple configuration from Enreach
The Enreach Solution displays AI receptionist instructions, Welcome message, Language, and Voice, as well as immediate or delayed pickup, delay in seconds, and immediate handling in Do Not Disturb mode. Both texts are grouped in the Welcome and instructions tab. Languages and voices are displayed with their human-readable names. The Listen to voices link opens a public BeAI page of pre-recorded samples, without login, without customer data, and without billed generation.
The receptionist uses the standard voice configuration, required by BeAI. The model cannot be overridden from Enreach, the BeAI editor, the API, or a restore. Triggering rules are also configured in the Enreach General tab; action permissions continue to be administered in BeAI. This simplification does not change pricing.
When creating a Solution, the default scenario greets the caller, identifies their request, collects their contact details, and confirms the message. It promises no pricing, turnaround time, or unconfigured action. The Solution presents generic text without variables to enter. When the bot is created, BeAI generates the default text using the company name known in Enreach. The subscription directly displays the text actually applied to the bot. If the name is not yet available, the greeting says "our company"; synchronisation then updates the default text. Custom texts are preserved.
Instructions grant no additional permissions: authorised destinations, active skills, and human approvals continue to apply. For sensitive or out-of-scope requests, set a human takeover and an explicit fallback, then check the outcome in the actions and call summary. The form is neither a deterministic workflow editor nor a progressive autonomy mode.
Properties locked or hidden by the Solution remain so in BeAI and in the API. Instructions are stored in Additional info, editable in Markdown. BeAI declares instructions and greeting messages for Solutions and subscriptions, as well as instructions for email and transfer destinations, in Enreach multiline format (textArea). On a compatible myTelephony version, these fields appear in a three-line text box and preserve line breaks. Addresses, extensions, and choice lists retain their usual presentation. If your platform has not yet received this update, use the BeAI editor for long texts. Limits remain 20 000 characters for the greeting and instructions, and 300 characters for each destination instruction.
API and compatibility
The multiline format only affects the presentation of configuration schemas transmitted to Enreach. It changes neither the public API parameters nor their permissions; BeAI forms and the API retain the same texts and line breaks.
GET /api/v1/integrations/enreach/voices returns voices compatible with value, label, and sample_url. The equivalent public catalogue is /picapp/enreach/voices (French and English samples).
BeAI operations remain PATCH /api/v1/integrations/enreach/solutions/{id} for inherited values and PATCH /api/v1/integrations/enreach/subscriptions/{id} for overrides. Their keys remain flat (instructions, greeting, language, voice, routing_policy, delay_seconds, immediate_on_dnd). The ai_model field is fixed and hidden. Example override:
{"revision": 2, "overrides": {"voice": "Puck", "instructions": "# Mission\nAccueille les appels de notre société et recueille un message."}}
The Enreach technical adapter groups texts under reception to display the tab. On subscriptions, the emails and transfers groups project the bot's skills over five lines; they are not inherited from the Solution. It still accepts legacy flat keys for these settings, rejects ambiguous duplicates, and retains omitted overrides during a partial PUT. An explicitly empty configuration object resets common overrides without clearing skills or their destinations. The model field is no longer accepted by this transport; trigger settings use the same keys and validations as the public API. The public API continues to replace all overrides when an overrides object is provided; an empty object resets them.
The Persona field has been removed for all bots. Its existing text is preserved at the beginning of Additional info, in the format Tempérament à adopter : calme, chaleureux, concis, before any information already present. You can edit this Markdown text freely. Legacy snapshots remain restorable; the legacy API parameter temperament, deprecated and write-only, is converted to text in extra_infos. There is no longer any separate persona processing in the execution prompt.
Availability
Setting up platforms, Solutions, subscriptions and pricing is available under Administration → Picapp Enreach. Automatic provisioning follows the Enreach contracts provided for EUP 3.0. The voice journey is delivered for a controlled pilot: call decisions, credit reservation and SIP runtime. The Enreach directory and transfer requests are available for this pilot, with separate permissions. Human consultation via popup with options is available when the platform advertises the compatible feature. SSO is provided to validate launch on each platform; transcript publishing is available for validation on compatible platforms. A platform authorised for provisioning does not automatically activate calls.
The Picapp targets compatible user extensions across all partner Enreach platforms. Each company becomes a child organisation of Beone, even when its carrier is not Beone. It shares a wallet across its extensions; each subscription has its own bot.
Prepare a partner platform
This configuration is restricted to platform administrators and administrators of the Beone organisation. Customer organisation administrators do not have access to it.
- Select the default Beone template for new Solutions and save the general configuration.
- Add a platform with a stable BeAI identifier, its name and the HTTPS destination of its API. The URL subsequently announced by Enreach must match this approved destination.
- Define a distinct installation key for this platform. Share it with its administrator via your usual channel for transmitting secrets. BeAI does not allow reading the key back; replacing it revokes previous tokens.
- If necessary, configure its negotiated pricing, then authorise provisioning for the platform.
- The Enreach administrator installs the Picapp. The connection created is reused by its Solutions and companies.
The identifier returned upon this registration is that of the BeAI connection. The label transmitted by Enreach does not allow selecting another platform's pricing.
If Enreach displays Invalid Picapp authentication when opening the form, the token exchange with BeAI was rejected. The connection accepts the Bearer and bearer variants of the authentication scheme; the token must remain valid and unchanged. If the issue persists after renewal, have the Enreach administrator check the connection. After losing a renewal response, they can re-register the connection using the existing installation key. Do not replace this key to fix a simple capitalisation discrepancy.
Support can distinguish an expired token from a rejected renewal using technical logs, without requesting tokens or displaying them in the interface. Periodic metadata checks also verify authentication: an expired token returns a 401 error so that Enreach requests its renewal. Direct access to the technical URL in a browser without credentials is therefore denied. A title retained in the catalogue cache does not guarantee that the connection used by the form is still valid.
An Enreach administrator with the reconnect permission can restore this connection using the existing installation key, then reopen the form. This reconnection replaces session tokens and retains the platform ID, key, pricing, Solutions, subscriptions and activation permissions. It does not reactivate a suspended platform.
Automatic renewal accepts concurrent requests from servers on the same platform within a 30-second window. This window does not extend a revoked session. If Enreach confirms the reconnection but the form remains rejected, have both sides of the connection verified, as well as the application of the new tokens. A successful reconnection response is not sufficient to confirm their use by subsequent requests; avoid repeating the reconnection without this diagnosis.
For this diagnosis, provide the test time and the X-BeAI-Request-Id ID from the technical response, if Enreach can retrieve it. This identifier allows finding the status and format of the BeAI response without sharing keys or tokens. On its own, it does not prove that Enreach saved the response.
Define pricing
The Default rates for new organisations section initially reflects the prices planned for new children of Beone: voice models, features, sessions, text consumption and SMS per country. No additional commercial charges are introduced by the Picapp.
Platform pricing and new customer defaults use a single voice price. Existing rate cards are carried over without recalculating historical records. Viewing the page does not modify any data; a missing rate remains unavailable without an implicit price.
In a platform's configuration, open Negotiated rates for this platform using Expand. The section is already open when a specific rate card is saved or when an error requires your attention. The Default rates for new organisations banner on the main page also lets you expand or collapse its rate card.
A platform uses this general rate card as long as Use general Picapp rates remains ticked. Untick this option in its configuration to save a negotiated rate card. Missing categories are completed before saving; a country code allows you to add a specific SMS rate.
Upon a company's first subscription, BeAI copies the effective rate card into the pricing of its new organisation and preserves the source and revision used. Subsequent changes never modify prices for organisations that have already been created, including when adding a new extension, reactivating or resynchronising.
Units and precision remain those of BeAI billing: two decimal places for minutes and session fees, six for text and SMS consumption. Negative or invalid values are rejected before rounding. Prices cannot fall below the parent floor price.
If an increase in parent pricing invalidates a rate card, BeAI displays the issue and blocks the creation of companies that would use this rate card. Correct it explicitly. Prices are never increased silently. A revision error means that another administrator has modified the configuration: reload the page before trying again.
Solutions and extensions
A new Solution is automatically activated if its platform is authorised in BeAI. It also inherits voice and action permissions from this platform: no second manual activation is required. A deactivated platform remains blocked. Existing Solutions are not reactivated automatically; a suspension or restriction decided in BeAI is preserved during reads, resynchronisations and replayed creations. Creation maintains zero credits: a top-up remains required for calls.
Subscriptions display the Emails and Transfers tabs to configure the bot's skills, including recipients for systematic summaries and the optional audio attachment. Email and Transfer features are enabled by default upon creation, with no actual destination and no systematic summary. Existing subscription choices are preserved. Unticking a feature hides its settings without deleting them. Empty lists display placeholder examples, which are never used as actionable destinations. Solutions do not share recipients or extensions between companies. See the destination configuration guide for the five rows of the native form, permissions and limits.
A Solution retains a versioned copy of the selected Beone template. Its configuration distinguishes between inherited values, locked properties and hidden properties. An extension can only customise permitted values. When a property becomes locked, any existing override is removed and the Solution's value applies.
Configured settings include instructions, greeting, language, voice and triggering after 20 seconds, immediately in Do Not Disturb mode. They are applied by the voice journey when the pilot is authorised and a compatible runtime is available.
Company and subscription identifiers are isolated per platform. BeAI does not match two companies by their name, number or email address. If Enreach does not provide a company name, its domain serves as a provisional label.
To edit an extension's settings from Enreach, open its Picapp subscription, adjust the permitted values and save. A configuration update automatically preserves the original company and extension, even if Enreach does not return their identifiers or forwards them as null. Any attempt to reassign to another company or extension is rejected with the message A subscription cannot change company or extension (picapp_409); create a separate subscription for that other target. The saved settings are then visible in Enreach and in BeAI.
From the subscription, Suspend blocks its use, Reactivate returns it to its active cycle and Resynchronise recalculates its configuration. Uninstall and archive preserves its organisation, wallet and history. Replaying a creation after uninstallation is rejected: use an explicit reactivation in BeAI, or a new Enreach subscription ID. Archiving a Solution blocks new subscriptions. Picapp bots and conversations bear this source; the API exposes origin, as well as voice_connection_mode on bots. Picapp bots are flagged accordingly. You can edit their instructions, voice and skills in BeAI in line with your standard permissions. SIP transport and locked properties remain protected, including during restores and updates via API or administration wizard. See Customise a Picapp bot.
Credit and visible statuses
A new organisation starts with zero credit and the status Awaiting top-up (awaiting_credit). No AI calls are admitted with a zero balance. Top-ups use the existing BeAI wallet. The bot configuration SSO does not grant access to the wallet; topping up uses your standard BeAI access.
The other statuses distinguish between a suspension, an uninstallation, an archived organisation, a deactivated platform/Solution and waiting for prerequisites (awaiting_contracts). The operational status remains false until delivery and validation of the end-to-end journey.
Voice pilot and call decisions
In the platform configuration, tick Allow voice admissions from the pilot. New Solutions inherit this permission if the platform is active. In an existing Solution, check this box as well. Both levels are checked for every admission. The technical team must have prepared a compatible SIP runtime and its connectivity. Inbound calls from user extensions are supported; outbound calls, hunt groups and ACDs are declined.
From a subscription, open Call decisions and wallet. There you can view the balance, the amount reserved by calls and the remaining available credit. The Test admission criteria button verifies the configuration and lets you compare normal routing with Do Not Disturb mode, without placing a call or reserving credit.
Each valid callback appears with its status and reason: awaiting top-up, credit already reserved, pilot deactivated, runtime unavailable or out-of-scope call. Retransmissions of the same call retain the same admission. A modified context with the same identifiers is rejected. Admission references and temporary tokens are never displayed on this screen or in the public API.
The minimum credit is reserved atomically in the shared wallet. If no SIP call arrives before expiry, it becomes available again. The runtime loads the bot using its internal identifier; no individual SIP accounts are created. A dialogue cannot use another dialogue's reservation. Charges are calculated only once at the end of the conversation; without SIP confirmation and without the AI starting, no charge is made.
To stop the pilot, untick its permission on the platform or Solution, or suspend a subscription. New admissions are blocked; calls already in progress can finish and their billing is preserved. Top-ups remain accessible with your standard BeAI account. Transfers require validation on a real extension before being made available to users.
Directory and in-call actions
In the platform, enable Authorise pilot Enreach actions. A new Solution then inherits the permissions Internal directory, Enreach transfer and Popup consultation with choice, provided the platform is active. These permissions can still be modified separately in BeAI by Beone or platform administrators. Bot skills, configured destinations and call permissions remain mandatory. Parameters sent by Enreach cannot modify them. An internal transfer requires the directory; a configured and validated external number can be transferred without directory permission.
The receptionist can then look up a colleague and check their availability. A search returns at most 20 internal users or groups accessible to that call's Enreach user. Private, hidden and locked contacts are excluded. For a user, unknown availability does not allow a transfer; groups and ACD groups require their own current presence, without inventing an individual telephony status. Compatible voice services do not require human presence. Before each request, BeAI refreshes the contact, checks the plan permissions and uses the Enreach transfer operation, independently of the model's tool catalogue. The transfer uses Enreach, without unconfigured destinations or SIP REFER commands. Configured external numbers must be valid landlines/mobiles in international + format, subject to the same premium-rate protection policy as other connections. They do not trigger a directory search or presence check; their availability is unknown and carrier fees or restrictions may apply.
An announcement such as "I'm putting you through" prepares the transfer; it does not prove it has been sent. BeAI waits for the announcement to be genuinely played and then checks the destination. If the contact is unavailable, the receptionist explains this and offers to take a message. If verification fails or remains uncertain, it states that the connection could not be confirmed, without inventing a reason. It stays on the line to take the message and does not hang up to execute the transfer. The summary distinguishes between a request accepted by Enreach and a confirmed answer.
To intervene from BeAI, open Call decisions and wallet, then click the call identifier. The Enreach actions page offers search, contact refresh, transfer request and the log. These commands require an established SIP call and the same administrative permissions as the configuration. The history remains viewable after the call, with 25 actions per page; a call is limited to 200 actions.
Request accepted means that Enreach accepted the request, without confirming that the colleague answered. Uncertain outcome means that no actionable response was received. A pending, accepted or uncertain telephony request blocks any further telephony request on that call. The receptionist must neither automatically repeat the request nor announce an unconfirmed connection; it can offer to take a message. An explicit rejection remains distinct from an unknown outcome.
In the conversation technical details, preparation appears as prepared, then acceptance as request accepted, instead of a failure. The console, live sessions and the API show the same statuses, including for historical conversations. The i button preserves the result received: ok: false here means that the action is not yet confirmed, even when its preparation or acceptance succeeded. Errors and rejections remain reported as failures.
Consultation is offered if Enreach advertises a compatible function. Human waiting time after sending is 60 seconds, with a short transport allowance. The pop-up is sent to the colleague on the subscription, never to the caller. A recognised choice or an explicitly confirmed open response can be acted upon; an ambiguous numeric response remains uncertain. Without a transfer, a shared note is automatically published at the end of the call containing the BeAI summary, questions, proposed choices, and confirmed responses. During a transfer, the receptionist provides a brief factual summary: BeAI publishes it alongside already recorded consultations before transferring the call, so that the recipient has the full context. If the note is not confirmed, the transfer remains blocked and the receptionist offers the scheduled fallback. An uncertain publication is never automatically retried. Ending the dialogue following this transfer does not generate a second identical note; if the conversation continues, its updated review is retained. Notes and actions remain visible as system events in the GUI/API history and statistics. Temporary identifiers are kept encrypted for up to five minutes to finalise the review, then deleted. BeAI forwards speech to Enreach when the platform supports live transcriptions; BeAI conversations continue to be recorded normally.
Useful directory results and execution states are stored in an encrypted log. Callback tokens remain segregated, are transmitted neither to the model nor to the browser, and are cleared upon call release or completion.
Automating via the BeAI API
The same permissions, validations, and services apply to both the portal and /api/v1/integrations/enreach:
| Operation | Resource |
|---|---|
| Read or edit general settings | GET/PATCH /settings |
| List, create, read, or edit a platform | GET/POST /platforms, GET/PATCH /platforms/{id} |
| List, create, read, or edit a Solution | GET/POST /solutions, GET/PATCH /solutions/{id} |
| List, prepare, read, or edit a subscription | GET/POST /subscriptions, GET/PATCH /subscriptions/{id} |
| View decisions and available wallet balance | GET /subscriptions/{id}/calls?page=1 |
| View the log or execute an action on a call | GET/POST /subscriptions/{id}/calls/{callId}/actions |
| Test criteria without affecting the wallet | POST /subscriptions/{id}/decision-preview with {"callee_in_dnd": false} |
| Suspend, resume, archive, or resynchronise | `POST /subscriptions/{id}/{suspend |
Global pricing updates use revision and default_organisation_billing_rates. A platform tariff uses billing_revision and the same pricing field; null restores general inheritance. Subscription actions require its revision. Lists accept page and limit (maximum 100). Formats, responses, and examples are detailed in the public API.
Istra callbacks constitute a separate technical transport, authenticated per connection. They provide no access to commercial tariffs and cannot replace them. Token exchanges are not operations accessible with a personal BeAI API key.
Voice authorisations use voice_enabled on platforms and Solutions, with identical permissions in both interfaces. The decisions list is paginated by 25. The /internal/api/picapp/* endpoints serve exclusively at runtime (claim, antispam, SIP confirmation, balance, and release): they are technical exceptions to GUI parity, with no access for a personal BeAI key.
Actions use actions_enabled on the platform and action_policy on the Solution (directory, transfer, consult, booleans), along with its revision. Example search via POST /subscriptions/{id}/calls/{callId}/actions:
{"request_id":"search-001","name":"directory_search","arguments":{"query":"Claire"}}
To refresh presence, use directory_contact with {"extension":"201"}; legacy contact_id remains accepted instead. To transfer, use transfer with {"extension":"204"} or an external number configured as {"extension":"+32475123456"}. contact_id remains reserved for internal contacts. Capabilities separate allowed_transfer_extensions and allowed_external_transfer_numbers. An external party requires permission transfer, not directory; an internal party retains both checks. The context field contains the summary intended for the recipient, for example {"extension":"204","context":"Le client souhaite joindre la garde pour une panne."}. It remains optional in the GUI and API for compatibility: without this text, BeAI reuses the summary or speech already recorded. The shared note is published and confirmed prior to transfer. call_note and call_note_confirmed indicate its delivery; transfer_note_unconfirmed with transfer_sent=false means that the transfer was not sent. An uncertain publication must not be re-attempted. The server resolves the extension, verifies authorised destinations, and checks the current presence of users, groups, and ACD groups; voice services do not require human presence. Consultation uses consult with {"question":"Comment traiter cette urgence ?","options":["Transférer au support","Prendre un message"]}. answer contains the confirmed response and answer_kind distinguishes choice and text; selected_option is retained for a recognised choice. Choice presentation conversions are handled by BeAI, and collisions are rejected before sending. Retain the same request_id upon retransmission: no new dispatch. Different content under the same identifier triggers a 409. States executing, confirmed, accepted, refused, and uncertain remain distinct; retry_allowed:false prevents automatic replay. The log can be reviewed with GET after the call. result_unavailable:true flags an unreadable encrypted detail without removing deduplication protection.
AskAgent diagnostics and authorised destinations
Solution authorisations do not replace bot skills. A transfer requires Enreach Picapp, Transfer, and an exact destination present in the Transfer destinations: an internal extension from the directory or a positively validated fixed/mobile international external number. Descriptions and conditions for these destinations are provided to the bot; the server checks activation and the exact destination before transferring. No contact or presence status is invented for an external party. Internal extensions and contacts retain their directory permissions and presence checks. An invalid, special, premium-rate, non-geographic, unknown external number, or one formatted as a SIP URI, is rejected; carrier charges continue to apply. Consultation scenarios are configured in the bot's Picapp skill.
In call actions, consultation_discovery_failed means that reading Enreach functions failed; upstream_code specifies, for instance, http_403 or transport_error. consultation_not_announced indicates that AskAgent is not declared in a recognised list, and consultation_schema_unsupported that an AskAgent declaration was recognised but remains incompatible. consultation_arguments_rejected means that the choices or question do not comply with the announced schema. For these four rejections, request_sent:false and popup_sent:false confirm that no pop-up was requested.
BeAI recognises both direct and nested Istra function declarations. Choices remain a list of two to six labels in BeAI. The transport accepts an array or a string depending on the type advertised by Istra. On the pilot, strings are split into choices on commas: BeAI therefore sends labels separated by commas, without adding JSON brackets or quotation marks. In this format, a label containing a comma or leading/trailing spaces is rejected prior to sending and must be rephrased. Platforms accepting an array keep labels as is. Display and choice return must be validated on the live platform. Function constraints are always checked before sending; any unknown additional mandatory field is rejected. ask_agent_declared:true confirms function recognition, not the pop-up dispatch. Blocked browser notifications do not account for a pre-dispatch rejection; check the action result first, then reception in myIstra.
Following a submission attempt, popup_sent:null means that delivery and response are not confirmed. Only human_choice_received with selected_option confirms a choice. Do not retry an action whose outcome remains uncertain. The same result is available in the conversation and in the public call-action resources; no temporary tokens are exposed.
myCRM callbacks use the registered platform domain and the /restletrouter/v1/crm routes indicated in the integration guide. The /apis prefix of the Swagger interface does not define the platform entry point. There is no automatic retry on a second route following a telephone action.
If the format of a consultation response is not recognized, BeAI preserves an encrypted structural trace: field types and any match to a choice number, without copying free-form text, labels, or tokens. This trace is reserved for technical diagnostics and excluded from prompts, the public API, and exports.
If a function is not recognized, BeAI preserves an encrypted structural fingerprint of its declaration to allow support to analyse the format after hang-up. Descriptions, default values, and tokens are not preserved in this diagnostic record, and this technical trace is not forwarded to the bot. An unknown function remains rejected until its compatibility is established.
Bot configuration via Enreach SSO
In the platform connection, enable Allow bot configuration via Enreach SSO after validating the pilot. The same setting is available via PATCH /api/v1/integrations/enreach/platforms/{id} with {"web_sso_enabled":true} and returned by GET. Authorized Beone administrators and platform administrators use the same controls. The option is disabled by default. Disabling it blocks new launches as well as existing sessions.
The Configure BeAI receptionist link is presented to Enreach users and administrators. Users access their subscription; administrators must hold permission to access Picapp administration interfaces along with standard write permissions on the relevant domain. Read-only administrators or those with unvalidated custom permission profiles are rejected. Federated accounts are never matched with a BeAI account by email address and receive no local password.
The updated Enreach documentation now provides for REST interface updates when a Picapp version changes, occurring at the platform's next health check. PIC events remain frozen for existing Solutions: modifying these events may still require recreation, which should be prepared outside of an active call while preserving settings. Check the behaviour of the deployed Enreach version before recreating a Solution.
In the form for an existing subscription, the Edit the receptionist in BeAI link opens its bot directly under the Enreach administrator session. In that of an existing Solution, a single bot opens directly; if multiple bots are authorized for that Solution, a selection is offered. This workflow requires an Enreach version supporting configuration SSO links; creating a Solution does not offer this link. BeAI consumes a single-use code, valid for 60 seconds, then validates the session and its domain with Enreach. The code and tokens never become permanent login links.
If Enreach opens the link without forwarding the session, BeAI displays Enreach did not forward your login. Simply reopening the same link is not enough: the platform must support SSO launch for this link. A still-valid BeAI SSO session may be reused for this same bot, following a fresh verification against Enreach; it does not allow switching bots or companies.
The Enreach platform can query a shared schema, then complete its link with the platform, Solution, and subscription identifiers. BeAI checks their consistency and subscription ownership before any code exchange. The identifiers do not constitute authentication. A missing, incorrect, or suspended context blocks launch; no bot is inferred from the name, extension, or subscription count. An older Enreach version may require an operator update.
Validate launching, saving a change, and rejection after logging out of Enreach before opening access to clients. A visible link without a forwarded session does not constitute working SSO. Refer to the bot customization workflow for limits and error messages.
The SSO editor also grants access to the configuration wizard for the selected bot only, using the same /api/v1/bots/{id}/setup-assistant operations. Writes using this cookie require X-CSRF-Token, obtained via GET /enreach/sso/session, including to start, upload or remove a document, and confirm. Creating bots, global logs, accounts, and billing remain excluded. Solution restrictions are preserved: an interview does not overwrite a locked value and is not opened if any of its settings are hidden.
The displayed branding is that of the first parent of the bot's organisation with defined branding when traversing up the hierarchy. It applies to both the manual form and the guided setup conversation, without altering the active organisation, parent links, or permissions. The public domain used for SSO does not override this branding.
Company names and automatic archiving
An organisation's name follows the format Platform — Company (reference), for example Enreach UP — BeAI-Pilote (0.6.10.0). The platform name comes from its BeAI configuration; a platform named Becloud yields names starting with Becloud. The identity remains bound to the platform and Enreach domain, even if names change.
In Administration > Picapp Enreach > Platform, open Organisation and subscription synchronisation. An authorized Beone administrator or platform administrator can enable the connection and provide the Enreach administrator account and its full domain. This account must hold the standard permissions for its type and have visibility over all relevant companies, Solutions, and subscriptions. BeAI uses it solely to read inventory. The password is encrypted, never returned, and can be kept unchanged by leaving its field blank. Disabling the connection clears the stored credentials.
Synchronization is scheduled every five minutes. Synchronise now triggers the same read immediately. The Enreach company name is updated upon each successful run; modifying the platform name immediately updates already linked organisations. Prior to the first successful read, the name temporarily uses “Company” with the platform name and reference.
A subscription deletion received from Enreach archives its bot. Deleting a Solution also archives all of its subscriptions. If a notification is missed, two matching complete inventories, spaced at least five minutes apart, detect vanished subscriptions or Solutions. A connection error, incomplete inventory, or insufficient scope never triggers an archival by absence. The status and last success are displayed in this section; resolve any connection issue and rerun synchronization if it is unavailable. Inventories exceeding 2 000 items per category require an update to the connector.
When no active subscriptions remain for a company, its organisation is archived automatically. A simple suspension keeps the organisation active. Former bots drop out of the active bot list, but their conversations, wallet, and pricing are preserved. A new subscription for the same company reuses and reactivates its automatically archived organisation, retaining the same balance and pricing; a manual archival remains blocking.
Equivalent operations are PATCH /api/v1/integrations/enreach/platforms/{id} with inventory_connection, followed by POST /api/v1/integrations/enreach/platforms/{id}/synchronise. Platform GET endpoints expose the status without secrets; subscriptions expose enterprise_name, organisation_name, organisation_archived, and bot_archived. Enreach callbacks remain technically separate, authenticated transports; their actions use the same archiving service.
Enreach administrative hierarchy
When a subscription is created, BeAI prepares the entire domain chain ahead of the bot: Beone → Enreach platform → provider domains → company. For example: Beone → Enreach UP (0.) → Presales_Service_Provider (0.6.) → SP_BEONE (0.6.10.) → BeAI-Pilote (0.6.10.0.). References are isolated per platform; two operators with the same references share no organisations.
In the Picapp connection, open View hierarchy and identities. The page displays references, parents, BeAI organisations, confirmed or provisional names, Reseller status, and discovered administrators. Synchronise now uses the existing inventory connection. The same view is available via GET /api/v1/integrations/enreach/platforms/{id}/hierarchy, with the same Beone or platform administrator permissions. Refreshing uses the existing POST /api/v1/integrations/enreach/platforms/{id}/synchronise, with no request body required.
Parent names are retrieved from the administrative myTelephony resources observed on the EUP pilot 3.0. Reading them must be validated for each platform: Picapp callback contracts do not transmit this complete chain. If it is unavailable, BeAI preserves already confirmed names and creates new levels under a provisional name with their reference. Calls never wait for remote hierarchy reads. A company move or inconsistent parent is rejected and requires explicit reconciliation.
The platform and intermediate tiers automatically have Reseller status. A BeAI administrator assigned to one of these tiers can view and manage their descendant organisations and their bots from Administration → Organisations, the organisation selector, and operations /api/v1/organisations and /api/v1/bots. Standard roles and restrictions continue to apply: no access to sibling branches, parent entities, or other platforms is granted. The Picapp view and the /hierarchy response expose the same reseller status. Enterprise organisations do not automatically become resellers.
These parents remain administrative tiers, with no dedicated bot or call wallet. They do not alter the BeAI vendor, platform-negotiated rates, or enterprise top-ups. They do not consume client organisation quotas. Their assignment and names are managed by Enreach and cannot be modified in organisation forms. Existing enterprises are assigned in place: their BeAI identifiers, bots, conversations, credit, and rates are preserved. Archiving an enterprise does not delete its shared parents.
When the inventory account allows read access, administrator identifiers, usernames, and email addresses are staged by domain. A staged identity does not create an active account, send an invitation, or grant any access: access remains subject to validated SSO or authorised manual creation. No email matching is performed. Out of scope or Read not confirmed does not mean that no administrator exists. Blocked Enreach accounts are flagged.
A known Solution outside the scope of the inventory account prevents confirmation of disappearances (scope_mismatch). The names and identities of the hierarchy actually read can still be updated; this check never turns a lack of permissions into proof of deletion. To inventory all Solutions across the platform, use an administrative account covering their domains.
Legacy opaque enterprise identifiers entered via API remain compatible with their historical assignment. New native subscriptions use Enreach domain references.
Simplified tools and initial context
The voice model receives four tools: search_directory(query), check_contact_presence(extension), transfer_call(extension, context), and ask_colleague(question, options). BeAI handles Enreach credentials, feature discovery, and their formats. This discovery is cached for up to 60 seconds, exclusively for the same call and its matching encrypted credentials.
Before an internal transfer, the bot first checks the contact's presence using check_contact_presence. If available, it announces the connection once and then calls transfer_call. If busy or unavailable, it states so and suggests the designated fallback, such as taking a message. Unknown presence or a denied read means availability cannot be confirmed: the bot does not present the person as absent and does not attempt the transfer. Verified voice services and external numbers follow their own rules.
BeAI checks the destination and its presence again at the time of transfer, as the status may change between the two tools. In screens and /api/v1, reading presence uses action directory_contact; the transfer uses transfer. The same permissions and checks apply. A contact_presence_unknown denial is distinct from contact_not_available: no transfer is sent in either case.
The compact projection intended solely for AI transport is a technical parity exception: screens and /api/v1 retain detailed results and use the same service, validations, and permissions. Legacy settings and history remain compatible. For example, the AI receives {"status":"available"}, {"status":"accepted"}, or {"status":"answered","answer":"Disponible dans dix minutes."}. An accepted request never confirms that the call has been answered; an inconclusive result does not trigger an automatic redirection.
The initial context contains only callback data and destinations already configured on the bot: enterprise, caller, recipient, DND at call start, permissions, names, types, instructions, and local time. It neither loads the full directory nor past presence states, and does not add any remote calls to the admission callback. Legacy standard technical prompts are updated; customisations are preserved.
Transcript tracking and link revocation
The call log indicates transcript.state, code, delivered_at, link_status, and link_expires_at. The same data is available via GET /api/v1/integrations/enreach/subscriptions/{id}/calls. The Revoke link button uses the same permission checks as POST /api/v1/integrations/enreach/subscriptions/{id}/calls/{callId}/transcript-link/revoke (no body required). Revocation is immediate, idempotent, and does not delete history. The token is never returned in this list or in action logs.
Example result: {"data":{"state":"confirmed","code":"transcript_updated","delivered_at":"2026-09-16T12:00:00+00:00","link_status":"revoked","link_expires_at":"2026-09-23T12:01:00+00:00"}}.
Parity exception: automatic myCRM submissions and limited link reading are technical transports. They do not grant any additional permissions to the BeAI user. The public page and its JSON request use the same projection, limited to the summary and transcripts of the authorised conversation.
The inventory may include Solutions inherited from an Enreach parent domain: BeAI ignores them and only manages the configured domain. Any response containing data from a neighbouring domain remains rejected, without automatic archiving.
The transfer directory remains restricted to the bot's enterprise, even when the Enreach connection uses an administrator from the parent provider. If the message Choose an extension from this company's Enreach catalogue. Refresh the directory if necessary. appears, refresh the directory in the transfer skill, then select a destination within this enterprise. Extensions from another enterprise remain rejected. Refreshing does not modify already saved destinations; external numbers retain the same checks against special or premium-rate destinations.
Browse lists and histories
Platforms, Solutions, and subscriptions share a neutral list interface. Each category retains its creation, configuration, and pagination settings. Call, validation, and synchronisation logs remain monitoring views: new search or export menus are not added to these tables.
Statuses, reasons, rates, and amounts remain visible in their workflow. Viewing these lists does not synchronise the provider, stage a subscription, or place any calls. These operations always require explicit commands and existing permissions.