Duck Float
All posts
7 min read

A Telegram bot for customer support: a guide for business

Telegram stopped being "just a messenger" long ago: for many customers it's the main way to reach a business. Writing to a Telegram bot is faster than hunting for a form on a site or composing an email, so the channel has a very low barrier to reaching out. That's exactly why a Telegram bot for customer support is increasingly the primary channel for requests, not just an extra one — especially where the audience is already used to talking through Telegram. For a business that means more conversations — but only if the bot is set up right: it needs to receive messages, keep the history intact, and let the team see who answered what. In this guide we'll cover why a business needs such a bot, how to create one technically in a few minutes, and which pitfalls to account for before the channel is actually ready for a stream of requests.

Why a business needs a Telegram bot

  • Customers are already there. No need to teach them a new interface — they write in an app they already use every day.
  • Immediacy. Messages and replies arrive like a normal chat, with push notifications on both sides — the customer sees the reply right away, not "check your email in a few hours."
  • Low barrier. One tap and the conversation starts — no signups, no forms, no email confirmation.
  • A natural tone. In a chat people write shorter and more concretely than in a formal email: "the promo code isn't working" instead of three paragraphs of explanation. That speeds up understanding the problem.
  • Reachable from a phone. The operator doesn't need a separate app for email or a web form — Telegram is already open on the phone all day.

In practice, a Telegram bot for customer support works best for short requests that need a fast reaction: order status, a question about a plan, a problem logging into an account. Those are exactly the requests that tend to fall through the cracks in slower channels like email.

How to create a bot via BotFather

Technically the start takes a few minutes:

  • 1. Open @BotFather in Telegram and send the command to create a new bot.
  • 2. Set the bot's name and a unique username — ideally one that's instantly recognizable as tied to your brand.
  • 3. Get the token — the key your system uses to control the bot. Guard it as carefully as a password: whoever has the token can fully control the bot.
  • 4. Connect the token to your support tool — and the bot starts receiving requests.

It's worth configuring a few small things in BotFather before connecting it, since they're the first things a customer sees: a short description (/setdescription) explaining what the bot is for, an avatar (/setuserpic) with your company logo, and, optionally, a list of commands (/setcommands) if you plan quick actions like "order status."

On its own, a BotFather bot is just a "pipe." The token gives technical access to the channel, but for it to be useful, messages have to land somewhere, become manageable requests, and not get lost between operators.

What the customer sees after they start

For the customer the whole process looks simple: they find the bot by link or username, tap Start, and can immediately write their request in their own words — no menu with a dozen options required, though a short welcome message explaining what to write about doesn't hurt.

On the support side, that message needs to instantly turn into a clear request: tagged as coming from Telegram, carrying the customer's name from their profile, and letting the conversation continue in the same thread the customer keeps writing to. If the customer writes again a day later, it should be the same conversation — not a new, lost thread.

Which limits to account for

  • The bot can't message first. Telegram doesn't let a bot start a conversation — the customer has to write first. So give them an obvious reason and a link: on the site, in an email signature, on social media, or a QR code on packaging.
  • One bot, many requests. If all messages fall into one chat, they mix up fast between different customers. You need them split into separate conversations with statuses — otherwise, after a week of active use, figuring out who's waiting for what becomes impossible.
  • Who replies. Without a shared inbox it easily ends up with one person watching the bot, and the channel "vanishes" for customers whenever that person is off or on holiday.
  • Attachments matter too. Customers send photos, error screenshots, and voice messages in Telegram just as often as text. If the support system only shows text, part of the request's context gets lost.
  • The channel runs 24/7, the team doesn't. The bot accepts messages at any hour, even when no operator is online. That's fine if there's a queue with statuses, and painfully inconvenient if messages just sit in the chat unsorted.

Common scenarios for a Telegram bot

  • Order or request status. The simplest and most frequent ask — a quick check that doesn't need a long back-and-forth.
  • Questions about a plan or feature. The customer is hesitating before paying and wants a fast answer before they change their mind.
  • Access problems. "I can't log in" or "I'm not getting the code" is a typical case where reply speed directly affects whether the customer sticks around.
  • An unhappy customer. In a chat, a complaint often arrives shorter and more emotional than an email — and that's exactly where replying with a canned template instead of understanding the context backfires.

For scenarios like these, it helps when an AI prepares a reply draft based on your product description and the conversation history — more on that in the article on AI in customer support, and on where the AI gets context about your product in the article on the product description for AI support.

Don't keep Telegram separate

The most common mistake is setting up a bot as yet another isolated channel on top of email and site chat. Then you simply add one more place to miss a request: you have to check a separate app, remember it separately from the rest of the queue, and manually cross-check whether the same customer also emailed you. It's far better when Telegram flows into the same inbox as the rest of your channels, with the same statuses and tags. Why this matters — in the article on scattered requests.

Checklist before launch

  • The BotFather token is obtained and connected to your support system.
  • The bot's description, avatar, and, if needed, commands are set so it's clear to the customer where they're writing.
  • A link to the bot is on the site, in email signatures, or on social media — so the customer can write first.
  • Telegram messages land in the same inbox as your other channels, not a separate app.
  • The team has a clear owner for the request queue and a plan for when that person is unavailable.
  • A test message has been sent to the bot to verify the whole path from customer to operator reply.

How it works in Duck Float

In Duck Float connecting Telegram is literally pasting the BotFather token. From there every message becomes a ticket in the shared inbox alongside requests from the widget and the API, with history, statuses, and tags — and updates arrive instantly, with no page reloads. AI prepares a draft reply in the customer's language based on your product description and the conversation history: it appears right in the reply field, and the operator accepts it with Tab, edits it, or writes their own — nothing is sent automatically. You answer from one interface, and the customer gets the reply in the Telegram chat they already know. On all the channels together, see the article on one inbox. Everything is free during the beta; questions — message us through the widget on this site.

Try Duck Float with your team

Free while in beta. Setup takes a few minutes.

Create an account