Step 1 — Sign up and pick your slug
On muro.chat/signup use a real address — verification is required for invites and password reset. Pick a short workspace slug; it shows in dashboard URLs and is hard to change later.
Step 2 — Add your first site
On /onboarding/website, type the domain with no scheme and no path:
textacme.com ✓
www.acme.com ✓
shop.acme.com ✓
https://acme.com ✗ (the form strips the scheme; not a hard error but it warns)Pick a colour and a default language now — most teams set this once and never change it. The widget supports 12 languages out of the box.
Step 3 — Paste the snippet
In /onboarding/install you get the install snippet. Drop it in your <head>:
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:'wgt_…'});
</script>Step 4 — Lock the origin (recommended)
On /app/sites/<id> add your real domain(s) to Allowed origins. Until you do, anyone who finds your widget id can mount it on a different site. Locking takes 10 seconds and saves you abuse later.
Step 5 — Send a test from a real visitor
Open your site in an incognito window. Click the widget. Type "test from <your name>". You should see it land in /app/inbox within a couple of seconds — instantly if Soketi is reachable, otherwise within the 4 s polling tick.
Step 6 — Wire your inbox email
Settings → Notifications → set the address you want notified when a visitor message stays unanswered. Default delay is 90 s; tighten or relax depending on how fast you usually reply.
Step 7 — Add patterns for the boring questions
Patterns auto-reply when a visitor message matches a keyword or regex. Common ones to set up day-one:
- →
pricing · cost · how much→ your pricing page link - →
refund · money back→ your refund policy - →
hours · open · closed→ your support window - →
integration · zapier · api→ your docs / signup page
Common questions during setup
- →The widget doesn't appear on my site. Check the browser console — most issues are a CSP that blocks
muro.chat. Addhttps://muro.chatto yourscript-srcand you're done. - →It appears, but messages don't reach the inbox. Open
/app/sites/<id>and confirm your origin is in the Allowed origins list (or that the list is empty for now). - →I want to test multiple sites. Add them all under the same workspace — every conversation lands in the same inbox, filterable by site.
- →Email forwarding never fires. Either an agent is replying within the delay (good), or
Settings → Notificationsis empty (fix that).
Anything in the way? Hit reply on this post and we'll look at it. We read every email — no support ticket required.