Customize the chat widget
Control the visitor-facing title, greeting, launcher, position, logo, human support, and website access.
Title and welcome message
The title appears in the widget header and supports up to 60 characters. The welcome message is the assistant's first message and supports up to 300 characters.
Answer tone
Choose Balanced, Professional, Friendly, Concise, Warm, or Custom in Advanced settings. The selected style is applied server-side to both live widget and Playground answers.
- Custom instructions support up to 300 characters.
- Tone changes wording and structure, not the knowledge used to answer.
- Grounding, safety, same-language replies, and structured-output rules always take priority.
Test before publishing: Save the tone, then ask representative questions in Playground. A tone setting cannot make missing knowledge answerable.
Launcher and logo
Choose the teardrop, chat circle, or headset launcher, or upload a custom PNG, JPG, or WebP image. Custom launcher files must be at least 64 × 64 px and no larger than 1 MB; 128 × 128 px square is recommended.
- Logo URL is optional and appears in the widget header and assistant avatar.
- If no customer logo is supplied—or the URL fails—the AskBrew mark is used.
- Choose bottom-left or bottom-right placement.
Greeting nudge
The optional greeting appears next to the closed launcher after the selected delay. It is shown once per browser session and disappears when the visitor opens chat.
- Message length: up to 160 characters.
- Dashboard delay control: 0 to 15 seconds.
- The red badge and nudge do not reappear again in the same browser session.
Human support requests
Enable Human support requests to let the assistant start a handoff when a visitor explicitly requests a person, when it cannot confidently resolve a question, after a not-helpful response, or when the workspace reaches its usage limit. Explicit requests skip the extra consent question. An AI-guided conversation then collects the visitor's name, email, and issue through the normal chat composer before creating a request. Natural skip requests are understood, and normalized or corrected email addresses are confirmed before use.
Separate support queues: Website visitor requests go to Customer Inbox. Support requests you send to AskBrew remain under Support and in the AskBrew staff console.
Allowed websites
Enter comma-separated domains to restrict where configuration and chat requests are accepted. A listed domain also allows its subdomains. Leave the field empty only when you intentionally want the widget to work everywhere.
Test the exact published domain: A blocked domain receives no widget configuration. Include the production hostname before publishing the snippet.
Was this page helpful?