Modes of Use

Appilot delivers contextual AI assistance through two distinct modes. Both share the same backend intelligence, knowledge base, and privacy controls — but they differ in how they reach your users.

---

Mode 1: Chrome Extension

The Chrome Extension is Appilot's user-installed mode. It works on any website without requiring the site owner to do anything.

How it works

1. The user installs the Appilot extension from the Chrome Web Store (or via enterprise deployment)
2. A discreet floating button appears on every page
3. Clicking it opens a side panel with the AI assistant
4. The extension automatically detects page context: forms, fields, navigation state
5. The user asks questions and gets answers grounded in their organization's knowledge

Best for

• Internal tools: Help employees navigate complex internal web apps (ERP, CRM, HR systems)
• Support agents: Provide real-time guidance while agents handle customer cases
• Training & onboarding: Accelerate how quickly new team members learn processes
• Power users: Anyone who wants AI assistance across multiple web applications

Key characteristics

Aspect	Detail
Installation	User installs from Chrome Web Store or downloads .crx file
Works on	Any website the user visits
Requires site changes	No
Enterprise deployment	Supported via Chrome policies (force-install)
Page context	Full DOM access — detects forms, fields, structure automatically
Privacy	PII masking runs client-side before data leaves the browser

For developers

If you want to deploy the extension across your organization, see Enterprise Deployment.

---

Mode 2: Embeddable Widget

The Embeddable Widget is Appilot's developer-installed mode. The site owner adds Appilot to their web application, so end users get assistance without installing anything.

How it works

1. The developer generates a Widget API Key in the Backoffice (bound to their domains)
2. The developer adds a <script> tag with the API key, or imports via NPM
3. The widget renders as a floating assistant on the page (configurable position and style)
4. It reads the host page's DOM to understand context — just like the extension does
5. Users interact with the assistant directly on the site
6. The organization's knowledge base powers the responses

Best for

• SaaS products: Embed contextual help in your application for all your customers
• Customer-facing forms: Guide users through complex forms (insurance, banking, government)
• E-commerce: Help customers complete checkout, understand products, resolve issues
• Regulated workflows: Ensure compliance by providing guided, knowledge-backed assistance

Key characteristics

Aspect	Detail
Installation	Developer adds a script tag with API key, or imports via NPM
Authentication	Widget API Key (domain-bound) + optional user auth
Works on	The specific site where it's embedded
Requires site changes	Yes — minimal (one script tag + API key)
User installation	None — works immediately for all visitors
Page context	Full DOM access via Web Component with Shadow DOM isolation
Style isolation	Shadow DOM prevents CSS conflicts with host page
On-premise	Same JS file, self-hosted, pointed to own backend

For developers

See the full integration guide: Widget Installation.

---

Choosing the right mode

                    ┌─────────────────────────────────┐
                    │  Do your users install software? │
                    └────────────┬────────────────────┘
                                 │
                    ┌────────────┴────────────────────┐
                    │                                  │
              Yes / Internal                    No / External
                    │                                  │
            ┌───────┴───────┐                 ┌───────┴───────┐
            │   Extension   │                 │    Widget     │
            │               │                 │               │
            │ • Any website │                 │ • Your site   │
            │ • User choice │                 │ • Zero setup  │
            │ • IT-managed  │                 │   for users   │
            └───────────────┘                 └───────────────┘

Decision matrix

Scenario	Recommended mode	Why
Internal employees using various web apps	Extension	Works across all sites without code changes
SaaS product with customer-facing forms	Widget	Customers shouldn't need to install anything
Support agents on a ticketing platform	Extension	Agents can use it on any platform
Regulated form (banking, insurance)	Widget	Ensure all users have access by default
Training across multiple internal systems	Extension	One install covers all systems
Single high-traffic web application	Widget	Embedded experience, no user friction

Can I use both?

Yes. The Extension and Widget are complementary:

• Extension for internal teams who work across many web applications
• Widget for specific customer-facing pages where you want zero-friction access

Both connect to the same knowledge base and backend, so knowledge management is unified regardless of how users access the assistant.

Unified identity. A user who accesses both the extension and the widget can link their accounts so both surfaces recognize the same person, share conversation history, and apply the same role. See Account Linkage.