On this page

Installing the chat widget means creating it under Settings, then Website, then Chat Widgets, filling in its Setup and Knowledge Base tabs, then copying two script tags from the Embed Code tab into your site just before the closing body tag; no other deployment step is needed on your side.
Chat widget setup: first 5 of 7 steps
- 1Go to Settings, then Website, then Chat
- 2Fill in the Setup tab
- 3Add the domain allow-list and bot disclosure
- 4Switch to the Knowledge Base tab and
- 5Configure lead capture, if you want it
Before you start
- Widget count is capped by plan: 1 on Free, 10 each on Starter and Growth, unlimited on Scale.
- You need access to edit your website's HTML, or a platform (WordPress, Webflow, Shopify) with a custom code or tracking-scripts section.
- The widget's AI is on Growth and above and uses AI credits: every workspace gets 1,000 free each month, and an AI reply costs 10.
- Decide what you want the widget to know before you start: pricing, policies, FAQs, or documents, since a widget with no knowledge added will answer very little.
Steps
- Go to Settings, then Website, then Chat Widgets, and click New widget. Give it a Bot Name; this is an internal label, not shown to visitors when a Form Title is set.

Fill in the Setup tab. Set the Form Title, Header Subtitle, Welcome Message, Primary Color and Position under Widget Appearance. Under AI Settings, tick Enable AI Responses, choose an AI connection (Workspace default uses VGraple AI when you have no key of your own), and tick the Agent Actions you want the assistant to use: Capture leads, Request appointments, Answer from catalog, or Hand off to human.
Add the domain allow-list and bot disclosure. Under Security, list the Allowed Domains the widget may run on (leave empty during testing), and under Safety & Handover set the Automated-experience notice plus Repeat the notice after for a returning visitor.
Switch to the Knowledge Base tab and add content. Add an Article / Paste Text, an FAQ (Question + Answer), or a Website URL. Back on the Setup tab, tick Answer only from your knowledge under Safety & Handover if you want every answer strictly limited to what you have added.
Configure lead capture, if you want it. Under Lead Capture, tick Show pre-chat form, choose which Form fields to show and require (name, email, phone with a Default country code picker covering more than 30 countries), and pick the pipeline under Add to Pipeline.
Open the Embed Code tab and copy the script. It is two script tags: one that sets your widget's token, and one that loads the widget itself, both carrying your widget's unique embed token.
Paste it into your site, just before the closing
</body>tag. On WordPress this is usually a theme's footer script area or a code-insertion plugin; on Webflow and Shopify, a custom code or tracking-scripts section serves the same purpose. The launcher appears immediately once the page loads with the script present.
What you will see
A chat launcher appears in the position you chose (usually bottom-right) on every page where the script tag is present. Opening it loads the chat panel as a lazy iframe, so an unopened widget costs almost nothing on page load. Once a visitor has a conversation and it hands off, it appears in your shared team inbox tagged as a web chat conversation with the AI's transcript shown above the point a human took over.
Settings and options
| Setting or field | What it does | Default |
|---|---|---|
| AI connection | Which connected provider answers for this widget | Workspace default: your default connection, or VGraple AI when you have none |
| Answer only from your knowledge | Restricts every answer about your business strictly to the widget's own knowledge base | On (recommended); untick it to let the assistant also give general guidance about your field, said to be general, while still never guessing your prices, availability, timings or policies |
| Wait before replying (Instagram and Messenger) | How long the assistant waits after a burst of Instagram or Messenger messages, so it answers them together | 4 seconds; the website widget needs no wait, because a visitor can send their next message once the reply has arrived |
| Allowed domains | Up to 20 domains the widget is permitted to load and message from | Empty (unrestricted) until you add domains |
| Show pre-chat form | Shows a form for name, email and phone and creates a contact/lead on submit | Off until turned on |
| Automated-experience notice and Repeat the notice after | The message telling a visitor they are talking to an automated assistant, sent as its own message before the first answer on the website, Instagram and Messenger, and how often it repeats | Set per widget, repeats after 24 hours; required for compliance with Meta and general disclosure norms |
| Knowledge sharing | Whether this widget's knowledge base is scoped to itself or shared with your other widgets and WhatsApp AI chatbot | Scoped to the widget unless you share it |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Launcher does not appear on the site | The script was pasted somewhere it never executes (inside a comment, a page builder's preview-only area) or the page has not been republished since adding it | Confirm the script renders in the page's live HTML source, not just the editor, and republish the site if needed |
| Widget loads but the AI answers incorrectly or not at all | No knowledge has been added yet, or Answer only from your knowledge is on with content that does not cover the question | Add or expand content on the Knowledge Base tab; untick Answer only from your knowledge if some general reasoning is acceptable |
| "This widget is not allowed on this domain" or similar block | The allowed domains list has entries but the current site is not in it | Add the site's domain to the allow-list on the Setup tab |
| A visitor needed a person but the chat was never handed over | The visitor's wording did not match the hand-off detector, Hand off to human is not ticked, and your fallback message promises nobody, so the bot kept answering and offered a person instead | Tick Hand off to human under Agent Actions so the AI can hand over on its own judgment, or word the fallback message to promise a person; a direct request like "talk to a person" always hands over, and a handed-over chat shows Needs a person in the inbox |
| Two widgets on the same page interfere with each other | Each widget is scoped by its own embed token, so this is unusual; check for a duplicated or mismatched script tag | Confirm only the intended widget's script tag is present on that page |
Related reading
Feed the widget the same knowledge as your AI chatbot if you want consistent answers across WhatsApp and the website. See the inbox tour for how a handed-off web chat conversation appears, and escalating from AI to a human for how the handoff itself behaves.