Key differences
| Aspect | Chat Assistant | Website Chatbot |
|---|---|---|
| What it is | A standalone, full-page chat interface | A collapsible widget that floats on your website |
| Layout | Occupies the full browser window with a conversation list on the left | Opens as an overlay in the corner of the page |
| Best for | Internal tools, dedicated support portals, team-facing assistants | Customer-facing websites where the chatbot supplements existing content |
| Typical use cases | Knowledge base Q&A for employees, onboarding assistants, research tools | Live support widgets, product recommendation bots, FAQ assistants |
| How users access it | Via a shareable link (optionally protected with SSO or password) | Via an embedded script tag or iFrame on your website |
| Conversation persistence | Built-in: users see their full conversation list | Configurable: you set how long conversations persist for returning visitors (default: 1 week) |
| Launcher | Not applicable (the chatbot is the full page) | Customizable launcher button with configurable icon, text, and position |
| Setup complexity | Simpler: share a link or protect with SSO | Slightly more involved: embed a code snippet, configure launcher position and appearance |
Choosing a template
Choose Chat Assistant when you want to give users a dedicated, full-screen chat experience. This works well for internal teams, knowledge portals, and any situation where the chatbot is the primary interface the user interacts with.

Next steps
Chat Assistant
Deploy and customize a full-page chat experience
Website Chatbot
Embed and customize a chat widget on your website
