Configure SupportSuite from account creation to go-live.
The documentation follows the same order as a typical rollout so you can test each layer before adding more automation.
Getting Started
Create an account, verify the email address, add the first website, configure the widget, copy the installation code and run a test conversation before going live.
Account Setup
Customer accounts live under the dashboard. The platform-owner account is separate and cannot be created through customer registration. Enable 2FA and review active sessions after the first login.
Website Setup
Each website has its own public identifier, allowed domains, widget settings, AI configuration and analytics. Free workspaces can add up to the configured website limit.
Widget Installation
Copy the generated script from Dashboard → Websites and paste it near the closing </body> tag. The bootstrap request validates the browser origin against the website domain list before issuing a short-lived widget token.
Customization
Choose launcher style, position, offsets, primary color, text color, greeting, widget title and light/dark behavior. Premium entitlements can remove platform branding.
Staff
Invite staff and assign Owner, Admin, Manager, Agent or Viewer roles. Permission checks are performed on the server; hiding a menu item is not treated as authorization.
Inbox
The desktop inbox separates conversation list, active conversation and visitor context. On mobile the list and active conversation become separate views, with the composer fixed at the bottom.
AI
Configure an AI agent per website, add instructions and knowledge sources, and define escalation behavior. Human takeover stops AI ownership. Let AI Continue returns ownership only after an authorized staff action.
Knowledge Base
Add company details, FAQs, policies and other approved text sources. Keep outdated content disabled or refreshed so the AI is not encouraged to rely on stale information.
Analytics
Analytics records visitors, chats, messages, ratings, response metrics and operational events. Use filters instead of collecting unnecessary visitor information.
Screen Sharing
An agent sends a request. The visitor reads a safety notice, explicitly accepts, and then chooses a screen, window or tab through the browser native permission. The visitor can stop sharing at any time.
Voice
Voice calls and voice messages are entitlement-controlled features. When the platform owner disables a voice feature, customer settings cannot override that platform-level decision.
Workspaces can configure SMTP credentials, which are encrypted before storage. If allowed, the platform mail service can be used as a fallback. Visitor transcripts exclude internal notes.
Billing
Prices come from the database. The browser never determines the authoritative amount. Pay.show callbacks are verified with the configured HMAC secret and duplicate events are ignored safely.
Security
Use HTTPS, secure cookies, 2FA, CSRF protection, private media storage, tenant-scoped queries and least-privilege staff roles. Review audit and security logs regularly.
Troubleshooting
If the widget is not detected, confirm the registered domain and script site identifier. If email fails, run the SMTP test and review the email log. If chat updates stop, inspect the browser network panel and application error log.