Learn how to configure settings and customize your chat widget
Core settings that control how the chat widget connects and responds. Manage these on the Configuration page.
The base URL of the site where the chat widget will be hosted. This URL is required for the chat widget to function properly. Ensure the URL is accurate and accessible from your website. This is a mandatory setting.
The predefined instruction or context sent to the underlying Language Model (LLM) when a user interacts with the chat widget. This prompt helps guide the LLM's responses and ensures the chat aligns with your intended behavior. For example: 'You are a helpful assistant for customer support' or 'Provide concise answers about our services.' This prompt will override any default prompts.
Select the AI model that the chat will use to answer user questions. You can choose a specific model from the available options, or select 'Auto' (default) where the system automatically analyzes each question and selects the most suitable model based on its complexity.
Controls how varied and creative the assistant's replies are. Pick one of three presets — Precise, Balanced (default, recommended), or Creative — or use the slider to set any value between 0.00 and 1.00. Lower values stay closer to your knowledge base and produce stable, repeatable answers ideal for support, policy, and factual Q&A. Higher values introduce more variation in wording and tone, which is better for brainstorming, marketing copy, or conversational engagement assistants. The setting applies uniformly across every supported model (OpenAI and Anthropic), so switching models won't change the tone of your assistant — switching style will.
When enabled, search results retrieved from your knowledge base are re-scored using a cross-encoder model before being sent to the LLM. This typically produces more relevant and precise responses at the cost of a small amount of additional latency per query.
Visual and behavioral settings that control how the chat widget looks and feels. Manage these on the Customizations page.
The title displayed at the top of the chat widget. This can be used to provide context for the chat, such as 'Customer Support', 'Ask Us Anything', or your company name.
The primary color used for the chat widget, including buttons and headers. Use a hex color code (e.g., #123456) to match your brand's theme and create visual consistency.
The name displayed for the chat agent, such as 'John Doe', 'Support Bot', or 'AI Assistant'. Enable 'Allow multiple names' to provide several names instead of one — the widget then picks one at random for each visitor's chat session and keeps it consistent throughout the conversation, making the assistant feel more personal across users.
The icon for the chat widget. You can upload a PNG or JPEG image (square, 64–128px recommended, up to 150 KB). This icon will be displayed in the chat interface to represent your brand.
Show a small circle with the agent's logo next to each of its messages, as in common chat apps. This option is available only after an icon is uploaded; without a logo in use it stays disabled.
The text displayed on the chat button. For example, 'Start Chat', 'Ask a Question', or 'Get Help'.
The placeholder text shown in the search input field. This guides users on what they can search for, such as 'Search FAQs', 'Type your question', or 'What can we help with?'
Enable streaming responses to chat. When enabled, the chat widget will stream responses in real-time as they are generated, providing a more interactive and engaging experience.
The direction of the text in the chat widget. Options include: Auto (automatically detects based on language), Left-to-Right (LTR), or Right-to-Left (RTL) for languages like Arabic or Hebrew.
Use the Install Widget page when you are ready to add the chat widget to your website.
The page shows whether your Host URL is configured, whether the widget script is ready, and whether your Knowledge Base has indexed content.
Copy the generated script from the Install Widget page and paste it into your website HTML. The script includes your tenant id and widget position.
The Dashboard highlights setup actions for Configuration, Knowledge Base, Customizations, and Install Widget so new users can finish deployment from one place.
Connect your own tools so the assistant can act on live data, not just answer from documents. Manage these on the Integrations page.
Register a Model Context Protocol (MCP) server your team already runs — ticket search, order lookup, an internal knowledge API — by giving it a name and URL. The assistant becomes an MCP client and can call your tools live during a conversation, retrieving real-time or transactional information instead of answering only from uploaded documents.
After adding a server, click Scan to discover the tools it advertises along with their descriptions. Enable the specific tools you want the assistant to use — disabled tools are never offered to the model. Re-scan at any time to pick up new tools; your enable and display choices are preserved by tool name.
Decide whether end users see tool activity. Turn on Show in chat to display a small indicator while a tool runs, and set a friendly Display text such as 'Searching ticket history…'. Leave it off to keep tool calls behind the scenes.
Servers can be open (no auth) or protected with a Bearer token. Tokens are stored securely in a secrets vault and are never displayed again after saving.
The server must speak MCP over HTTPS (streamable HTTP or SSE). Tool calls are bounded per conversation turn to keep responses fast, and tool output is treated as untrusted data. No website changes are needed — your embedded widget automatically gains access to the tools you enable. Tool support currently runs on Anthropic (Claude) models.