It is 11:04pm. You closed the work laptop three hours ago, ate dinner standing up, and now you are staring at six support emails for a side project that makes a few hundred dollars a month. Two are the same question about exporting data. One is a refund request written in all caps. This is the moment most side projects start to die: not from a lack of users, but from the founder quietly deciding that answering strangers at midnight is not worth it.
It does not have to work like that. Customer support for side projects is a systems problem, not a time problem. You will never have more hours, so the goal is a small machine that answers the repetitive stuff automatically, batches the rest into moments you actually have, and only interrupts you for conversations that genuinely need a human. Here is the playbook, in the order I would set it up.
Step 1: one inbox, not five contact forms
Indie hackers accumulate projects the way other people accumulate browser tabs. Each one gets its own contact form, its own support@ alias, its own half-configured Gmail filter. Then a customer writes to the wrong address, waits four days for an answer, and churns. The fix is boring and effective: route every project into one shared inbox, where each project stays cleanly separated but you only ever check one place.
In muro, every project is its own site with its own widget and its own scoped API key, but all conversations land in the same inbox. Checking support goes from opening five tabs and trying to remember which project the frustrated customer uses to scanning one list. The pricing matches this model: Solo is $19/mo for up to 2 projects and Fleet is $59/mo for unlimited projects, both with unlimited agents. Adding a cofounder, or the friend who covers for you on vacation, costs nothing extra.
Install is one snippet per project. The widget is around 6 KB and loads async, so it will not wreck the Lighthouse score you spent a weekend optimizing:
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>For projects living on a no-code builder, the same snippet goes in the custom code section of the site settings. One honest warning: most site builders only allow custom code on their paid plans, so check that before you build a plan around a free tier.
Step 2: let AI answer the repetitive stuff while you sleep
Read your last 30 support emails. Most of them are answered somewhere in your docs, your FAQ, or that one changelog post from March. "How do I export my data?" "Does this work with my stack?" "Where do I change the billing email?" These questions do not need you. They need something that has read your docs and can type.
muro's AI auto-reply is grounded on your published help articles and product context. You point it at what you already wrote (import the URL of your docs or FAQ and it pulls the content in), and it answers visitor questions from that material. When the answer is not in the material, it does not improvise a confident guess. It hands the conversation to a human. Grounding matters, because a bot that hallucinates a refund policy at 2am is worse than no bot at all.
The handoff rule is the whole trick
What makes this safe for a side project is what the AI refuses to touch. Refunds, account and billing problems, and visibly angry messages get handed off instead of auto-answered. Those conversations wait in the inbox for you, and that is the correct behavior: an upset customer wants a person, and a thoughtful human reply the next morning beats an instant useless bot reply every single time.
- →A password question at 3am: the AI answers from your docs, the customer is unblocked, and you never see the thread.
- →"Does the API have webhooks?": answered from the docs page you imported, conversation closed.
- →"You charged me twice, fix this now": handoff. The thread waits for you, flagged, with full context attached.
On limits: Solo includes 1,000 managed AI credits per month and Fleet includes 3,000, where 1 credit is 1 AI action. For most side projects that is plenty. If one project runs hot, or you simply hate metered anything, paste your own Claude (Anthropic) API key: BYOK gives you unlimited AI at zero markup, so you pay Anthropic directly and muro adds nothing on top.
Step 3: answer from your phone, not from a dashboard
A hard truth about side project support: you will not open a dashboard every day. You already have a day job full of dashboards. Any system that depends on you remembering to log in and check will quietly rot within a month.
So flip the direction. Turn on email forwarding and every new conversation lands in the inbox you already check compulsively: your personal email, on your phone, in the queue at the grocery store. Reply-by-email closes the loop. You hit reply, type three sentences, and the customer receives your answer in the chat widget or in their own email thread. No login, no context switch, no telling yourself you will handle it when you get home.
This is the step that makes support survivable alongside a day job. The AI absorbs the volume, and forwarding turns whatever remains into two-minute phone replies instead of a nightly admin session you will learn to dread.
Step 4: automation rules, so triage happens without you
Once two or three projects share one inbox, the next failure mode is mush: one long list with no signal about what matters. Automation rules fix that. They run on every incoming conversation and do the boring sorting a support hire would do on their first day.
- →Tag by project, so you can batch: project A's threads on Tuesday night, project B's on Thursday.
- →Route anything mentioning refunds, charges, or cancellation straight to a priority tag that reaches your phone.
- →Fire a saved reply on known-issue keywords, like a heads-up that the fix for the export bug ships this weekend.
- →Tag feature requests so they pile up in one place you can mine when you plan the next release.
Saved replies deserve their own mention. You do not realize how much of support is retyping the same three paragraphs until you stop doing it. Write the answer once, insert it with two clicks, tweak one sentence for the specific case, send. Ten conversations become fifteen minutes.
Step 5: when a project takes off, give your coding agent the inbox
Bug reports are the most valuable tickets and the most annoying to process. A customer describes a bug in chat, you read it on your phone, mentally file it, forget it, and rediscover it three weeks later when someone else hits the same wall.
muro ships a hosted MCP server, which means your coding agent can read support conversations directly. If you build with Claude Code, Cursor, or any other MCP client, the connection is one command with a scoped API key:
bashnpx mcp-remote https://muro.chat/api/mcp --header "Authorization: Bearer mr_live_…"Now, inside a coding session, you can ask the agent to pull recent conversations tagged bug, summarize the reproduction steps, and open the relevant files while the report is still fresh. The customer explains the problem once, in their own words, and those same words end up in front of the agent that fixes it. For a solo founder, this is the closest thing to a support engineer on staff. If you would rather script it yourself, the full REST API and webhooks sit underneath.
What this looks like on a random Tuesday
During work hours, the AI quietly answers the documentation questions and you never see them. At 2pm a refund request arrives: the handoff kicks in, a rule tags it priority, and it lands in your phone inbox. You reply from email in ninety seconds on your coffee break. At 9pm you open the shared inbox once, batch through four human threads with saved replies, spend two minutes turning one new question into a help article, and close the laptop at 9:20.
That is the whole system. Not zero support, but support that fits inside the margins you actually have, and degrades gracefully during the weeks when you have no margins at all. Your users get faster answers than plenty of funded teams manage, and your side project stops being a second job.
If your setup today is a contact form wired to your personal Gmail, this is a one-evening fix. Create a site in muro (14-day free trial, no card), paste the snippet into each project, import your docs URL so the AI has something to stand on, and switch on email forwarding. Tomorrow at 11pm, sleep instead. If you want to poke around first, the live demo is open.