Keep three people focused on product. Answers from your docs. Team replies in Slack or Telegram.

Support friction in a three-person SaaS team

The support queue rarely arrives as one neat category. A founder gets a question about invoices, an engineer gets a screenshot of a failed import, and the person who owns onboarding is asked to explain role permissions again. With three people, interrupting any one of them changes the day’s shipping plan. A widget that only collects email addresses adds another queue; it does not answer what is already documented.

Common questions have concrete answers in product pages: “Does the Team plan include SAML SSO?”, “How do I export a workspace before renewal?”, “Can I invite three teammates?”, and “How do I rotate my webhook secret?” Those do not all have the same risk. A plan comparison can be public; a request to change a customer’s workspace requires someone with access. The support experience should tell those cases apart.

• Plan and feature availability before a buyer books a call.
• Setup instructions customers need while the team is offline.
• Private billing, access, and data changes that need an accountable person.

Answers tied to the product you actually ship

Connect the public pages that describe your current plans, onboarding steps, and troubleshooting paths. MivoChat uses that material as the answer source. If the docs say SAML is Enterprise-only, the assistant can state that; if your pricing page does not settle a question about a grandfathered contract, it should say it does not know and hand the conversation to the team. This is useful only when the public documentation stays current, so make an owner responsible for plan and release notes.

The team can receive unresolved questions in a Slack thread or Telegram topic. The conversation remains in the website widget for the visitor, while your teammate reads the context and replies from the channel. Someone can take over, ask a follow-up, hand the conversation back to AI when the exchange is complete, or close it. No one needs to ask the customer to repeat the whole issue in a different support portal.

A fair comparison for a three-person team

Starter is $29/month and includes 3 seats, 1 site, and 1,000 AI replies each month. Pro is $99/month with 10 seats, 5 sites, and 10,000 replies. These are flat plan prices, not a fee for each teammate or resolved conversation. Paid billing checkout is still coming soon; the 14-day trial does not require a card.

A useful comparison needs to account for how each product counts work. MivoChat counts AI replies, typically 3 per AI-handled conversation by default, rather than counting one conversation as one reply. At that default, 333 AI-handled conversations use about 1,000 replies. Fin at $0.99 per resolved conversation would cost about $329.67 for that volume, before any seat charges. The assumptions matter: one-reply conversations cost less on Fin, while longer conversations consume more MivoChat reply allowance. The calculator and plan page show the inputs clearly.

Install the widget where customers ask

For a marketing site or docs site, add the MivoChat widget script to the shared site layout so it appears on the pages where support questions start. Use the site key from the workspace. If you run a Next.js App Router site, put the script in the root layout’s body using the supported script placement for your app, using next/script. Keep it out of authenticated account screens if those pages expose private data or create an expectation that the assistant can see it.

Connect the pricing, onboarding, and troubleshooting URLs after installing the widget. Test a public question such as “Can I invite three teammates?” and one account-specific request such as “Please change my billing email.” Confirm that the first answer is supported by the plan page and the second is handed off. The script is: <script src="https://mivochat.app/widget.js" data-site="YOUR_SITE_KEY" async></script>. Review the visitor experience on a narrow screen before placing it on every page.

Keep product support inside its real boundary

MivoChat does not read a private workspace, inspect a user’s invoice, change permissions, issue refunds, or perform account actions. The answer should clearly state the supported instruction, and important policy URLs should remain explicit in your public pages.

A human should own security incidents, data export requests tied to a particular account, plan exceptions, and reports that conflict with your documentation. MivoChat can say “I don’t know” when the available material is insufficient and route the question. That answer is better than inventing a product behavior, but a handoff only works if somebody in the team watches the connected channel and responds.