Check platform permissions before installation
Use an administrator-controlled script insertion mechanism or the existing theme workflow. A Custom HTML content block is not a substitute for a reliable site-wide script placement, and restricted hosting can remove scripts.
Use an account authorised to make the change and keep a way to revert it. Platform labels and plan rules can change, so check the linked documentation if the described setting is unavailable.
Setup steps
Installation displays the assistant. It does not automatically make every answer complete or accurate. Train and test the business knowledge separately.
- Create the business workspace and add approved information.
- Approve the exact production hostname and any separate staging hostname in widget settings.
- Copy the embed snippet shown for your business; do not reuse another tenant snippet.
- Check your hosting and account permissions first. Keep the theme backup and place the copied dashboard snippet once using the approved site-wide method. Do not scatter duplicate script blocks through individual posts.
- Publish only after the staging or preview test, then inspect the real visitor experience.
Verify the public page and the saved enquiry
Test a post, a service page and a cached page while logged out. If an optimisation plugin delays scripts, inspect whether the widget can still open and exchange messages. Clear only the relevant cache after a deliberate change.
Ask a known question, an unsupported question and a voluntary contact request. Inspect the enquiry in the correct workspace. Confirm the requested callback and any appointment preference remain unconfirmed until staff responds.
Troubleshoot the specific failure
If nothing appears, check that the snippet exists on the published page, the approved hostname matches and there is not a second copy of the loader. Inspect browser errors without sharing account secrets. Check site security policy and cache settings through the administrator responsible for them.
If the widget opens but a reply fails, separate a loader issue from business knowledge, token or service availability. Keep the public form or telephone route available while you diagnose. Avoid changing several configuration settings at once because it becomes harder to identify the cause.