Customise a Picapp Enreach bot and SSO access
Configure transfers, consult a colleague, and retrieve transcripts in Enreach with a restricted read link.
Go to Bots, select your Picapp receptionist, and click Edit. Your organisation's standard permissions and tag restrictions also apply to these bots.
Instructions, greeting, voice, and skills
You can customise instructions, additional information, voice, and skills. The Telephony tab remains available for codecs, DTMF sending, RTP test mode, and automatically marking conversations as read. Only SIP connection and registration settings are hidden: the company, extension, and connection are managed by the Enreach subscription. A new extension is created in Enreach; a Picapp bot cannot be duplicated like a SIP account.
Properties locked or hidden by the Solution cannot be overridden in BeAI, via the API, via restore, or via the administration wizard. A resynchronisation preserves skills and additional information added in BeAI. If two changes arrive concurrently, reload the data before retrying.
Picapp bots use standard voice configuration, enforced by BeAI. The Enreach Solution provides instructions, greeting message, language, voice, and call-handling rules. Each subscription also has Emails and Transfers tabs specific to its bot. Instructions and persona are now freely described in Markdown within Additional info. Text from the former Persona field has been preserved at the start of this field. Values locked or hidden by the Solution remain protected. The Listen to voices link opens public samples without signing in.
Configure call handling
In the General tab of the Enreach Solution or subscription, choose Immediately or After a delay without an answer. The delay is adjustable from 1 to 120 seconds (20 by default) and only appears in delayed mode. Answer immediately in Do not disturb mode, enabled by default, prioritises this status reported by Enreach. Subscriptions inherit settings from their Solution, unless overrides are permitted. Visibility and modification restrictions still apply; settings take effect on subsequent calls without altering an ongoing call. The same properties routing_policy, delay_seconds, and immediate_on_dnd can be configured in BeAI and through the Solution/subscription resources in /api/v1/integrations/enreach.
The initial script welcomes callers on behalf of the Enreach company, captures the request, and offers to take a message when an authorized action or required information is missing. Transfer and consult functions remain subject to configured skills and permissions. Business scripts must specify the required human confirmation and fallback.
A directory lookup, availability check or record lookup does not consult a colleague. The receptionist announces the hold once for the same request, then provides the outcome. Human consultation takes place only in the planned scenario. If it is unavailable, the receptionist applies fallback without initiating it again for that request. If the caller agrees to leave a message, the receptionist collects and confirms this message before ending the call.
Configure emails and transfers from Enreach
In the Enreach subscription configuration, open Emails or Transfers. The master toggles are ticked by default for new subscriptions. Existing subscriptions keep their choice. Unticking a toggle hides all settings in its tab and suspends that feature without clearing its destinations or settings; settings reappear when it is ticked again. Systematic summaries remain disabled by default. These tabs modify the same skills and destinations as the BeAI form; they do not create a separate list.
- Emails: one address per line and a short note on its use, for example
support@example.com— "Technical enquiries". A valid address and a description are required for each row used. Enable Emails, then Automatically email the summary after every conversation to automatically send the BeAI report. Specify its recipients, separated by a comma or semicolon; at least one valid address is required. Attach recording attaches it when available, without enabling call recording. These recipients are independent of the numbered addresses used during the conversation. Saving the configuration does not send any emails. The summary is sent once generated, subject to the email service operating properly. - Transfers: the number of an internal extension or an external landline/mobile number in international format
+, and, if useful, the transfer instruction. Example:204— "On-call service, only after colleague's approval". Any new internal extension is checked against this organisation's directory. An external number such as+32475123456is validated by the premium-rate prevention policy, without a directory lookup. If the catalogue is not ready, refresh it in BeAI and try again. Solution permissions and in-call presence checks remain applicable.
Empty lists display examples when their tab is enabled: message@example.invalid to leave a message and XXXX for an urgent transfer, with generic instructions. These values are placeholders, are not saved as destinations, and trigger no action. Replace them with your actual recipients (or clear them). Even with the main toggle enabled, these examples remain excluded from actionable destinations. For automatic summaries alone, simply enter the summary recipients. The subscription agreement and catalogue currently used do not provide a reliable user email address: no personal address is inferred.
The native form displays up to five destinations for each function, in separate blocks. The Add a destination checkbox reveals the next block with its address or extension and instruction. Destinations already saved are opened automatically. Unticking a checkbox hides subsequent blocks without deleting saved destinations; they reappear the next time the form is opened. The current Enreach form cannot condition this display on text input: the checkbox allows controlling it. Clear the address or extension to remove its line. Additional destinations created in BeAI are preserved; manage them in BeAI. Disabling a function retains its destinations for later re-enabling. Modifying one tab does not delete other settings or the bot's skills. A save containing an invalid destination is rejected without partially applying other changes.
These settings are reserved for persons authorised to configure the Enreach subscription or the BeAI bot. SSO accounts remain restricted to their own bot. The configuration schema is shared across the Solution and does not receive the organisation’s identity: the Enreach field therefore prompts for the extension number or the international external number, whereas BeAI provides the selector with names and types.
The equivalent API is GET/PATCH /api/v1/bots/{id}/skills/emails or /skills/transfers. It uses enabled and the complete destinations list, without the five-line limit imposed by the Enreach form. Email example: {"enabled":true,"destinations":[{"email":"support@example.com","description":"Demandes techniques"}]}. Mixed transfer example: {"enabled":true,"destinations":[{"extension":"204","description":"Après accord du collègue"},{"extension":"+32475123456","description":"Astreinte externe"}]}. For summaries: {"enabled":true,"summary_email":{"enabled":true,"recipients":["suivi@example.com"],"attach_recording":false}}. The settings are also accessible in the Emails skill of the BeAI form, with the same permissions and validations. The placeholder examples are an Enreach display aid and are absent from GUI/API destinations. An API PATCH replaces the provided list; omitted fields are retained. The five-line presentation is an adaptation of the Enreach transport only.
Enreach Picapp skill
The Enreach Picapp skill replaces Enreach UP. It is reserved for bots created from a Picapp subscription and requires no username or password. It is enabled upon creation; its activation remains subject to platform and Solution authorisations.
It allows searching accessible internal users, groups, and voice services, checking their presence and telephony status, transferring a call, and passing context to the recipient in a shared call note. An absent presence remains unknown. The presence of groups and ACD groups is interpreted according to their own format, which might not include a telephony status.
Choosing transfer destinations
To transfer, enable Transfer, then choose Add an internal extension or Add an external destination. An internal row uses the Extension list; an external row requires a valid landline/mobile number in explicit international format, for example +32475123456. Both types can be mixed within the same list. When opening the form, BeAI refreshes the internal extensions for this organisation in the background. Refresh directory allows you to trigger this retrieval again. The list offers numerical extensions from 2 to 6 digits supported by the Transfer skill, along with their number, name, and type: user, group, ACD group, or voice service.
For an internal destination, the Enreach name also appears before the Additional context; it cannot be modified in BeAI. This optional context describes when to use the destination, for example "Only after colleague's approval for a blocking urgency". Changing the selection automatically updates the name. Names modified in Enreach are retrieved upon the next refresh. Standard SIP bots keep the free-text extension field and their usual description.
Retrieval requires a read connection configured once by the Picapp platform administrator. In the event of unavailability, the form indicates this and keeps the last known destinations. A legacy extension absent from the catalogue remains displayed to avoid losing the configuration; no new extension absent from the catalogue can be added. A directory currently loading does not prove that a destination is available.
An external number must start with +, without spaces, separators, suffixes, prefix 00, or SIP URIs. The same allowlist policy as for other connections accepts only valid numbers categorised as landline, mobile, or landline/mobile; it rejects special, premium-rate, toll-free, shared-cost, non-geographic, or unknown types. BeAI does not look up any external contacts and is unaware of their availability. Your operator's charges and restrictions remain applicable; this categorisation does not guarantee the cost of the call. Please refer to the transfer validation limits.
The Solution's Enreach transfer permission and authorisation for actions on the platform remain required. The Internal directory permission is also mandatory for an internal extension or contact reference; it is not required for an explicitly configured and validated external number. A refusal by the platform remains possible.
Enreach Picapp supplements internal destinations with the necessary transfer checks:
- User: current presence and telephony status. An extension that is unavailable, busy, or whose availability is unknown is not transferred.
- Group or ACD group: current group presence. The absence of an individual telephony status is normal for these types; unavailable or unknown presence blocks the transfer.
- IVR or compatible voice service: no human presence check. BeAI always verifies the destination's identity, number, and access. A hidden, locked, or ambiguous contact remains rejected.
The cache contains names and types, never a presence state to reuse during the call. For a known destination, the transfer directly checks the current contact without asking the model for an additional directory search. A colleague's approval does not bypass the allowlist or the required availability. If the destination is unavailable, no transfer is sent and the bot applies the scenario fallback. Disabling Transfer or clearing its list blocks transfers; searching and consulting the colleague remain independent.
The internal directory and the same edit permissions are accessible via GET /api/v1/bots/{id}/transfer-directory. POST /api/v1/bots/{id}/transfer-directory/refresh schedules the refresh and returns 202 once queued. Re-query the first endpoint to monitor its status. PATCH /api/v1/bots/{id}/skills/transfers only accepts extension and description for each destination; names, types, and references are provided read-only by BeAI. Enreach SSO access remains restricted to the authorised bot, with CSRF protection for the refresh.
The final note retains the factual context of the transfer. For an already configured extension, BeAI directly resolves its contact and refreshes its availability, without requesting a prior directory search from the model. An empty or ambiguous resolution prevents the transfer. A transfer request accepted by Enreach does not prove that the recipient answered. A request whose outcome remains uncertain is never retried automatically.
The bot asks the caller to hold before contacting their colleague. BeAI checks that this announcement has been spoken and that its audio has finished streaming to the telephone before sending the consultation. The colleague's 60-second response window starts upon actual dispatch. For transfers, the bot announces the connection and BeAI likewise waits for its audio to finish. If the announcement is interrupted or its completion cannot be confirmed, the action is not sent and the bot applies fallback instructions. A timeout does not force a transfer in mid-sentence.
Spoken words remain recorded in the history during tool chains and upon hang-up. Announcement preparation is an internal step, with no request sent to Enreach; it represents neither a consultation failure nor a response from the colleague.
Example: urgent escalation
In Edit → Enreach Picapp, two Markdown fields define the business behaviour: Directory and availability (4 000 characters) and Escalation scenarios (10 000 characters). The second describes the triggers, the information to collect, the question, the options offered to the colleague, and then the next steps in case of agreement, refusal or no response. The legacy fallback field is preserved within scenarios when reading or restoring an older configuration. Technical tool usage rules are managed separately by BeAI and cannot be edited in these fields.
Use the same Markdown editor as for greeting instructions: visual formatting or editing raw Markdown text. A ? icon next to each bot instruction field explains its role with a brief example. It also works for transfer destinations, schedules and usage rules for other skills, including newly added rows. Open it with a click or from the keyboard; Escape closes it. Labels and help text follow the English or French interface language.
For example:
For a blocking incident, collect the name, site and symptoms. Look up the Support group in the directory. Ask the user of this extension to choose between "Transfer to support" and "Take a priority message". Follow the choice received. Without a confirmed response, take a priority message and indicate that the connection could not be confirmed.
To test this journey without involving a live team, your Enreach administrator can create an IVR extension that plays a test announcement. Add only this extension under Transfer. In the Picapp scenario, offer "Transfer to on-call" or "Take a message", and require a confirmed choice before transferring to the configured extension. A refusal or timeout keeps the call with the bot to take a message. The destination announcement must clearly state that it is a demonstration.
Before a consultation or a directory/presence lookup, the bot audibly announces that the caller should hold, using an appropriate phrase such as "Please hold on while I gather some information". It then uses the consultation tool to present the options, including for a user choice test. It does not ask the caller for these choices. Tool results appear in the conversation. If capability discovery fails or consultation is not available in a compatible format, no pop-up is sent. An uncertain outcome does not prove that the user received or ignored the request; only a confirmed choice allows proceeding based on their response. If the outcome remains uncertain, further consultation or transfer within this call is blocked, even if the caller asks to try again. The bot then receives a pre-send rejection and must state that no new request was dispatched. After a confirmed choice, further consultation remains possible.
The choice pop-up is sent to the user associated with the subscription, on myIstra or their compatible mobile application. It accepts between two and six choices. The response must match an offered choice exactly (its label or its number in the documented format). Unmatched free text or ambiguity between a numeric label and a choice number does not count as agreement. The waiting time lasts a maximum of 60 seconds after sending. It does not arbitrarily contact another agent in the directory. The capabilities advertised by Enreach on the call determine what is available. BeAI adapts the technical format of the choices to the received declaration. On platforms using comma-separated choices, each label must contain no commas or leading/trailing spaces; an incompatible label is rejected before sending. During the pilot, verify that each choice appears as a distinct button and that clicking it produces the correct outcome in the conversation; format adaptation alone is not sufficient to confirm pop-up operation.
The question and options intended for the colleague remain in the Enreach pop-up. To the caller, the bot only announces that it is consulting a colleague, followed by the next step for the call. Parameters, codes and tool names are not spoken lines to be read out. With the voice engine, the history contains the audio transcript; internal model preparation text is excluded from it.
Transfer uses Enreach's dedicated telephony API. It may therefore be available even if the list of consultation capabilities does not include a transfer function. Destinations in the Transfer skill and plan permissions remain mandatory. Directory and presence checks apply to internal destinations; configured external numbers are revalidated without assuming availability. A server rejection or an uncertain transfer response appears in Actions; no automatic retry is initiated.
Call notes in Enreach
BeAI publishes a single shared note at the end of the call. It includes the same summary as the BeAI conversation, all questions asked to the colleague, the choices offered and the choices actually confirmed, along with their timestamps. It also retains the context and outcome of any transfers. A human refusal remains a refusal; an uncertain response never becomes an agreement. If the request was not sent or if the timeout elapsed, the summary indicates this.
No intermediate notes are now sent following a consultation or before a transfer. The final note is generated automatically from the existing summary and preserved results, without requesting a second generation from the AI. BeAI waits for a pending summary or action for up to five minutes after the call ends. If the timeout expires, publication is marked as rejected and the summary remains in the BeAI history.
In Enreach Picapp → Subscription → Call decisions → Actions, the End-of-call note entry indicates whether publication is confirmed, rejected or uncertain. Older intermediate notes remain viewable. The same history is available via GET /api/v1/integrations/enreach/subscriptions/{id}/calls/{callId}/actions. The note is linked to the same Enreach call leg and does not require the Transfer skill. An HTTP 204 response confirms publication, even without a response body. A 200 response must contain the expected note; an empty response without confirmation of success remains uncertain. Its failure affects neither a received human choice nor billing. A publication whose outcome is unknown is not resent automatically, in order to avoid duplicates.
The results of all Enreach tools used by the bot appear in Conversation → History, including search, presence, user choices and transfer. Each automatic note also adds a system event, like other tool results, under the name enreach_call_note with its text and outcome: confirmed, refused or uncertain. It appears live and in the downloadable transcript, even for summaries published after hang-up. A retransmission does not create a second note or a second entry. These system events are subject to the same permissions as the conversation and are available in its API export GET /api/v1/conversations/{id}/transcript. Reprocessing legacy conversations uses only the preserved traces: it does not resend any notes or replay any transfers.
SIP badge
A green badge indicates that the Enreach server has responded positively to a recent SIP OPTIONS check from monitored runtimes. Checks are spaced 60 seconds apart. A partial, outdated, or unavailable check does not turn green. The measurement expires after three minutes.
The server is identified during an authorised SIP call. Prior to this first call, the status remains pending. No individual REGISTER registration is performed. This badge provides information on the SIP link; it guarantees neither available credits nor the availability of an interlocutor.
Access from Enreach and API
When your operator enables SSO on a compatible Enreach version, open an existing subscription in myTelephony and click Edit the receptionist in BeAI, next to the configuration title. The link directly opens the settings of the bot associated with this subscription, without a BeAI password. The same link on an already created Solution opens its single accessible bot or offers a choice if multiple bots are permitted. Only bots from this Solution and the authorised domain are offered. Creating a Solution does not display this link.
From Enreach Picapp applications, Configure the BeAI receptionist also opens the bot associated with your subscription, or the authorised bots for an administrator. No BeAI password is required. The location of the links depends on the version of myTelephony or myIstra and your administrator account's Picapp permissions.
If Enreach opens the link without transmitting the connection, BeAI displays Enreach did not transmit your connection. Reopening the same link is not enough: the platform must support its SSO launch. A still-valid BeAI SSO session can be reused for this same bot, after re-verifying with Enreach; it does not allow switching bots or companies.
Enreach populates the subscription link with its context identifiers. BeAI checks that they indeed refer to the same platform, the same Solution, and an active subscription before opening its bot. A missing or inconsistent context is rejected; no bot is deduced from the name, extension, or number of subscriptions. Older Enreach versions may require an update by the operator to display this button and transmit the connection.
From this editor, Configuration wizard also opens the guided interview for this same bot: onboarding, monitoring, documents, and confirmation share the same GUI/API permissions. Locked settings remain protected. If the Solution hides a setting used during the interview, it is rejected so as not to reveal hidden data; other settings remain accessible via manual configuration. The frame of the editor and wizard adopts the branding of the bot organisation's first parent with a defined brand when traversing up the hierarchy: product name, logo, colours, and background. This choice does not alter the session permissions.
Enreach transmits a one-time connection code, valid for 60 seconds. BeAI immediately removes it from the URL, exchanges it with the platform, then validates the session and authorized scope. This session lasts a maximum of 30 minutes and grants access to this single bot's settings. Accounts, billing, API key creation, and global administration remain outside this session. Solution restrictions continue to apply. Separate OAuth connection flows and Documents skill management currently require your usual BeAI access; file uploads specific to the guided interview are accessible within it. Close configuration ends BeAI access without disconnecting your Enreach applications.
An expired Enreach session, a suspended subscription, a disabled platform, or revoked administrator rights will block access. If the connection is refused, reopen the link from Enreach to obtain a new code; do not reuse the URL received previously. If the link is missing or opens a page prompting you to return to Enreach, the operator must verify the client version, SSO activation, and the registration of the management interface. Compatible Enreach versions refresh external interfaces when they detect a new Picapp version; older ones may require operator intervention. Simply possessing the bot's URL does not permit editing it. The actual launch must be validated on each platform before opening to customers.
The same operations exist in /api/v1/bots/{id} and its sections prompting, voice, and skills. The skill is configured with PATCH /api/v1/bots/{id}/skills/enreach-picapp, for example:
{
"enabled": true,
"instructions": "Respecter les descriptions des extensions dans Transfert et vérifier la présence.",
"escalation_scenarios": "Pour une panne bloquante, demander à l’utilisateur Enreach : Transférer au support ou Prendre un message.",
"fallback_instructions": "Sans choix confirmé, prendre un message sans promettre un transfert."
}
A GET on this same resource returns the guidelines, Solution permissions, Transfer activation, and permitted extensions. A PATCH preserves omitted fields; an empty string clears the guideline. Unknown fields, invalid types, or excessively long texts are rejected. The list of destinations is configured via PATCH /api/v1/bots/{id}/skills/transfers, for example {"enabled":true,"destinations":[{"extension":"202","description":"Support : incidents techniques"}]}. The same bot editing permissions apply to both skills. The read field picapp_sip_status exposes the same state as the interface. Section sip permits outbound_dtmf_enabled and codecs, for example PATCH /api/v1/bots/{id}/sip with {"outbound_dtmf_enabled":true,"codecs":["alaw","ulaw"]}. RTP test mode is configured via PATCH /api/v1/bots/{id}/conversation with {"test_mode":true}. Other SIP settings are rejected. These settings apply to the next call and are preserved after resynchronisation.
Authorised administrators can test and review a call's actions in Administration → Enreach Picapp → Subscription → Call decisions, or via Picapp operations. Results and notes remain linked to the call and its company.
For an API client using the same browser session, GET/PATCH operations on this bot's settings accept the SSO cookie. Retrieve the CSRF token with GET /enreach/sso/session, then pass it in X-CSRF-Token for each PATCH request. A standard BeAI API key continues to use the Bearer header without this CSRF token. Available operations and restrictions are identical to the SSO editor.
Former subscriptions and archived bots
Deleting a Picapp bot is handled by Enreach. The Delete and Duplicate actions are therefore not offered in its BeAI menu. Delete the subscription or its Solution on the Enreach side: BeAI archives the bot and retains its conversations. Platform synchronisation also detects deletions where notification was not received.
An archived bot disappears from the list of active bots. It remains accessible via its link and in subscription history, with the same organisation permissions. The API exposes archived and deletion_managed_by on the bot; it also rejects manual deletion. When the company's last subscription is deleted, the organisation is archived while retaining its data and wallet.
Actions, filters, and statistics
Picapp tools use the same Actions history as other skills: search, presence, consultation, transfer, and automated notes. The list and details of conversations display a distinct icon per type: consultation, directory search, presence, transfer, and note. Repetitions of the same type are grouped with a counter. Hover over it or select it using the keyboard to view each operation, its status, and its timestamp in a formatted tooltip. Escape closes the tooltip; long lists can scroll. Legacy entries without a date explicitly state this. Exports and statistics preserve all individual actions. The Enreach actions filter includes Picapp actions and legacy Enreach notes. The dashboard counts Picapp usage under the Enreach actions category. These counters include refusals and uncertain results; they do not solely represent successful actions. Retransmitting the same operation does not count it twice.
Statuses distinguish between an ongoing action, a confirmed result, an accepted request without confirmed connection, a refusal, and an uncertain outcome. A note whose creation remains uncertain is flagged as such, even if the user's choice was received. A transfer that was not requested does not become a successful transfer action.
The API exposes the same data in actions of GET /api/v1/conversations/{id} and in the list. Use GET /api/v1/conversations?action=enreach&bot_id=144 to filter (replace 144 with your bot), or GET /api/v1/conversations/action-statistics?action=enreach&bot_id=144 to retrieve counters. Time period, organisation, and bot filters remain subject to the same permissions as viewing conversations. Temporary tokens and private technical responses are not exposed in these actions.
The API uses the same instructions and escalation_scenarios fields via PATCH /api/v1/bots/{id}/skills/enreach-picapp, with the same limits and access rights. The legacy field fallback_instructions remains accepted for writing by older clients: non-empty text is added to scenarios without duplicating an identical fallback. It is no longer returned when reading. To modify or remove an already merged fallback, edit escalation_scenarios. Technical prompts are reserved for platform administrators, in their dedicated screen and /api/v1/technical-prompts; they do not appear in the skill configuration exported to users.
Limit exchanges with the model
BeAI checks capabilities in the background and resolves configured destinations during the transfer. The model no longer needs to request function discovery or search for a known contact before transferring. If the announcement has already been played, the action continues after the audio finishes without a second model invocation. Otherwise, BeAI requests the announcement before proceeding. Results passed to the model retain useful information and refusals, with less technical metadata; full details remain in the history.
For a scenario with a choice followed by a transfer to a known extension, the standard journey uses two model tool calls: consult, then transfer. Any searches that are genuinely required or a missing announcement may add steps. Token savings depend on the scenario and the provider, with no guaranteed percentage.
Administrators can also request a transfer directly to an authorised extension from Call Actions. The API equivalent is POST /api/v1/integrations/enreach/subscriptions/{id}/calls/{callId}/actions with {"request_id":"transfer-1","name":"transfer","arguments":{"extension":"204"}}. For a configured external number, use the same field, for example {"request_id":"transfer-ext-1","name":"transfer","arguments":{"extension":"+32475123456"}}. The legacy contact_id field is still accepted instead of extension for internal contacts only. Both cannot be provided together. Checks and permissions are identical.
Call end after a transfer
Enreach may close the dialogue with BeAI when the transfer begins. This closure does not mean that the caller hung up intentionally or that the transfer failed. BeAI awaits the result of the current action before requesting the final summary; any new tool request received after closure is ignored without triggering a false failed action.
An HTTP 204 response to the transfer indicates Request accepted, without confirming that the recipient has answered. If a response timeout occurs, the status remains Uncertain outcome: the request was sent, but its outcome was not confirmed via HTTP. It is not replayed automatically. The summary and the final note must preserve this distinction. Historical logs retain their recorded status.
Fewer steps during the call
For a configured destination, the bot requests the transfer directly: BeAI retrieves the extension and checks its availability if its type requires it. A consultation followed by a transfer therefore uses two tools in the standard journey, without any preliminary search. Enreach technical identifiers and formats are handled automatically.
The bot orally announces the hold before a consultation or transfer. BeAI waits until this announcement actually finishes before sending; a missing announcement requires additional preparation. The colleague has 60 seconds and can select an option or enter a free-text response. A confirmed free-text response becomes information to interpret according to your scenario; it does not grant additional permissions. Ambiguous responses remain uncertain.
The organisation, recipient, available caller details, and configured destinations are provided at the start of the call. Only availabilities retrieved during the call are used to decide on a transfer. Full results remain viewable under Actions, and the single final note also retains free-text responses.
Live transcript and call note link
During a Picapp call, BeAI automatically forwards words spoken by the caller and receptionist to Enreach. The server groups the messages and sends the full transcript in order, without calling the AI model or adding any tools. The content appears in MyIstra or the mobile app when supported by the platform version. Technical tool results and internal instructions are excluded. Automatic transcription may still contain errors; BeAI does not rewrite it for this transmission.
The single final note retains the BeAI summary as well as the colleague's questions, choices, and responses. It also contains a BeAI — Call transcript link to a read-only page: summary and speech from that call, with no access to the bot, audio, or other conversations. It does not require a BeAI login. Anyone with this link can view it for seven days: share it only with authorised individuals. Deleting the subscription, disabling the platform, or archiving the organisation will make the link inaccessible.
Link display depends on the MyIstra version. Enreach indicates that url and urlLabel are currently retained only when the note is created in the history: if the call still exists on their platform, particularly after a transfer, the link may be lost. BeAI does not recreate the note automatically, to prevent duplicates. Enreach SSO support on these links remains separate and is not required for this single-conversation page.
In Administration → Picapp Enreach → Subscription → Calls, Beone and platform administrators can view the latest transmission and select Revoke link. An "Unconfirmed transmission" status indicates an Enreach confirmation failure; the voice call continues normally. Missing transcripts, expired links, or revoked links are explicitly indicated. To reload the shared page, reopen the original link from Enreach.
On the General tab of the Solution or Enreach subscription, select Immediately or After a delay without an answer. The delay can be set from 1 to 120 seconds (20 by default) and only appears in delayed mode. Answer immediately in Do not disturb mode, enabled by default, prioritises this status sent by Enreach. Subscriptions inherit settings from their Solution, except where overrides are permitted. Visibility and modification restrictions still apply; settings apply to subsequent calls without affecting ongoing calls. The same routing_policy, delay_seconds, and immediate_on_dnd properties can be configured in BeAI and via the /api/v1/integrations/enreach Solution/subscription resources.
Schedule and extension cap
Picapp calls also use the bot’s Schedule, announcements and cap settings,
with the same viewing and editing permissions and the same
contract /api/v1/bots/{id}/telephone-policy. The cap is linked to the extension and
to its company; it shares reservations for calls and SMS messages linked to
the scenario. Renaming does not reset consumption to zero. In-progress
calls are monitored as they proceed and end with the configured
announcement when funded time runs out.
The cap never tops up the account. If the company credit no longer permits Picapp routing, Enreach may reject the call before the announcement: playing it with a zero balance is not guaranteed. Third-party carrier costs are not included in the BeAI counter. Settings remain disabled until you configure and explicitly enable them.