Search... ⌘K

Introduction

Welcome to the official documentation for SupportBuddy β€” Weego's high-performance multi-bot Telegram customer service ticketing solution. Built to manage active support desks directly inside your native Telegram channels and groups, SupportBuddy bridges the gap between your customers and support agents flawlessly.

With SupportBuddy, you don't need a clunky external helpdesk tool. When a customer messages your dedicated Telegram support bot, SupportBuddy automatically creates a separate, cleanly isolated Forum Topic Thread inside your Central Support Group. Your agents can chat directly inside that topic, and the bot seamlessly forwards answers back to the user's private chat window in real time.

πŸš€
Clean & Threaded Conversational Context! SupportBuddy utilizes Telegram's native group Topics feature. It avoids chaotic mixing of multiple client queries by organizing each user's ticket into an independent chat topic.

How It Works (The Messaging Flow)

SupportBuddy acts as a real-time messaging pipeline. Let's trace the architectural thread:

SupportBuddy Communication Pipeline
Customer Chat
βž”
[SupportBuddy Bot]
βž”
Forum Topic (Admin Group)
Customer gets response
L
[Agent replies in Topic]
L
Agent Message

Core Features Dashboard

πŸ€–
Multi-Bot Webhook Hosting
Add and host multiple customized support bots from a single background server using secure BotFather API webhooks.
πŸ’¬
Forum Topics Integration
Automatically creates dedicated forum threads for each customer with locked user cards pinned at the top.
πŸŽ‰
Custom Welcome Messages
Set custom styled texts, pictures, or inline links to automatically welcome new users on start.
πŸ“’
Broadcasting Engine
Securely broadcast announcements to thousands of users simultaneously with visual summaries.
🚫
One-Click Banning
Instantly restrict disruptive or abusive clients from sending updates via chat actions or inline buttons.
⚑
Universal Format Sync
Perfectly supports texts, photos, inline videos, documents, audio clips, voice notes, stickers, and animations.
πŸ“‹
FAQ Auto-Responder
Answer repeat questions instantly with keyword-triggered replies, before a human agent ever has to read them.
βœ…
Tickets & Star Ratings
Close a conversation with /close and the customer is automatically asked to rate it from 1 to 5 stars.
πŸ“Š
Analytics Dashboard
A full Mini App dashboard inside Telegram: traffic, tickets, CSAT, response times, and an agent leaderboard.
ℹ️
This support suite is powered and managed by Weego's master Telegram administrator bot: @WeegoSupportBot.

Getting Started

Set up your own dedicated helpdesk bot in less than 5 minutes. Follow this step-by-step onboarding guide:

  1. 1
    Start Weego Support Master Bot

    Open Telegram, search for @WeegoSupportBot, or click the direct launch link: t.me/WeegoSupportBot. Press Start. You'll be greeted with the main setup menu.

    πŸ“Œ
    Official Channel Join Required: To unlock support bot creation, you will be prompted to join Weego's official update channel first. Join the channel and click "I've Joined" to unlock controls.
    Start Weego Support Master Bot
  2. 2
    Register Your Custom Bot Token

    Tap πŸ€– Create Support Bot in the @WeegoSupportBot main menu (or send /createbot). The bot will prompt you to enter an HTTP API token. To generate one:

    • Open Telegram's official bot architect: @BotFather.
    • Send the command /newbot and follow the instructions to choose a name and custom username.
    • Copy the generated HTTP API token (e.g. 7563482769:AAG4XT...) and send it directly to Weego Support Bot.
    Register Bot Token with @BotFather
  3. 3
    Create a Telegram Support Group

    Create a standard Telegram group for your support agents and moderators. Once the group is created:

    1. Open Group Info βž” Edit settings.
    2. Enable Topics toggle (Forum mode). This is a critical requirement for ticket sorting.
    3. Add your freshly created custom bot as an Administrator in the group. Make sure to grant permissions to "Manage Topics", "Pin Messages", and "Post Messages".
    Enable Topics in Group Settings Add Bot as Administrator with Topics Permissions
  4. 4
    Bind Support Group and Verify Webhooks

    Now open your own newly created bot in Telegram (not the master bot) and send /start. Because no support group is linked yet, it replies with "βš™οΈ Setup Required" and shows a πŸ’¬ Add Support Group button.

    Tap it and pick the forum group you created in step 3. Telegram will only let you pick groups where you are an admin and Topics are enabled β€” if your group doesn't appear in the picker, go back and check both. Once selected, the bot confirms with your Bot ID, username, and Support Group ID.

    βœ…
    You're live. From this point on, every setting β€” welcome message, FAQs, broadcasts, statistics β€” lives in your own bot's /start menu. The master bot @WeegoSupportBot is only used to create, list, and delete bots.
  5. 5
    Explore Your Owner Control Panel

    Sending /start to your own bot as its owner opens the control panel:

Support Group Setup

To establish a flawless ticket dispatching system, SupportBuddy relies on active Forum Topics inside your designated support group. If topics are not enabled or permissions are incomplete, the bot will notify you with configuration warnings.

⚠️
Topics Must Be Enabled! If you try to run your support bot inside a group that does not have topics active, the bot will display an alert: "⚠️ Setup Incomplete! Please enable Topics in group settings."

Enabling Topics & Perms Checklist

Ensure your support group settings perfectly meet the following checklist:

  • Topics Toggle: Active. Allows creation of separate conversation threads.
  • Bot Permissions:
    • Post Messages: Yes. Enabled for sending agent copies.
    • Manage Topics: Yes. Required to programmatically create and edit threads for new clients.
    • Pin Messages: Yes. Required to pin user details cards at the top of each thread.

Changing Your Support Chat Group

If you need to change your central support group in the future, send /start to your own support bot and tap πŸ”„ Change Support Group, then pick the new forum group. However, keep the following alert in mind:

⚠️
Warning: Updating your support group will sever connection to previous forum topic IDs. Past conversation threads inside the old group will no longer be accessible by the bot for replying.

Custom Greetings

First impressions matter. SupportBuddy allows bot owners to fully customize the greeting welcome message that is sent to customers when they start the bot.

How to Set Custom Greetings

  1. Open your own support bot in Telegram and send /start.
  2. Tap πŸ’¬ Set Welcome Message. If one is already set, the bot shows you a copy of it with a πŸ’¬ Change Welcome Msg button.
  3. Send the styled greeting message to the bot. You can use standard formatting like bold, italics, code, hyperlinks, and even attach media (like images or intro guides).
  4. The bot will present a preview and ask you to confirm: "❓ Are you sure you want to set this as your welcome message?". Tap Yes to save.
Edit Welcome Message Option Confirm Custom Welcome Message

Default Welcome Greeting

If you don't configure a custom greeting, the bot will automatically fall back to Weego's built-in default welcoming template:

Default Support Welcome Template
πŸš€ Welcome to [Bot Username]! πŸš€

Hi there! πŸ‘‹ I'm here to assist you with any support-related queries.

Whether you need help with our services, have a question, or need technical support, I've got you covered!
⚠️
Alert: Do not delete your custom welcome greeting source message in your personal Telegram chat window. The bot fetches and copies that message ID dynamically to greet clients; deleting it may reset your greeting to the default template!

Ticket Assignment Modes

Every bot's Settings menu has a Ticket assignment toggle that decides how your team divides up incoming conversations. Switch it from @WeegoSupportBot β†’ Settings β†’ tap the assignment row to flip between the two modes.

Open Mode (Default)

Anyone in your support group can reply to anyone. Simple, and best for small teams where everyone sees everything.

Claim Mode

The first agent to reply to a ticket automatically takes ownership of that conversation. If another agent tries to reply to a ticket that isn't theirs, their reply still goes through β€” the customer is never blocked β€” but they get a warning: "⚠️ Heads up: this ticket belongs to [Agent]. Your reply was still sent β€” use /claim if you're taking it over."

Three commands, typed inside the ticket's forum topic, manage ownership in Claim mode:

  • /claim β€” take ownership of the current ticket, including taking it over from another agent.
  • /release β€” hand the ticket back to the pool so anyone can pick it up.
  • /assign (as a reply to a teammate's message) β€” hand the ticket directly to them.
ℹ️
All three commands only work while the bot is in Claim mode. In Open mode they reply with a reminder that assignment isn't switched on.

Response Time Alerts

Response alerts chase tickets that have gone unanswered past your promised reply time, so a customer doesn't sit waiting while nobody notices. Configure it from Settings β†’ ⏰ Response alerts, choosing Off, 5, 15, 30, 60, or 120 minutes.

How the Nudge Works

When a ticket's first reply hasn't landed by the deadline, the bot posts directly into that ticket's topic:

Response Alert
⏰ Waiting 45 minutes with no reply.
Nobody has picked this up yet.

In Claim mode, if the ticket is already assigned, the alert names the agent instead: "Assigned to [Agent]."

Escalation

If the ticket still has no reply after roughly double the alert window, the bot escalates by messaging you (the bot owner) directly: "🚨 A ticket still has no reply after 2h. Bot: @YourSupportBot."

⚠️
Each ticket only gets one nudge and one escalation β€” never a repeating reminder. Alerts also stay silent outside your configured Working Hours, since a notification nobody can act on just becomes noise.

Working Hours & Away Message

Tell SupportBuddy when your team is actually online so customers get honest expectations, and your Response Alerts stay quiet when nobody can act on them anyway. Configure it from Settings β†’ πŸ•˜ Working hours.

Setting It Up

  • Enable/Disable: toggles the whole feature on or off. The first time you turn it on, a sane default weekday schedule is seeded automatically.
  • Set hours: send a range like 09:00-18:00. Overnight desks like 22:00-06:00 are supported too.
  • Days: cycles through day-of-week presets (e.g. weekdays only, every day).
  • Set timezone: send a Region/City name, e.g. Asia/Kolkata or America/New_York. This timezone also drives the Owner Digest send time.
  • Away message: customize what customers see when they message outside these hours. Include the placeholder {back} and it's replaced with when you're next open. Send default to reset to the standard wording.

What Customers See

A customer messaging outside working hours still reaches your team as normal β€” nothing is blocked β€” but they also get an automatic heads-up, sent at most once per away period so it doesn't repeat on every message:

Default Away Message
We're currently outside our working hours.
Your message is saved and we'll reply as soon as we're back.

Attachment Controls

Decide exactly what kinds of message your customers are allowed to send. Configure it from Settings β†’ πŸ“Ž Attachments, where every content type is listed with a tap-to-toggle status.

  • πŸ–Ό Photos
  • 🎬 Videos
  • πŸ“Ž Files (documents)
  • 🎀 Voice notes
  • β­• Video notes
  • 🎡 Audio
  • 🎞 GIFs
  • 🌟 Stickers
ℹ️
Text is always allowed and cannot be blocked β€” a support bot that refuses text isn't a support bot. Everything else defaults to allowed until you turn it off.

When a customer sends a blocked type, it never reaches your team. They're told politely and asked to write instead: "🚫 We can't accept [type] here. Please send your question as a message and our team will help."

Voice Transcription

Agents can't always play audio at their desk. When it's on, SupportBuddy automatically writes out a text transcript underneath every voice note, video note, and audio file a customer sends β€” right inside the forum topic β€” so your team can read instead of listen, and search it later.

πŸ’Ž
Premium feature. Voice transcription is gated to Premium bot owners by default. Attempting to enable it on a non-Premium bot shows: "πŸ’Ž Voice transcription is a Premium feature."

Turning It On

  1. In @WeegoSupportBot, open your bot's Settings menu and tap 🎀 Voice transcription.
  2. Tap βšͺ Off (tap to turn on) to enable it β€” it becomes 🟒 On (tap to turn off).
  3. Tap 🌐 Spoken language to tell the model what language to expect, or leave it on Auto-detect. Naming the language helps with short clips or when customers mix two languages in a sentence β€” but getting it wrong makes results worse, not better.
  4. Tap πŸ” Translate to English to have every transcript come back in English, regardless of the spoken language.
  5. Tap πŸ”€ Roman script (Hinglish) to get transcripts in Roman letters instead of native script β€” e.g. "aur bhai kya haal hai" instead of Devanagari. This is a nudge to the model, so the odd line may still come back in its original script.
ℹ️
Translate and Roman script are mutually exclusive β€” translation already outputs English, so turning one on automatically switches the other off.

What Agents See

The moment a voice note lands, the bot immediately posts a "πŸ“ Transcribing…" placeholder in the topic β€” silence otherwise looks like nothing is happening. That placeholder is then edited in place with the result, so the topic gains one message instead of two:

Transcript Outcomes
πŸ“ Transcript
"Hi, I wanted to ask about my refund status..."

β€” or, if nothing was said β€”
πŸ“ No speech found in this one.

β€” or, if it failed β€”
⚠️ Couldn't transcribe this one β€” the audio is still above.

Limits

  • Length cap: voice notes longer than 5 minutes are not transcribed. The bot posts "πŸ“ Voice note is longer than 5 minutes β€” not transcribed." and skips straight past β€” no placeholder, no wasted call.
  • Supported languages: Auto-detect, English, Hindi, Bengali, Tamil, Telugu, Marathi, Urdu, Arabic, Spanish, Russian, and Portuguese.
  • Server availability: if transcription isn't configured on the server yet, the toggle warns instead of silently doing nothing: "⚠️ Voice transcription isn't configured on this server yet."

FAQ Auto-Responder

Most support desks answer the same handful of questions all day long. SupportBuddy's FAQ engine watches incoming customer messages, and when one looks like a question you've already answered, it replies instantly β€” before your team ever has to read it.

⚑
Deflection, not deletion. An auto-answered message still lands in the customer's forum topic, tagged so your agents know the bot already replied. Nothing is hidden from your team β€” you simply stop being the first responder for routine questions.

Adding Your First FAQ

  1. 1
    Open the FAQ Menu

    Send /start to your own support bot and tap πŸ“‹ Manage FAQs. You'll see the list of existing FAQs, each with a 🟒 (active) or βšͺ (disabled) marker.

  2. 2
    Add Trigger Keywords

    Tap βž• Add FAQ. The bot asks for the keyword(s) that should trigger this answer. Separate multiple variants with commas so one FAQ can catch several phrasings:

    Example Trigger Phrase
    refund, money back, return policy, how do i get a refund
  3. 3
    Write the Answer

    Send the text the bot should reply with. The bot then shows a summary β€” "❓ Save this FAQ?" with your triggers and answer β€” and you tap βœ… Yes to save. You'll get "βœ… FAQ saved! The bot will now auto-answer matching messages."

How Matching Works

SupportBuddy does not require an exact match. Each incoming text message is compared against every variant of every active FAQ using fuzzy matching, so real-world typing still connects:

  • Fuzzy, not literal: "wheres my refund??" still matches the trigger refund.
  • Case-insensitive and whitespace-tolerant.
  • Best match wins: if several FAQs are close, only the strongest match replies β€” a customer never gets two auto-answers at once.
  • Confidence threshold: weak matches are ignored on purpose, so an unrelated message is passed straight to your agents instead of getting a wrong canned answer.
  • Text only: photos, files, voice notes, and stickers are never auto-answered.
πŸ’‘
Write triggers the way customers type. Short, distinct phrases work best. Very generic triggers like help or hi will swallow messages that should have reached a human.

What Your Agents See

When an FAQ fires, the customer's original message is still copied into their forum topic, immediately followed by a marker:

Auto-Answer Marker in the Topic
πŸ€– Bot auto-answered this with an FAQ response.
Reply here if the user still needs help.

Agents can simply keep typing in the topic to take over the conversation as usual.

Editing, Disabling & Deleting

Tap any FAQ in the list to open it. The detail screen shows its triggers, its answer, how many times it has auto-answered, and its status:

FAQ Detail View
πŸ”‘ Triggers: refund, money back, return policy
πŸ’¬ Answer: Refunds are processed within 5-7 business days.
πŸ“Š Auto-answered: 128 times
πŸ”˜ Status: 🟒 Active
  • ⏸️ Disable / ▢️ Enable β€” pause an FAQ without losing it or its hit count. Disabled FAQs are never matched.
  • πŸ—‘οΈ Delete β€” asks for confirmation first, then removes the FAQ permanently.

To reword an FAQ, delete it and add it again β€” there's no in-place edit.

Plan Limits

Plan FAQ Auto-Responses
Free Up to 5 FAQs per bot
Premium Unlimited FAQs per bot

Trying to add a sixth FAQ on the free plan shows: "🚫 Free plan limit reached (5/5 FAQs). πŸ’Ž Upgrade to Premium for unlimited FAQ auto-responses." See Premium Plans.

πŸ“Š
Your Analytics Dashboard ranks your FAQs by hits and shows your deflection rate β€” the share of all incoming messages that got an instant answer. Use it to find which question to automate next.

Messaging & Topics Flow

SupportBuddy dispatches client messages instantly. This section walks you through how thread mapping and forwarding behave under the hood.

User Profile Pin (Forum Header)

When a new user starts your support bot, the bot automatically creates a new Forum Topic inside your Telegram group named after the customer's full name. Inside that topic, SupportBuddy pins a user details card for quick agent context:

Pinned Thread Profile Card
πŸ‘€ User Details:
Ritik Kumar (@ritik_weego)
πŸ†” ID: 597284903

Clean Real-time Mirroring

Every message your client sends to the bot (text, photo, file, sticker, voice note, etc.) is instantly copied and posted inside their designated forum topic. Your support agents simply chat inside that topic thread. Any text, media, or file your agents type or reply with inside that topic is copied and sent back directly to the client's private bot screen.

Live Edit & Reaction Sync

Edits and reactions are mirrored in real time on both sides of the conversation β€” not just relayed once and left to go stale:

  • Edited messages: if a customer edits their message, the copy sitting in the topic thread updates to match β€” and the same happens in reverse when an agent edits their reply, the customer's copy updates too. If a message predates threading (or its counterpart can't be found), the bot falls back to a plain notice instead of leaving stale text in place.
  • Reactions: an emoji reaction added by an agent in the topic is mirrored onto the customer's copy of that message, and a reaction the customer adds is mirrored back onto the agent's copy. Custom (Premium) emoji reactions can't be set by bots, so only standard emoji reactions are mirrored.
ℹ️
Both features are cosmetic conveniences β€” if a sync fails (message too old, deleted, etc.) it's logged quietly and never blocks the underlying conversation.

Canned Quick Replies

Save your team's most-used answers as shortcuts agents can fire off with a single command, instead of retyping the same reply every time. Manage them from @WeegoSupportBot β†’ your bot's admin menu β†’ Quick Replies.

Saving a Reply

  1. Tap βž• to add one.
  2. Send a shortcut name β€” letters, numbers, underscores, and hyphens only (up to 40 characters), since it has to survive being typed as a command.
  3. Send the reply body. Include {name} anywhere in the text and it's replaced with the customer's first name (or group title) when sent.

Saving a shortcut that already exists overwrites it, and the bot tells you so rather than silently creating a duplicate.

Using It in a Topic

Inside a customer's forum topic, type /r <shortcut> to instantly send that saved reply to the customer. Typing /r with no shortcut lists every saved shortcut for that bot.

Sending a Quick Reply
/r refund

⚑️ Sent via /r refund β€” Agent Name
Your refund has been processed and should arrive within 3-5 business days.

A quick reply counts as a real agent reply β€” it starts the response-time clock, threads correctly if the customer replies to it, and (in Claim mode) claims the ticket just like a typed message would.

πŸ’Ž
Free bots can save up to 5 quick replies. Premium removes the limit.

Tickets & Ratings

A forum topic lives forever, but a conversation doesn't. SupportBuddy tracks each customer conversation as a discrete ticket so you can measure how fast you answer, how much you close, and how happy people were at the end of it.

Ticket Lifecycle
User messages
βž”
Ticket opens
βž”
Agent replies
Next message = new ticket
L
User rates 1-5 ⭐
L
Agent runs /close

When a Ticket Opens

A ticket opens automatically the first time a customer writes to your bot β€” no command needed. It stays open while the conversation continues, and the clock on your first reply time starts the moment it opens and stops when an agent posts the first message in that topic.

ℹ️
Only one ticket at a time is open per customer. Further messages join the ticket that's already open rather than piling up new ones.

Closing a Ticket

When the issue is resolved, an agent types /close inside that customer's forum topic. The bot confirms in the topic:

Close Confirmation
βœ… Ticket closed by Ritik.
The user was asked to rate this conversation.
Their next message opens a new ticket.

If you run /close in a topic with nothing open, the bot answers "ℹ️ There's no open ticket in this topic." and does nothing.

⚠️
/close ends the conversation, not the topic. The forum topic and its full history stay exactly where they are β€” the customer's next message simply starts a fresh ticket in the same thread.

Customer Satisfaction Ratings (CSAT)

The moment a ticket is closed, the customer receives a rating prompt in their private chat with the bot:

Rating Prompt Sent to the Customer
βœ… Your support request has been closed.

How did we do? Your rating helps us improve.

  [ ⭐ ]
  [ ⭐⭐ ]
  [ ⭐⭐⭐ ]
  [ ⭐⭐⭐⭐ ]
  [ ⭐⭐⭐⭐⭐ ]

Tapping a star replies "πŸ™ Thanks for the feedback!" and posts the score straight into the agent's topic:

Rating Delivered to the Topic
⭐ User rated this conversation: ⭐⭐⭐⭐ (4/5)
  • One rating per ticket. A second attempt shows "You've already rated this conversation."
  • Ratings are tied to their ticket, so a customer who rates days later still scores the right conversation.
  • Only the customer who owns the ticket can rate it.
  • Rating is optional. If the customer blocked the bot or simply ignores the prompt, the ticket still closes normally.
πŸ“Š
Every close and every star feeds your Analytics Dashboard β€” average CSAT, rating distribution, open ticket count, median first reply time, and the per-agent leaderboard. Closing tickets is what makes those numbers real, so make /close a habit for your team.

One-Click Moderation

Spam and abuse happen. SupportBuddy integrates a robust, one-click client blocking system to protect your support team and keep channels clean.

Banning a Client

If a user is sending spam, sending advertisements, or being abusive, you can ban them from using the support bot instantly. Choose between two methods:

  • Inline Button Action: Every user details profile pinned at the top of a topic thread contains a button: [🚫 Ban User]. Simply tap it to ban them.
  • Group Command: Type the command /ban inside the user's forum topic thread. The bot will automatically parse their mapped ID, block them, and reply with confirmation: "🚫 User has been banned by: Agent Name".

Once banned, the user will be blocked from sending any further messages to the bot. If they attempt to send a message, the bot will reply with a strict warning: "🚫 You have been banned from using the bot."

Unbanning a Client

To restore a blocked customer's access, choose between these options:

  • Inline Button Action: Tap the updated inline button: [βœ… Unban User] in their thread.
  • Group Command: Type /unban inside their forum topic thread. The bot will unlock their account immediately, replying: "βœ… User has been unbanned by: Agent Name".

Announcements Broadcast

Need to announce a product update, a system downtime warning, or a promotional offer? SupportBuddy features a secure, bulk-broadcasting engine allowing bot owners to mass-message all their support users at once.

How to Broadcast a Message

  1. Send /start to your own support bot and tap πŸ“’ Broadcast.
  2. The bot will check your database, calculate your total active client base, and ask: "πŸ“’ How many users would you like to broadcast this message to?".
  3. Either tap πŸ“© Send to All Users, or send a number to target a subset (e.g. 500). The number must be lower than or equal to your total user count.
  4. Send the styled announcement message (can contain text, images, bold formats, and buttons).
  5. Confirm the trigger when prompted: "⚠️ Are you sure you want to broadcast this message?". Tap Yes.
Confirm Broadcast Announcement

Broadcast Summary Report

Once initiated, Weego Support Bot processes the broadcast in the background to avoid rate-limiting issues. Once completed, it dispatches a visual progress report to your admin chat:

Broadcast Summary Report
πŸ“Š Broadcast Summary
βœ…πŸ“© Message sent to 482 users.
❌ Error Count: 18.

Send /start to see bot buttons!

Automatic Blocked-User Cleanup

When a broadcast can't be delivered because a customer has blocked your bot or deleted their account, SupportBuddy marks them as unreachable and stops targeting them in future broadcasts. Temporary failures (rate limits, network hiccups) are counted as errors but leave the user eligible, so nobody is dropped by accident.

πŸ“Š
The Audience tab of your Analytics Dashboard shows exactly what share of your user base is still Reachable by broadcast β€” worth checking before you promise anyone a reach number.

Analytics Dashboard

SupportBuddy ships with a full analytics dashboard that opens as a Telegram Mini App β€” a real, interactive dashboard with charts, running inside Telegram itself. No browser login, no external tool, no separate account.

Opening the Dashboard

Send /start to your own support bot and tap πŸ“Š Statistics. The dashboard opens over your chat and matches your Telegram light/dark theme.

πŸ”’
Owner-only, and verified server-side. Telegram signs your identity when the Mini App opens, and SupportBuddy re-checks that signature against your bot's own token before returning a single number. Sharing or editing the link gives nobody else access to your data.

Every screen has a range switch at the top β€” 7d, 30d (default), or 90d β€” and four tabs: Overview, Audience, Tickets, and Team. Each chart also carries a data table underneath, so every figure is readable as plain numbers too.

Overview

Your daily pulse: unique users today, compared against the same weekday last week rather than yesterday, because support traffic has a strong weekly rhythm.

Metric What it tells you
Daily unique users People who sent at least one message, plus a % change vs. the same weekday a week ago.
Messages today Message volume today, with the total across the selected range.
Open tickets Conversations still awaiting resolution right now.
Median first reply How long a customer typically waits for the first human answer, across all agents.
CSAT Average star rating out of 5, plus how many ratings it's based on.
New vs returning First-time writers plotted against people coming back.
πŸ’‘
Median, not average. First reply time uses the median so that one ticket answered a week late doesn't quietly wreck an otherwise fast month.

Audience

Who your user base actually is, and how much of it you can still reach:

  • Total users reached β€” everyone who has ever written to your bot, plus how many are new in the selected range.
  • Audience composition β€” a breakdown of Active (last 30 days), Dormant, and Banned users.
  • New users per day β€” first-ever messages, day by day.
  • Reachable by broadcast β€” the percentage of your base that hasn't blocked the bot, and the raw blocked count.

Tickets

Workload and quality, in one screen:

  • Open tickets, plus how many opened and closed within the range.
  • Tickets opened per day β€” with closes shown alongside in the table.
  • When your users write β€” a heatmap by weekday and hour. Staff your agents against the strongest cells.
  • Top FAQs β€” your busiest auto-answers ranked by hits (range and all-time), headlined by your deflection rate: the share of all messages that got an instant answer.
  • Rating distribution β€” how your 1β˜… to 5β˜… ratings split, so a 4.2 average with a spike of 1β˜… reviews can't hide.

Team

How your agents are performing β€” built from replies actually sent inside your support group's topics:

  • Agent leaderboard β€” ranked by replies sent, each with their own first reply time, CSAT, and tickets handled.
  • First reply time β€” the daily median trend; gaps are days with no answered tickets.
⚠️
Numbers depend on /close. Tickets that are never closed stay counted as open forever, and never trigger a rating request β€” so CSAT, resolution counts, and open-ticket totals only reflect reality if your team closes finished conversations. See Tickets & Ratings.
πŸ”
Message content is never stored for analytics. SupportBuddy records only the shape of a message β€” when it arrived and what type it was β€” never the text your customers wrote.

Text Summary Fallback

If the Mini App dashboard is unavailable, the πŸ“Š Statistics button falls back to a plain text summary in chat:

Text Statistics Summary
πŸ“Š Bot Statistics

πŸ‘₯ Total users: 1,204

πŸ†• New users
  β€’ Today: 18
  β€’ Last 7 days: 96
  β€’ Last 30 days: 342

⚑ Active users
  β€’ Today: 57
  β€’ Last 7 days: 289

😴 Dormant (30d+): 411
🚫 Banned: 6

Owner Digest

Nobody opens a dashboard unprompted. The Owner Digest sends the numbers that matter β€” tickets, reply speed, ratings β€” straight into the chat you already read with @WeegoSupportBot, so you don't have to remember to go looking for them.

πŸ”
New: Pick your own cadence. The digest used to be locked to a weekly send. You can now choose Daily, Weekly, or Monthly β€” a five-minute-old bot and a year-old one want different rhythms.

Turning It On

  1. In @WeegoSupportBot, open your bot's Settings menu and tap πŸ“¬ Digest.
  2. Tap βšͺ Disabled (tap to turn on) to enable it β€” it becomes 🟒 Enabled (tap to turn off).
  3. Tap πŸ” Frequency to cycle through Daily β†’ Weekly β†’ Monthly.
  4. If you're on Weekly, a πŸ“… Day button appears so you can pick which day of the week it lands (daily and monthly digests don't need this β€” monthly always sends on the 1st).
  5. Tap πŸ•— Time to cycle through send-time presets. The digest follows the timezone already set in your Working Hours.
  6. Tap πŸ‘€ Preview at any point to see exactly what a delivered digest looks like, built from your bot's real numbers.
Example β€” Weekly Digest
πŸ“Š Your week on @YourSupportBot
28 Jul – 3 Aug

🎟 42 tickets opened (+18% on the previous week)
βœ… 37 closed Β· πŸ”΅ 5 still open
⚑ First reply, median 4m
⭐ 4.8β˜… average from 21 ratings
πŸ‘₯ 63 wrote in, 12 of them new
πŸ… Busiest agent: Agent Name, 22 replies

Sent every Sunday. Change or stop it in Settings.

How Each Cadence Behaves

  • Daily: reports the last 24 hours against the day before. Sent every day at your chosen time.
  • Weekly: reports the last 7 days against the 7 days before that. Sent on your chosen day and time.
  • Monthly: reports the last 30 days against the prior 30. Always sent on the 1st, at your chosen time.
🀫
Quiet periods are never sent. If a day, week, or month passes with zero tickets and zero messages, the automatic digest is skipped rather than reporting "0" and training you to ignore it. Preview always shows you a result, even a quiet one.

Turning It Off

Every delivered digest carries its own πŸ”• Turn off digest button, so you can stop it in one tap straight from the message β€” no need to dig back into Settings. You can always switch it back on later from the πŸ“¬ Digest menu.

Premium Plans

SupportBuddy is free to use β€” you can create a bot, link a group, and run a full helpdesk without paying anything. Premium removes the free plan's two limits: Weego branding shown to your customers, and the cap on FAQ auto-responses.

Free vs Premium

Feature Free Premium
Support bots you can create Unlimited Unlimited
Forum topic ticketing, moderation, broadcasts βœ… βœ…
Analytics dashboard, tickets & CSAT ratings βœ… βœ…
FAQ auto-responses Up to 5 Unlimited
"Created by" branding shown to your customers Shown Removed
🏷️
What the branding actually is: on the free plan, customers who start your bot also see a short note that the bot was created with Weego's SupportBuddy. Premium removes it, so your bot reads as entirely yours.

Pricing

Monthly
β‚Ή200 / $2
per month
  • Unlimited FAQ auto-responses
  • Zero Weego branding
  • Applies to every bot you own
Go Premium

How to Upgrade

  1. Open @WeegoSupportBot and send /premium, or tap πŸ’Ž Buy Premium (also available inside your own bot's menu).
  2. Tap Buy Now and choose Monthly or Yearly.
  3. Pick a payment method and complete the payment.

Payment Methods

  • πŸͺ™ Crypto β€” BTC, USDT, and other major coins via a hosted checkout.
  • πŸ”„ Binance P2P β€” USDT only. Pay to the Binance ID shown in the bot (tap to copy), then paste the Order ID from your success screen back into the chat to confirm.
  • πŸ’΅ UPI β€” India only.
⚑
Activation is automatic. Once payment is processed, the bot confirms your plan is active β€” no manual approval, no waiting on an admin. Each transaction ID can only be redeemed once.

Renewals & Expiry

SupportBuddy sends you a reminder before your plan expires, and a renewal notice with a one-tap renew button if it lapses. When a plan expires, your bots keep running β€” they simply return to free plan behaviour (branding returns, FAQs beyond the free limit stop matching).

Managing Your Bots

You can run as many support bots as you like from one account β€” one per brand, product, or language. Two different chats control them, and it's worth knowing which does what.

Where What it controls
@WeegoSupportBot
(the master bot)
Creating new bots, listing the bots you own, deleting bots, buying Premium.
Your own support bot
(as its owner)
Support group, welcome message, FAQs, broadcasts, statistics.

Listing Your Bots

In @WeegoSupportBot, tap πŸ“‚ My Bots or send /mybots. Pick a bot to see its details:

Bot Details
πŸ€– Bot Details:

πŸ†” Bot ID: 7563482769
πŸ“› Username: @YourSupportBot
πŸ’¬ Support Group ID: -1002345678901

Adding Another Bot

Tap πŸ€– Create Support Bot (or send /createbot) and paste a fresh token from @BotFather. A token that's already registered is rejected with "🚫 Bot is already added.", and an invalid token with "⚠️ Please enter a valid bot token to proceed." Each bot needs its own forum group.

Deleting / Dumping a Bot

Open πŸ“‚ My Bots βž” select the bot βž” πŸ—‘οΈ Delete/Dump Bot, then confirm with βœ… Yes, Delete.

⚠️
This is permanent. The support bot stops functioning, its webhook is removed, and all associated conversation and topic mappings are deleted. Your Telegram group and its message history survive, but the bot can no longer route replies into those old topics. Re-adding the same token later starts from a clean slate.

Getting Help

Send /help or /support in the master bot or any of your own bots to get πŸ“ž Contact Admin and πŸ“– Docs buttons. /doc or /docs opens this documentation directly inside Telegram.

Command Reference

Every command SupportBuddy understands, grouped by who runs it and where.

Master Bot β€” @WeegoSupportBot

Command What it does
/start Opens the main menu: Create Support Bot, My Bots, Help, Buy Premium.
/createbot Registers a new support bot from a BotFather token.
/mybots Lists every support bot you own.
/premium Shows premium plans and upgrade options.
/help Β· /support Contact the admin, with a link to these docs.
/doc Β· /docs Opens this documentation inside Telegram.

Your Own Support Bot β€” as the owner

Command What it does
/start Opens your control panel: Change Support Group, Set Welcome Message, Manage FAQs, Broadcast, Statistics.
/help Β· /support Contact the admin, with a link to these docs.
/doc Β· /docs Opens this documentation inside Telegram.

Your Own Support Bot β€” as a customer

Command What it does
/start Starts a support session and creates the customer's forum topic in your group.
/help Β· /support Shows support contact instructions.

Support Group β€” agents, inside a ticket topic

Command What it does
/close Closes the ticket in this topic and asks the customer to rate it 1-5. Their next message opens a new ticket.
/ban Bans the customer this topic belongs to.
/unban Lifts the ban on the customer this topic belongs to.
πŸ’‘
Group commands must be sent inside the customer's topic β€” that's how the bot knows which customer you mean. Sent in the group's General thread, they can't resolve a ticket.