Widget setup and customization
Widget settings control how your AskAnyDocs assistant appears on your website. Learn how to align branding, choose a useful starter question, preview the chat experience, and check the widget before launch.
The widget settings page controls how the AskAnyDocs assistant appears on your website. Good widget configuration makes the assistant feel like part of your product instead of a separate tool added at the last minute.
Branding options
You can configure the main visual and text elements visitors see:
- bot name
- accent color
- avatar or logo
- starter question
- button text
Use a bot name that makes the assistant's purpose clear. For example, Docs Assistant, Support Assistant, or Ask Product Docs is more useful than a generic name that does not explain what the widget can answer.
The accent color should fit your website theme while staying readable. If your brand color is very light or very dark, test the widget preview to confirm that message bubbles, buttons, and links have enough contrast.
Avatar and logo
An avatar helps visitors recognize the assistant. You can use a product mark, company logo, or simple support icon. Choose an image that remains clear at small sizes because the widget header and launcher may display it in a compact format.
Avoid images with tiny text or complex details. If a logo is unreadable when small, use a simplified mark.
Starter question
The starter question is one of the most important widget settings because it tells visitors what the assistant is good at. A focused starter question increases the chance that users ask relevant questions.
Good examples:
How do I upload my documents?Can you explain the pricing plans?How do I embed the widget on my website?What can this product help me with?
Weak examples:
HelloAsk anythingHow can I help?
Generic prompts are not always wrong, but specific prompts set better expectations when your assistant is trained on documentation.
Previewing changes
The settings page includes a live preview so you can see how the widget header, messages, and trigger button will look before saving. Use the preview to check:
- whether the color matches your site
- whether the bot name fits on small screens
- whether the avatar is recognizable
- whether the starter question sounds natural
- whether the button text is clear
Previewing is especially important before adding the widget to mobile pages. Long names or starter text can feel cramped on small screens.
Embedding the widget
After saving the widget settings, copy the embed snippet from the current bot settings page and place it on your website where scripts are normally loaded. In most websites this means adding the script before the closing </body> tag or through your tag manager.
The widget should be embedded only on domains you control. Add your website to the allowed domains list before going live so the widget can load for visitors.
Recommended launch checks
Before going live, verify:
- the welcome or starter question matches your use case
- the branding fits your site and remains readable
- the bot can answer the most common visitor questions
- fallback or support escalation is configured if needed
- the widget appears correctly on desktop and mobile
- your production domain is allowed
After launch, review conversations during the first few days. If visitors ask questions the bot cannot answer, update the indexed documentation and test again.
Related articles
Getting started
Start here if you are setting up AskAnyDocs for the first time. This guide explains the complete workflow: creating a bot, adding knowledge sources, checking indexing quality, configuring the widget, and preparing your assistant for a live website.
Create your first bot
The bot creation wizard guides you from basic company information to resources and preview settings. This article explains what each step does and how to make choices that improve answer quality.
Add website, documents, videos, and cloud sources
AskAnyDocs can index website pages, sitemap URLs, exact URL lists, uploaded files, YouTube transcripts, Google Drive files, Notion pages, and manual Q&A pairs. This guide explains when to use each source and which file formats are supported.