Answer while you are away from the laptop. Answers from your docs. Team replies in Slack or Telegram.

The cost of being the whole support department

When one person handles product, sales, billing, and support, a simple question still interrupts focused work. A visitor cannot find an API key, another wants to undo an import, and a third asks about cancellation. Each deserves an answer, but not each needs the founder to type the same documented steps again. At the same time, an account-specific request cannot be safely handled by a general answer.

Useful examples to document include “Where do I find my API key?”, “How can I undo an import?”, “How do I cancel my plan?”, and “Can someone review a failed sync?” Keep the answer to the first three current and route the last one if it requires logs or account access. This makes the widget a small filter for repeat questions, not a promise that a founder is always online.

• Keep setup steps short enough to read on a phone.
• Publish cancellation and data export instructions before customers need them.
• Set realistic human response expectations in your own availability copy.

Telegram handoff that fits a solo workflow

Connect your onboarding and troubleshooting pages so MivoChat can answer common questions while you are away from the laptop. If the documentation does not cover a case, the assistant can admit it does not know and send the conversation to Telegram. A separate topic keeps that visitor’s question and prior messages together instead of burying them in one group stream.

Read the handoff when you have a moment, reply in the topic, and the visitor sees your response in the website widget. You can take over the exchange, hand it back to AI when the issue is resolved, or close it. A phone-friendly reply path helps between errands or while travelling, but notifications are not the same as an on-call service. Avoid promising an immediate human response unless you can provide one.

Choose a plan from actual reply volume

Starter costs $29/month and includes 1,000 AI replies, 3 seats, and one site. Pro costs $99/month and includes 10,000 replies and 10 seats. Every response generated by AI counts, so with the default 3 replies per conversation, Starter covers about 333 AI-handled conversations in a month.

For those 333 conversations, a Fin comparison at $0.99 per resolution comes to roughly $329.67 plus seats. It is an illustration, not a prediction: a conversation with one answer uses fewer MivoChat replies, while a longer exchange uses more. MivoChat is flat monthly pricing with no per-resolution charge. Billing checkout is coming soon; the trial lasts 14 days with no card.

Install it once on your public site

Most indie products use a small marketing site or documentation site. Add the widget snippet to the shared page template where visitors look for setup and billing guidance. If your site uses Next.js, use the supported App Router script placement in the root layout using next/script. A basic install is: <script src="https://mivochat.app/widget.js" data-site="YOUR_SITE_KEY" async></script>.

Start with your three most repeated questions rather than importing every old note. Connect the canonical API-key, import recovery, and cancellation pages. Ask those questions in the widget and verify the answers against the live product. Then send a question that needs private account context and check that it arrives in Telegram. If you are not available at night, make that expectation clear in your site copy and choose a handoff routine you can maintain.

Keep the human promise manageable

The assistant cannot see an account, inspect a failed job, refund a charge, cancel a subscription, or make product changes. It can only use connected documentation and say it does not know when that material is insufficient. A Telegram handoff gives you the conversation; it does not create a support rota or guarantee a response time.

For data deletion, payment disputes, suspicious activity, or a bug that affects one customer, take over and handle the case yourself. Ask only for information you need and do not request passwords or secrets in the public chat. When a published instruction changes, update the relevant documentation so the next visitor sees the new route.