01
Widget Installation & Delivery
Getting the browser-based widget onto a customer site via script tag or NPM package, obtaining the client key, and keeping the widget reachable under enterprise network and browser constraints.
Mapped capabilities
4 capabilities
Script tag vs. NPM/Yarn install
Head placement of the script tag, npm install --save @repai/widget, and RepAI("init", clientKey) bootstrapping.
API key retrieval and widget settings
Where the client key appears during onboarding and in widget settings; distinguishing widget client key from REST API key.
Content-Security-Policy and network allowlisting
CSP directives, Rep.ai domains and ports for firewalls and VPNs.
Browser compatibility and notifications
Supported browsers and notification setup so reps are alerted when visitors are ready to talk.
Illustrative example
- Input
- We use a React build pipeline and don't want a raw script tag. How do we install the Rep.ai widget via npm and initialize it with our client key?
- Expected behavior
- Gives the npm/yarn install of the @repai/widget package, then shows importing RepAI and calling the init form with the client key. Does not invent extra required config or a server-side setup step.