How to add a live chat widget to Wix, step by step

You built your site on Wix, the contact form technically works, and questions still leak everywhere: your personal inbox, social DMs, sometimes nowhere at all. A visitor who has to open an email client to ask does this work with my setup? usually does not bother. They just leave. A chat bubble catches that question in the exact moment it happens, which is also the moment the person is closest to paying you.

This guide walks through adding a live chat widget to a Wix site with muro. The mechanical part is short: copy one snippet, paste it into Wix's Custom Code settings, publish, test. Then comes the part that actually saves you hours, which is pointing the AI at your help content so it answers the repetitive questions and hands anything sensitive to you.

What you need before you start

• →A Wix site on a Premium plan with your own domain connected (see the callout above).
• →A muro account. Signing up starts a 14-day free trial, no card required.
• →About ten minutes, plus whatever help content you already have. An FAQ page counts. So does a long how it works section.

Do you need a widget at all, or is built-in chat enough?

Wix has chat functionality of its own, and if you run exactly one site and answer every message yourself, it may be all you need. The case for a dedicated widget comes down to three things. First, one inbox: every muro site reports to the same place, so running two or five projects does not mean checking two or five dashboards. Second, AI grounded on your content: you import your docs once and the widget answers from them instead of guessing. Third, programmability: a full REST API, webhooks, and a hosted MCP server mean your support data is not stuck inside a site builder. If none of that matters to you yet, bookmark this and come back when project number two ships.

Step 1: create the site in muro and grab your snippet

In muro, create a new site. A site is one project with its own widget, its own AI settings, and its own slice of the shared inbox. Open the widget settings for that site and you will find your widget ID along with the install snippet. It looks like this:

html<script>
  (function(w,d,s,o){
    w.MuroChat=o;w[o]=w[o]||function(){(w[o].q=w[o].q||[]).push(arguments)};
    var j=d.createElement(s);j.async=1;j.src='https://muro.chat/widget.js';
    d.getElementsByTagName('head')[0].appendChild(j);
  })(window,document,'script','muro');
  muro('init',{widgetId:'YOUR_WIDGET_ID'});
</script>

Replace YOUR_WIDGET_ID with the ID from your dashboard. The script weighs about 6 KB and loads async, so it will not block your Wix pages from rendering or drag down your page speed score. Wix templates load enough JavaScript already; your chat widget should not add to the pile.

Step 2: paste the snippet into Wix Custom Code

1. 01Open your site's dashboard on Wix. Not the visual editor, the dashboard.
2. 02Go to Settings and look for the advanced section, then click Custom Code. If you cannot find it, type custom code into the dashboard search bar and it will take you there.
3. 03Click + Add Custom Code.
4. 04Paste the full snippet into the code box and give it an obvious name, like muro chat.
5. 05Under the pages setting, choose All pages and set the code to load once, not on every page transition.
6. 06For placement, pick Head. The script is async, so putting it in the head is safe and gets the widget on screen sooner.
7. 07Click Apply.

If you build in Wix Studio rather than the classic editor, the same capability exists there too: open the site settings and look for the custom code section, then follow the same steps. The snippet, placement, and everything after this point are identical.

Step 3: publish and test it properly

Code added through the dashboard applies to your live site, but if you have unpublished changes sitting in the editor, publish them now so you are testing one consistent version of the site. Then run through a real test, not a glance:

• →Open your live site in a private browser window. Extensions and logged-in state can hide problems you would otherwise catch.
• →Look for the chat bubble in the corner. Give it a beat on slow connections; it deliberately loads after your content.
• →Send yourself a message from the widget, then answer it from the muro inbox. Confirm the reply appears back in the widget.
• →Check your phone. Wix renders mobile layouts differently, and the bubble should sit clear of your mobile menu button. If it overlaps something, change the widget position in muro, no code edits needed.

If the bubble does not show up

• →Confirm the plan situation first: without Premium and a connected domain, custom code silently does nothing.
• →Confirm the code is applied to All pages and that you are visiting the domain the site is actually published on.
• →Check the widget ID. The snippet must contain your real ID, not the YOUR_WIDGET_ID placeholder.
• →Turn off ad blockers for the test. Some aggressive filter lists block any script with widget in the name.

Step 4: point the AI at your docs

A bubble on its own just moves questions from email to chat. The win is what answers them. In muro, open your site's AI settings and import a URL: your FAQ page, your docs, even a dense feature page on the Wix site itself. muro reads the page and uses it as grounding, meaning the AI answers from what you actually wrote instead of improvising. Add a few lines of product context (what you sell, who it is for, what you refuse to promise) and the answers get sharper still.

What to feed it

• →Your FAQ, obviously, but rewrite the answers you always retype into it first.
• →Your pricing explanations: what each plan includes, trial terms, billing questions.
• →Policy pages: shipping, returns, cancellation. These generate the most repetitive questions of all.
• →Anything you have answered three times this month. Three times is the threshold where writing it down pays for itself.

Grounding matters because a wrong answer is worse than no answer. When the AI is not confident, or the topic is sensitive (refunds, account problems, a customer who is clearly angry), it does not bluff. It hands the conversation to a human with the full transcript attached, and you pick it up from the shared inbox. That handoff behavior is the difference between an AI that helps and an AI that generates apology emails for you to write later.

Make the widget match your Wix design

Wix templates are opinionated about color, and a mismatched chat bubble looks like a sticker someone slapped on your site. In the widget settings you can set the accent color, the position (left or right corner), the size, and the agent name and avatar visitors see. You can also set the widget language, with 12+ available, so if your Wix site sells in Spanish, the chat greets in Spanish. All of it updates live, no need to touch the snippet again.

What you get beyond the bubble

The snippet is just the front door. Behind it:

• →A shared inbox for every conversation across every project, with unlimited teammates.
• →Email forwarding with reply-by-email, so messages to support@yourdomain land in the same inbox and you can answer straight from your mail client.
• →Saved replies and automation rules for the questions the AI should not handle but you answer identically every time.
• →A REST API and webhooks if you want conversations flowing into your own tools; see the API docs.
• →A hosted MCP server, so you can read and answer support threads from Claude or any MCP client without opening a browser tab.

Ship it

That is the whole job: create a site in muro, paste the snippet into Settings, then Custom Code on Wix, publish, and send yourself a test message. Then spend ten more minutes importing your FAQ so the AI starts absorbing the questions you are tired of typing. If you want to poke at a working widget before touching your own site, open the live demo and see what your visitors would see.