Business chatbots on WhatsApp and Telegram: a setup guide

A chatbot on a messaging app answers customers where they already spend their time. Instead of filling in a web form or waiting on a phone line, a customer sends a message and gets a structured reply: an answer to a common question, a menu of options, or a short form collected step by step inside the chat.

The best use cases are repetitive and well defined. Order status lookups, appointment booking and reminders, opening hours and directions, delivery updates the customer asked for, simple product questions, collecting details before a support agent takes over, and short satisfaction surveys all work well. A bot handles these at any hour and frees your team for conversations that need judgement.

A bot is a poor fit when every conversation is unique, emotional or high stakes, such as complaints, refunds with exceptions, or medical and legal questions. In those cases the bot's job is to route the customer to a person quickly, not to pretend to be one.

Messaging apps are personal spaces, and both WhatsApp and Telegram are built around the idea that users decide who can reach them. A business chatbot should talk to people who started the conversation or clearly agreed to hear from you. Buying contact lists, scraping numbers or usernames from groups and sending unsolicited messages break the platforms' rules, damage your reputation and can get your number or bot blocked.

Collect opt-in openly. A checkbox at checkout saying that customers can receive order updates on WhatsApp, a chat link or QR code on your website, or the Start button a user presses in Telegram all record a clear choice. Tell people what kind of messages they will get and make stopping them easy, for example by honouring a simple stop keyword or an unsubscribe option in the bot's menu.

Keep proactive messages useful and expected. A delivery update that a customer asked for is welcome; a stream of promotions they never requested is not. Relevance matters far more than reach.

WhatsApp offers two routes for companies. The WhatsApp Business app is a free app for small businesses, run from a phone and linked devices. It includes a business profile, labels, a product catalog and simple automation such as greeting messages, away messages and quick replies. That covers basic needs, but it is not designed for custom chatbot logic.

For a real chatbot you use the WhatsApp Business Platform, Meta's API for businesses. You can connect directly through Meta's cloud-hosted API or through a Business Solution Provider, a partner that offers hosting, shared inboxes and often a visual bot builder. Setup generally involves a Meta business portfolio, a phone number your business controls and registers for the platform, a display name that Meta reviews, and a payment method for messaging where charges apply.

The platform distinguishes between conversations the customer starts and messages the business starts. When a customer writes to you, you can reply freely during a limited customer service window. Outside that window, business-initiated messages must use pre-approved templates and require the customer's prior opt-in. Meta's business messaging and commerce policies also limit what can be offered and how bots may be used, so read the current policies and follow WhatsApp's terms of use when you design your bot.

Telegram makes bots part of the app itself. You create one by opening a chat with BotFather, Telegram's official bot for managing bots, choosing a name and a username, and receiving an access token. That token lets your code, or a builder service, control the bot through Telegram's Bot API, either by regularly polling for new messages or by receiving them at a webhook on your server.

A Telegram bot cannot start a conversation with someone who has never opened it. People find your bot through a link, a QR code, your channel or search, and press Start; from then on the bot can reply and send the updates they signed up for. This design supports opt-in naturally, and it is a good reason to promote the bot wherever your audience already is.

Bots can show buttons under messages, custom keyboards and command menus, accept files and locations, and open Mini Apps, which are web interfaces that run inside Telegram for catalogs, booking forms and similar tasks. Telegram's business features also let you connect a bot that answers chats on behalf of a business account; availability can change, so check the current settings. Keep the bot token secret, and if it ever leaks, generate a new one through BotFather straight away. Telegram's terms of service and its rules for bot developers apply to every bot, so read and follow them.

Developers can write a bot against the official API using a library in their preferred programming language and host it on their own server. This gives full control over logic, data and integrations with your CRM, booking system or online shop. The trade-off is maintenance: you need hosting, monitoring and someone to fix things when an API changes.

No-code chatbot builders offer a visual editor where you arrange blocks for messages, buttons, conditions and data collection, then connect a WhatsApp number through a provider or paste in a Telegram bot token. They are quick to launch and often include a shared inbox for your team. Before committing, check how the builder stores customer data, whether you can export your flows and contacts, and whether it is an official partner for the channels you need.

Whichever route you choose, design the conversation before building it. Map the few tasks the bot must handle, write short and friendly messages, prefer buttons to free text where you can, and always include a way back to the main menu. If you add an AI model to answer open questions, limit it to your own verified information, tell users they are talking to an automated assistant, and test it for wrong or invented answers before launch.

Nothing frustrates customers faster than a bot that goes in circles. Every flow should include an obvious option to talk to a human, and the bot should also hand over on its own when it repeatedly fails to understand a request or when words such as complaint or refund appear.

A good handover passes the context along. The agent should see the conversation so far and any details the bot collected, so the customer does not have to repeat everything. Outside working hours, the bot should say plainly when a person will be available rather than leaving the chat in silence.

Review conversations regularly. Questions the bot could not answer show you what to add next, and handover reasons reveal where a flow is confusing. Treat the bot as a product that improves over time, not a one-off setup.

A chatbot collects personal data, so treat it with the same care as your website forms. Ask only for what each task needs, explain why you need it, and keep it no longer than necessary. Publish a privacy notice that covers chat data, and follow the data protection laws that apply where your customers live.

Never ask customers to send passwords, full card numbers or one-time codes in a chat, and say so in your bot's messages, which also makes scammers who imitate your brand easier to spot. Protect API tokens and builder accounts with strong passwords and two-step verification, give team members only the access they need, and remove access promptly when someone leaves.

Finally, be transparent. Your business profile or bot description should make clear who operates the bot, and users should always know how to stop messages and how to reach a person. Clear, honest automation builds the kind of trust that keeps customers coming back to the chat.

rStock is not affiliated with WhatsApp, Meta or Telegram. Whichever accounts or numbers you use for a business bot, follow the terms of use of each platform.