Support on Autopilot: FAQ Bot and Templates

Fast support is the main retention factor in this niche, and silence during a mass outage is the number-one cause of churn. I show how to build support in tiers so most questions are put out on their own and only the truly complex reach you. Practice, no code.

This material is about engineering your own infrastructure and is educational in nature. You are responsible for complying with the laws of your own jurisdiction.

Why support is about money, not kindness

In the VPN niche the customer tolerates a clunky interface but doesn't tolerate two things: "won't connect" and "no one answers me." And the second hits harder. A person whose something isn't working is still willing to wait — if they see they're being heard. A person who got no reply for a day leaves and posts negativity.

Hence the task: support must answer typical questions instantly and not lose the complex ones. You can't handle this by hand at scale. We build it in tiers, where each tier filters out some people, and only a few reach a live person.

Tier 1. An FAQ bot with prewritten answers

The first line is ready answers to common pains right in the bot or miniapp. Not AI, not magic — just buttons with pre-written answers. This is enough in 80% of cases.

The mandatory minimum of questions that close most tickets:

• "VPN doesn't work" — first "switch the server / turn on Auto," then instructions for reinstalling the subscription.
• "How to pay" — step by step, with a screenshot, for each payment method.
• "How to renew" — where the button is, what happens to the term.
• "How to connect on iPhone/Android/PC" — per client for each OS.
• "Subscription didn't arrive / no key" — where to look, how to re-fetch.

The key here is to write answers for a real confused person, not for yourself. In short steps, with pictures. A person in a panic doesn't read paragraphs.

The core of such an auto-responder is matching a keyword from the message to a prewritten answer. A schematic aiogram handler:

from aiogram import Router
from aiogram.types import Message

router = Router()

# keyword -> prewritten FAQ answer
FAQ = {
    "не работает": "Открой приложение и включи режим Авто. Не помогло — переустанови подписку по ссылке из miniapp.",
    "оплатить":    "Нажми «Продлить» в miniapp — откроется оплата на сайте: СБП, карта или крипта.",
    "продлить":    "Кнопка «Продлить» в miniapp. Дни добавятся к текущему сроку, доступ не прервётся.",
    "iphone":      "Ставь Happ из App Store, потом жми «Подключить» в miniapp — подписка добавится сама.",
}

@router.message()
async def faq_autoresponder(message: Message):
    text = (message.text or "").lower()
    for keyword, answer in FAQ.items():
        if keyword in text:
            await message.answer(answer)
            return
    # nothing matched — an escalation button to a live person
    await message.answer("Не нашёл готовый ответ. Нажми «Проблема не решена», подключу поддержку.")

The order of keys matters: the first match wins, so keep narrower words above general ones.

Tier 2. Video instructions

Some people won't manage text, even short — they need video. Set up a separate channel with video instructions: 30-second clips for each action (connect, pay, renew, switch server).

For someone stuck on installation, it's easier to watch how it's done than to read a manual. In the FAQ answers, put links to a specific video: "didn't work out? here's what it looks like →."

Tier 3. Escalation to a live person

If the ready answers didn't help — a "Problem not solved" button. It moves the person into a chat with a tech-support account, where they describe the problem in detail, and a live person solves it.

The point of this tier: only those not saved by the FAQ reach a live person. These are the genuinely complex cases (a non-standard client, a rare bug, a payment dispute) — there aren't many, and you have time for them because the typical ones were filtered above.

The "you didn't figure it out" broadcast

The quietest losses are those who don't write to support at all. A person registered in the bot but didn't take the trial. Or took it but didn't connect. They don't complain — they just didn't understand how, and leave silently.

For this case — a broadcast to such users with a button leading straight to the miniapp → the instructions section or the video channel. It pulls back those you'd almost lost, and without a single ticket.

Who to catch with the broadcast:

• registered but didn't activate the trial;
• activated the trial but never connected;
• the subscription ended, no renewal (here it's already a push "come back, here's a bonus").

Templates for a mass outage

A separate story — when it went down for everyone at once (a wave of blocks, a node fell). Here silence kills fastest. Keep ready:

• A reply template in support: "We see the problem, we're fixing it, for now try the server marked Auto." Sent in one click to everyone who writes.
• A status post in the channel: "The provider is throttling TCP, switch to the backup server, we're working on it." One post removes hundreds of identical tickets.

Transparency at the moment of an outage paradoxically raises loyalty: the customer sees the service is alive and being handled, not "it died again and no one cares."

About AI support

If you have lots of resources, you can layer an AI assistant that answers in free text on top of the FAQ. But honestly: at the start it's overkill. Well-written ready answers to typical pains are enough almost always, and AI adds costs and the risk that it makes things up. Start with buttons and templates, bolt on AI when you hit the volume.

Checklist

• [ ] An FAQ bot with ready answers to the 5-7 main pains, for a confused person.
• [ ] A channel with 30-second video instructions for each action.
• [ ] A "Problem not solved" button → transfer to a live person.
• [ ] A broadcast to non-activators → a button to the instructions.
• [ ] A reply template + a status post in the channel for a mass outage.

Multi-tier support is part of the overall retention funnel; how it's built into the miniapp and the client's overall path, see in the business section on the funnel.