[BLOG · 36 ENTRIES]
What we've learned shipping live chat for teams who hate per-seat pricing. Pricing manifestos, engineering deep-dives, migration guides — written by the people who wrote the code.
35 entries
Guides7 min
"Is it free?" is the most asked question in AI chatbot comments, and the most dodged answer. Free tiers that block anything useful, "free" that slaps a watermark back on, trials dressed up as free. Here is how to read what free actually means, and an honest account of muro's 14-day trial with no free-forever plan.
The muro team
Guides8 min
Ticket deflection sounds great until a bad bot makes customers angrier and creates more work than it saves. The difference is whether the bot answers from your real docs and hands off the moment it is unsure. Here is good deflection vs bad, and how muro does it.
The muro team
Guides8 min
Capturing a visitor's email reliably is harder than it sounds: force a form too early and people leave, ask too late and they are gone. Here is how muro's chat collects name and email inside the conversation, and how you push those leads to a CRM or spreadsheet with webhooks and the API. No native one-click CRM integration, so we show the real flow instead.
The muro team
Guides7 min
Live chat means a human replies. An AI chatbot means automated answers. They solve different problems, and picking one over the other is usually the wrong question. Here is the honest difference and why most small sites want both.
The muro team
AI7 min
Dead-end bots that loop and never let you reach a human are the most hated thing in support. The fix is not less AI, it is AI that knows its limits and hands off the instant it should. Here is how muro does it.
The muro team
Playbook7 min
Running an AI support agency on a shared message pool means one busy client starves the rest. The fix is not a bigger pool. It is per-client isolation: unlimited projects on one Fleet account, and a separate Claude key per client so each client's AI runs at cost with zero shared budget.
The muro team
Guides7 min
A step-by-step guide to adding AI live chat to WordPress: paste the widget snippet site-wide, train the AI on your docs, and dodge the two things that actually break it. Caching plugins hiding the widget from logged-out visitors, and the icon being out of reach on mobile.
The muro team
Guides6 min
A shared Gmail mailbox stops working once two people answer it. Heavy help desks are the opposite problem: per-seat pricing and a setup you never finish. Here is the middle path: one inbox for live chat and email, with assignment, full history, and AI drafts.
The muro team
AI5 min
Flip a toggle, paste your docs URL, and an AI agent answers your visitors grounded on your real product. Here is how muro's AI Answer Agent works, and where it deliberately stays quiet.
The muro team
AI4 min
Per-resolution AI pricing punishes you for being popular. Bring your own Claude key and muro's AI runs on your account, unlimited, with no markup.
The muro team
AI5 min
The Model Context Protocol lets your AI agent act on real systems. muro exposes your support inbox as an MCP server, so the agent in your code editor can read and answer customers.
The muro team
AI4 min
Most SaaS support volume is the same handful of questions. Ground an AI agent on your docs and it handles them instantly, day one, while real edge cases reach a human.
The muro team
Guides3 min
Adding an AI chatbot to a site is usually a project. With muro it is one script tag in your head, then point it at your docs.
The muro team
AI4 min
Enterprise help desks are priced and built for support teams. Indie hackers need the opposite: flat price, instant install, and AI that handles the repetitive stuff.
The muro team
Support4 min
Most support is a search problem. Put the answers where the question is asked, in the chat, and a lot of tickets never become tickets.
The muro team
Pricing4 min
Per-seat chat pricing punishes you for adding the intern, the founder, the freelancer. Flat pricing with unlimited agents removes the tax entirely.
The muro team
AI4 min
Charging per AI resolution couples your support bill to your success in the worst way. Flat plans with included credits, plus BYOK, fix that.
The muro team
Guides3 min
You do not need an npm package or a React provider to add chat to Next.js. One script tag in the layout, around 6 KB, loaded async.
The muro team
Manifesto4 minManifesto4 min
A small idea: the chat product you pay for shouldn't make you think twice about adding a teammate. We built muro around that idea.
The muro team
Pricing5 minPricing5 min
Picking flat pricing wasn't a marketing reflex — it was the conclusion of an honest look at what it actually costs us to serve one more agent.
The muro team
Engineering8 min
You reply to a notification email and the visitor magically sees the chat update. Here's every layer between your Gmail Send button and that bubble appearing in their browser.
The muro team
Guide6 min
Sign up, create a workspace, install the snippet, send the first test message. Here's the full path with every gotcha we see in the wild.
The muro team
Guide7 minGuide7 min
Most teams already use one of five platforms — Shopify, WordPress, Webflow, Wix, or Next.js. Here's the exact path through each one's admin to get muro live in five minutes.
The muro team
Playbook6 min
You don't need a fancy AI to deflect 60% of repetitive questions — twelve well-tuned keyword patterns do most of the work.
The muro team
Engineering6 min
Twelve languages out of the box, RTL support, per-website default, and visitor-side override. Here's how the i18n layer is wired without bloating the bundle.
The muro team
Playbook6 minPlaybook6 min
First-response time is the single best predictor of customer satisfaction in chat. It's also the easiest metric to game by burning the team out. Here's how to actually move it.
The muro team
Engineering7 min
Webhook receivers are the second-easiest API code to write — and the most-dangerous to write wrong. Here's the muro contract and a verified Node receiver in 15 lines.
The muro team
Compliance8 min
GDPR isn't a label you slap on a homepage. It's seven articles your chat product touches every day. Here's the practical version for founders.
The muro team
Buyer's guide6 minBuyer's guide6 min
When you compare live chat tools, the pricing model matters more than the per-month number. Here is how per-seat and flat-rate actually differ over two years.
The muro team
Guide6 min
Static-site generators are the easiest place to add live chat: they all give you one spot to inject head markup on every page. Here is the exact spot for each.
The muro team
Data11 minData11 min
Chat converts visitors at 10 to 20 percent versus 2 to 3 percent for forms, a 5 percent retention lift can grow profit 25 to 95 percent, and 53 percent of buyers abandon if no one answers within three minutes. The full evidence, sourced.
The muro team
Engineering6 min
Everything you need to build on muro: authenticate with a Bearer key, page through conversations, send a message, and read the error envelope. Copy-paste curl included.
The muro team
Integrations6 min
Automation platforms speak HTTP, and so does muro. Point a webhook at your catch hook to trigger flows, and call the REST API to send replies back. No server to host.
The muro team
Integrations6 min
A chat that never reaches your CRM is a lead you forgot. Push contacts in real time with webhooks, or pull them in batches with the REST API. Here is both, with code.
The muro team
Engineering6 min
You do not have to accept a bundled bot you cannot tune. Wire a webhook to your own model and post replies through the API. The loop is three steps and you own every one.
The muro team
[✉ NEWSLETTER]
We send each new post when it ships. We don't sell your address. We don't even cross-sell our own stuff. Hit reply if you want to chat — Robin reads them.