A useful setup for owners of static html sites begins with the information visitors need and the handoff the team can reliably cover.
Install website chat on any HTML site: setup in practice
Test the install website chat on any html site experience
A contractor can answer service-area and estimate-process questions from published information.
Source and next step for install website chat on any html site
The install website chat on any html site workflow should cite approved information and identify who can confirm an open detail.
Install website chat on any HTML site launch owner
Your chosen reply channel
A named teammate owns the install website chat on any html site install and reply path.
Check Slack beta access before routing install website chat on any html site requests there.
Installation steps
- 1
Copy the snippet
Copy the complete snippet from the Install page for the correct MivoChat site.
Illustration — your screen may look slightly different. - 2
Add it before the closing body tag
Open the shared HTML template, or each page that should show chat, and paste the snippet immediately before `</body>`.
Illustration — your screen may look slightly different. - 3
Publish and test
Save and deploy the files. A `file://` preview will not work; use a published HTTP or HTTPS site.
Illustration — your screen may look slightly different. - 4
Step 4
In MivoChat, allow the exact production origin where the widget will run.
- 5
Step 5
Open the published site in a private browser window, send a test message, and verify a team reply reaches the visitor.
Before you start on Owners of static HTML sites
The script loader needs a real HTTP or HTTPS origin. It refuses opaque `file://` origins.
For a plain HTML site, choose the shared template that serves every page with chat, and confirm the deployment process can publish that file.
- You can edit the live site's shared template or upload revised HTML files.
- You can distinguish the production URL from a preview or staging URL.
- The copied key belongs to the MivoChat site for this business.
- You have a browser and a second device available to check the live widget.
Step-by-step Owners of static HTML sites setup
Use this sequence to place the loader in the shared document and verify it on the public HTML site.
- Copy the complete snippet from the Install page for the correct MivoChat site.
- Open the shared HTML template, or each page that should show chat, and paste the snippet immediately before `</body>`.
- Save and deploy the files. A `file://` preview will not work; use a published HTTP or HTTPS site.
- In MivoChat, allow the exact production origin where the widget will run.
- Open the published site in a private browser window, send a test message, and verify a team reply reaches the visitor.
Domains and content security policy for Owners of static HTML sites
Register the public HTTPS origin in the MivoChat site's allowed websites before testing the HTML install.
For CSP, allow the MivoChat app origin in `script-src`, `frame-src`, and `connect-src` so the loader, chat frame, and API calls can run.
Test on your published Owners of static HTML sites site
Open the public HTML page over HTTP or HTTPS; local file previews do not provide the origin the widget needs.
Troubleshooting Owners of static HTML sites installation
If the launcher is absent, confirm the deployed HTML includes the snippet and that the page is served from the allowed HTTPS origin; inspect the browser console for blocked scripts.
Frequently asked questions
Does MivoChat install automatically on every platform?
For Owners of static HTML sites, use the installation path described above and check the platform’s current settings if labels change.
Can MivoChat confirm bookings or availability?
For owners of static html sites, MivoChat can show an external booking link or collect a request, but it does not sync calendars or confirm availability; staff must review the request.
How do I know the installation worked?
On Owners of static HTML sites, test the published site from a private browser window. Check the launcher, send a visitor message, confirm it reaches the chosen team inbox, and reply to verify both directions.