Telegram or WhatsApp for a bot: the differences that decide it

Telegram and WhatsApp both let you run a bot, and the experience of building on them is so different that comparing them feature by feature misses the point. One is an open bot platform that has encouraged bots for over a decade. The other is a commercial business messaging product with approval processes, per-message pricing and rules about what a number may be for.

Neither is better. They suit different things, and the choice is usually settled by two questions: who your users are, and whether what you are building is a business talking to its customers or something else.

What we'll cover

• The structural difference
• Getting started, and what it costs
• Who is actually on each
• What you are allowed to build
• Building it with CodeWords
• Groups, which only one of them does
• Identity and what each knows about a user
• Interface capabilities
• Reaching people who have not messaged you
• Choosing, and running both
• Making it survive
• Limits worth knowing about
• What to decide first
• Frequently asked questions

The structural difference

Telegram treats bots as a feature of the platform. There is a documented bot API, you create a bot by messaging another bot, and you are sending messages within minutes. Nobody approves your content, there is no per-message charge, and a bot is an ordinary thing for a user to interact with.

WhatsApp treats business messaging as a product it sells. You register a number, you go through verification, messages outside a 24-hour window use templates Meta approves in advance, every message is priced by category and market, and the account carries a quality rating that governs how many people you may contact.

Those are not two implementations of the same idea. They are different propositions, and most of the practical differences below follow directly from this one.

Getting started, and what it costs

Telegram: create the bot, get a token, start sending. No business verification, no template approval, no per-message charge. The cost is your hosting and whatever model you use.

WhatsApp: a business portfolio, a number that is not on the consumer app, verification, template submission and approval, and per-message charges by category and market. From 1 October 2026 that includes service messages, which had been free, with an allowance of 1,000 delivered service messages per business number per month.

For a prototype or something personal, Telegram is a morning's work and WhatsApp is not. For a business with customers who already message it on WhatsApp, the friction is the cost of reaching people where they are.

Who is actually on each

This is usually the deciding factor and it is the one people research least.

WhatsApp is the default messaging app across much of Europe, Latin America, India, Africa and South East Asia, and it is where ordinary customers of ordinary businesses already are. A bakery's customers are on WhatsApp. They are not going to install Telegram to order a cake.

Telegram's user base skews towards communities, technical audiences, crypto, and specific countries where it is genuinely mainstream. If your users are a community rather than a customer base, that changes the answer.

The mistake to avoid is choosing the platform that is pleasant to build on and then discovering your customers are not there. Ask twenty of them what they use, which takes an afternoon and settles it.

What you are allowed to build

A real divergence, and one that has grown since early 2026.

WhatsApp's Business Solution Terms prohibit making AI technologies available through the platform where they are the primary functionality being offered, which rules out general-purpose assistants. ChatGPT ran on a WhatsApp number until 15 January 2026 and was withdrawn.

Telegram carries no equivalent restriction. An assistant-style bot is an ordinary thing to build and run there.

So the split is clean. A business automating its own customer conversations can do that on either. An assistant, a tool, a community utility, or anything where the bot itself is the product, belongs on Telegram.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder, keeping the logic separate from the channel it arrives on.
3. Authorize the connections to your systems and to whichever platform you are using.
4. Describe the exceptions, including the ones that differ by channel such as what happens when a WhatsApp window has closed.
5. Build the behaviour once and attach the channel to it, so adding the second platform later is configuration rather than a rewrite.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Groups, which only one of them does

Telegram bots work in groups. A bot can be added to a group, respond when addressed, and act as a shared utility for everybody in it. Groups can be large, and this is a genuine capability with no equivalent elsewhere.

WhatsApp's Business Platform does not do this. Messages go to one recipient at a time, and there is no supported way to operate a bot inside a group.

If what you are building is fundamentally about a group of people sharing something, that single difference decides the platform.

Identity and what each knows about a user

A difference that surfaces once you try to connect a conversation to a customer record.

On WhatsApp you get a phone number, which is usually already in your systems. That makes matching a conversation to an existing customer straightforward, and it is a large part of why the channel suits businesses.

On Telegram you get a user id and possibly a username, and the phone number is not shared with bots by default. Linking a Telegram conversation to a customer record means asking the person to identify themselves, which is an extra step and a point where people drop out.

Neither is a phone number you should treat as proof of identity, since numbers are recycled and devices are shared. For anything consequential, verify separately rather than trusting the channel.

Interface capabilities

Both support buttons, lists and media, and the details differ enough to affect design.

Telegram offers inline keyboards, commands discoverable through a menu, inline queries from other chats, and generally more freedom in how a bot presents itself. Files are large and formatting is flexible.

WhatsApp offers a more constrained set: reply buttons, list messages, and limits on how many options and how much text. The constraint is not only a limitation, since it pushes designs towards simplicity, which usually improves them.

The practical consequence is that a conversation designed for one needs adjusting for the other. The logic carries over; the presentation does not.

Reaching people who have not messaged you

The sharpest operational difference.

On WhatsApp, contacting somebody outside the 24-hour window after their last message requires a pre-approved template, and it costs money. This is restrictive, and it is also why the channel is not full of unsolicited messages.

On Telegram, a bot can message a user who has started a conversation with it, without templates or charges, though it cannot message people who have never interacted with it.

For proactive messaging at scale, WhatsApp is the more capable channel despite the friction, because reminders and updates are exactly what the template system exists for. For responsive bots, Telegram is simpler.

Choosing, and running both

Choose WhatsApp when you are a business talking to customers who already use it, when you need reliable proactive messaging, or when the alternative is customers installing something.

Choose Telegram when the bot itself is the product, when groups matter, when you are prototyping, or when your users are a community already there.

Run both when you genuinely have two audiences. Build the logic once, with the channel as a layer over it, and keep anything channel-specific at the edge. The cost of a second channel is then small; the cost of two separate implementations that drift apart is not.

Making it survive

Keep the logic independent of the channel, so a second one is configuration.

Track the 24-hour window state on WhatsApp, or scheduled messages will fail silently.

Keep templates current as your wording changes.

Re-read both platforms' terms periodically, since one of them has changed materially twice recently.

Test the presentation separately on each, since buttons and lists differ.

Limits worth knowing about

Your users' platform is not a preference you hold. Building where they are not is the expensive mistake.

Telegram's openness cuts both ways, since no approval also means less protection from what other bots do.

WhatsApp's costs scale with volume, and the free tiers are modest.

Assistant-style bots are not permitted on WhatsApp, whatever model sits behind them.

Feature parity is not the goal. A design that works on both is usually worse on both than two designs sharing the same logic.

What to decide first

Who your users are, established by asking twenty of them rather than by reasoning about market share. Everything else here follows from that answer, and it is the one people skip because it feels too simple.

Two habits make the difference. Keep the behaviour separate from the channel from the first day, since adding the second platform is then configuration rather than a rewrite. And check what you are permitted to build before you build it, because the assistant restriction on WhatsApp catches people who assumed the platforms were interchangeable.

Frequently asked questions

What is the main difference between Telegram and WhatsApp bots?

Telegram treats bots as an open platform feature with no approval and no per-message charge. WhatsApp sells business messaging, with verification, approved templates, per-message pricing and a quality rating.

Which is faster to get started on?

Telegram, by a wide margin. A working bot takes a morning. WhatsApp requires a business portfolio, a verified number and approved templates before any proactive message goes out.

Can I run a general-purpose AI assistant on either?

On Telegram, yes. On WhatsApp, no. The Business Solution Terms prohibit AI technologies where they are the primary functionality offered, which is why ChatGPT was withdrawn in January 2026.

Which platform should a local business use?

Almost always the one its customers already use, which in most of Europe, Latin America, India and South East Asia is WhatsApp. Customers will not install a second app to order from you.

Can bots work in group chats?

On Telegram, yes, and it is a genuine capability. WhatsApp's Business Platform sends to one recipient at a time with no supported way to operate inside a group.

Which is better for proactive messaging?

WhatsApp, despite the friction. The template system exists for reminders and updates and works reliably. Telegram bots can only message users who have already interacted with them.

How do the costs compare?

Telegram charges nothing per message. WhatsApp charges per message by category and market, including service messages since 1 October 2026, with a modest monthly allowance per business number.

Do the interfaces differ?

Yes. Telegram offers inline keyboards, command menus and inline queries. WhatsApp offers a more constrained set of reply buttons and lists. Logic carries over between them; presentation does not.

Can I run both?

Yes, and the way to do it is to build the behaviour once with the channel as a layer over it. Two separate implementations will drift apart.

How do I decide?

Ask twenty of your users what they use. That settles it faster and more reliably than any comparison of platform capabilities.

Related reading

• Why there is no assistant number on WhatsApp
• The four kinds of tool
• Buttons, lists and free text