Documentation

Version 1.3 · Last updated 2026-09-04 · legal@prestancelab.com

This page is the technical reference for the Prestance Lab Solution. It describes the channels, device, browser, network, audio, and enrolment prerequisites that Customers and Authorized Users must meet to use the Solution. It exists to give procurement, IT, and end users a single canonical surface to consult before, during, and after deployment.

1. Overview

The Solution is an AI assistant for retail sales advisors and their managers. The advisor reaches it the way they reach a colleague: by telephone call, WhatsApp message, text message (SMS), or email. No download and no application is needed. A mobile application (native iOS / Android, also available as a browser-based web application) is available on request, and managers use the same channels plus browser-based manager surfaces that show aggregated team signals. Voice calls with the assistant run over the telephone network or, in the application, over WebRTC. The assistant never records, listens to, or contacts the Customer's clients: it captures audio only on the advisor's own calls with it and in practice sessions, and every client-facing message it drafts is sent by the advisor from their own tools.

2. Channels

Each channel is activated per Customer in the Order Form. The assistant serves only calls and messages that originate from a telephone number or email address enrolled for a seat (§7); unknown senders receive no answer.

Channel	How it works	Prerequisites
Telephone	The advisor calls the assistant's dedicated number from their enrolled mobile. Practice sessions run on the same number. Where enabled, the assistant calls the advisor back for a scheduled brief.	A mobile line with voice service; calls to and from the assistant's number allowed by the Customer's mobile plan and device policy.
WhatsApp	The advisor messages the assistant's WhatsApp Business number; briefs, drafts and reminders come back in the same thread.	WhatsApp installed on the enrolled mobile; the assistant's number saved or allowed under the Customer's device policy.
SMS	Short exchanges and reminders by text message from and to the enrolled mobile number.	A mobile line with SMS service. SMS is unencrypted on the carrier leg; prefer a call, WhatsApp, or email for client details.
Email	The advisor writes to the assistant's mailbox from their enrolled professional address; replies come from the same mailbox.	A professional mailbox; the assistant's sending domain allowed through the Customer's mail filtering.
Mobile application (optional)	The same assistant, plus in-app voice sessions over WebRTC, for Customers who prefer an application.	See §3–§6 and §9.

3. Supported devices (mobile application)

Mobile

iOS 16+ — iPhone 11 or later recommended.
Android 12+ with at least 4 GB RAM.

Desktop

Any device capable of running one of the supported browsers listed below.

Notes

iPad is supported via the iPhone application running in compatibility mode.
Chromebook is supported via Chrome on Chrome OS 110+.

4. Supported browsers

The browser-based application and the manager surfaces are supported on the following browsers:

Browser	Minimum version	Notes
Chrome	`110+`	Full support.
Safari	`16.4+`	Full support on macOS and iPadOS.
Firefox	`110+`	Full support.
Edge	`110+`	Full support.
Internet Explorer	—	Not supported.

5. Network requirements

Pursuant to Section 2.3 of the General Terms and Conditions, the Customer is responsible for ensuring that its hardware, software, network connectivity, and systems are adequate to benefit from the Solution. Telephone calls with the assistant need only a working mobile voice line. The following are the minimum network conditions for a usable in-application voice session (mobile application and browser):

Sustained throughput of at least 1 Mbps upstream and downstream per concurrent voice session.
Round-trip latency to the nearest EU edge no greater than 150 ms for natural voice cadence.
WebRTC over UDP preferred, with TCP fallback; firewall configuration should follow the LiveKit firewall guide.
WebSocket support; no aggressive corporate proxy that breaks wss:// connections.
No content-filter or inspection device that strips audio MIME types.

6. Audio hardware

Built-in laptop or phone microphone is acceptable.
For boutique-floor acoustic conditions, AirPods Pro or any wired USB-C / Lightning headset with noise isolation is recommended.
Bluetooth Classic headsets using HFP work but degrade speech intelligibility; AAC or aptX codecs are preferred.

7. Enrolment and account provisioning

The Customer Administrator enrols each Authorized User with their name, professional email address, and professional mobile number, through Prestance Lab's onboarding process. Bulk CSV enrolment is available. Prestance Lab provisions the seat and confirms it to the Authorized User on their enrolled channel.
Channel identity: the assistant serves only calls and messages from the enrolled number and address. A changed or reassigned number, device, or mailbox must be reported to support@prestancelab.com so the seat can be re-bound.
Mobile application and manager surfaces: authentication is brokered by Supabase Auth (ES256 JWTs), either by single sign-on with the Customer's identity provider — SAML 2.0 or OIDC (Microsoft Entra ID, Okta, Google Workspace, and any compliant provider), configured with the Customer's IT at onboarding — or by email and password with multi-factor authentication.
Named seats only — shared logins and shared numbers are prohibited per Section 5.3 of the General Terms and Conditions.
Password requirements (mobile application): minimum 8 characters; rotation every 12 months recommended.

8. Languages

Assistant (voice and text, on every channel): English and French. The assistant answers in the language it is addressed in.
Interface (mobile application and manager surfaces): English and French.
Additional languages on request: the voice and text layers are multilingual by design, and a new language is enabled after a testing pass on the Customer's content.

9. Application permissions (mobile application)

Microphone access — required for in-app voice. The application prompts the Authorized User on the first voice session. Without microphone access, the application cannot run a voice session; the telephone channel is unaffected.

Camera access — not used by the Solution.

Geolocation — not used by the Solution.

Notifications — not used by the mobile application.

10. What if a prerequisite is not met?

On iOS, Android and in the browser, the application checks microphone access before every in-app voice session and refuses to start without it, rather than degrade voice quality silently; on macOS the platform defers the permission prompt to the session's first audio capture. Device, browser and network prerequisites remain the Customer's responsibility under the sections above. This is by design: a degraded practice session teaches the wrong reflexes and is worse than none at all. Telephone calls need no preflight.

If the preflight check blocks a session and the cause is not obvious, contact support@prestancelab.com.

11. Related references

For service availability and support response targets, see Maintenance Services and SLAs.