WhatsApp and Telegram for Business: How Encrypted Messaging Is Replacing Traditional Customer Contact
The contact center quietly moved into a chat app
Phone support is not dying because people stopped talking. It is dying because they now type, and increasingly they type in the two apps that already hold their friends, their family group chat, and their delivery notifications. WhatsApp reports more than 3 billion monthly active users, a figure Mark Zuckerberg gave on Meta’s first-quarter 2025 earnings call. In June 2023 Meta announced that the free WhatsApp Business app had passed 200 million monthly active users, up fourfold from 50 million in 2020, and that 175 million people message a business account every day.
Telegram is the smaller but stranger story. It crossed 1 billion monthly active users in March 2025, announced by founder Pavel Durov, with roughly 500 million people opening it daily. For most of its first decade it was the messaging app businesses used informally and denied using formally, until Telegram Business launched on 31 March 2024, adding opening hours, quick replies, greeting and away messages, and connectable chatbots to any account with a Premium subscription.
The preference data is not subtle either. WhatsApp’s own 2026 Consumer Report – a survey of 11,056 consumers across 22 markets, published in September 2025 – found that 73.3 percent of them prefer messaging when they deal with a business. Treat that number the way you would treat any platform’s research about its own category: it tells you which direction the floor is tilting, not how fast anyone is walking. But the direction is not really in dispute anymore.
What is actually making businesses switch
Here is the part that gets buried under the privacy talk. Messaging wins at the contact center because it is cheaper and faster to answer, not because it is secret.
Benchmarks compiled from Gartner and Juniper Research figures put a WhatsApp service interaction at roughly $1.30 to $2.70, against $4.50 to $9.00 for phone support and $2.20 to $4.50 for email, with chatbot-handled conversations falling to cents. The same compilations place first response time at around 42 seconds with a bot and 3.2 minutes with a live agent, against roughly 4.2 hours for email. Those are vendor-adjacent numbers and should be read as directional, but the underlying mechanism is not mysterious: a text thread can be triaged, handed off, and answered between other tasks, while a phone call cannot.
That economics explains a migration that looks, from the outside, like a privacy movement. It is mostly a queue-management movement. The encryption is real on WhatsApp, and it is a genuine benefit for the customer, but no finance director is approving a channel switch because of a cipher.
Encryption is the pitch. It is usually not the mechanism.
This is where the marketing and the architecture part ways, and where I think most businesses repeating the “encrypted messaging” line are saying something they have not checked.
WhatsApp does encrypt one-to-one and group messages end-to-end by default, using the Signal protocol. That protects the conversation in transit and at rest from Meta. It does not protect it from the business on the other end: whoever operates the account reads every word, and once a support thread is exported into a CRM or a ticketing tool, it lives wherever that system lives. End-to-end encryption is a promise about the pipe, not about your filing cabinet.
Telegram is a sharper example. Its default “cloud chats” are encrypted between your device and Telegram’s servers – the same role TLS plays for a website – and the company holds the keys. True end-to-end encryption exists only in Secret Chats, which must be switched on manually for each individual contact, work only one-to-one, and are unavailable in groups and channels. Cryptographer Matthew Green made the case bluntly in “Telegram is not really an encrypted messaging app”: the vast majority of conversations, and every group, are probably visible to the servers.
Telegram’s defenders have a fair point. No practical break of MTProto 2.0 has been demonstrated, the company runs a bug bounty, and Secret Chats – where people use them – genuinely are end-to-end encrypted. The problem is not that Telegram is broken. It is that a business reading “encrypted” assumes the channel behaves like Signal, and it does not. If your compliance team signed off on Telegram because of that word, they signed off on the wrong thing.
WhatsApp and Telegram for business, side by side
The operational differences matter more than the encryption labels, and they point in opposite directions depending on your size.
| Channel | Who it reaches | Encryption by default | What it is genuinely good at | The catch |
|---|---|---|---|---|
| 3bn+ monthly users; strongest in Brazil, India, Indonesia, much of MENA and Europe | Yes, end-to-end (Signal protocol) | Support, order updates, conversational commerce at massive scale | Business Platform bills per delivered template; marketing templates blocked to US numbers since April 2025 | |
| Telegram | 1bn+ monthly users; deepest in Russia, Ukraine and parts of Asia | No – cloud chats are server-encrypted; Secret Chats are opt-in, 1:1 only | Broadcast channels, large groups, free and mature bot API | Cloud chats are readable by Telegram; server code is not open for audit |
| Phone | Everyone, with no app or data needed | Not applicable | Complex, emotional, high-stakes problems | Expensive per interaction, and nobody wants to wait on hold |
| Everyone, asynchronously | Not end-to-end | Records, attachments, escalation trails | Slow; open rates in the low double digits | |
| RCS | Roughly 80%+ of smartphones in major markets | No, not for business (A2P) messaging | Branded, interactive messages inside the native inbox | Requires device and carrier support, plus a verified brand profile |
The row worth staring at is Telegram’s. It is the better broadcast tool and the weaker private one, which is the opposite of how most people describe it.
The shift looks different depending on where your customers live
Channel preference is regional, not universal, and a strategy copied from a US blog will underperform in São Paulo. This is the part of the decision that no encryption claim can make for you.
Australia: privacy-sensitive services found the channel first
Australia adopted messaging for the least glamorous reason available: it is asynchronous. A tradesperson cannot answer the phone mid-job, and a customer does not want to repeat their address three times. That reasoning applies hardest in sectors that sell discretion, which is why directory-driven services tend to leave the phone line as a last resort and route first contact through a chat window. Listings like Perth escorts sit at the far end of that spectrum – the customer’s preference for a text thread over a recorded call is the entire product – but the same logic shows up in clinics, legal intake, and anything where the first question is sensitive.
The UK: the same tools, with heavier rules attached
British businesses moved to messaging slightly later and with more paperwork. The channel is now routine for appointment reminders, delivery windows and support triage, but consent and record-keeping obligations under UK data protection law mean teams cannot treat a chat thread the way they treat a personal one. Even consumer-facing directories where discretion is the selling point – Birmingham escorts listings among them – end up building the same infrastructure every other sector does: a business profile, an automated greeting, and a human who takes over when the bot runs out of road.
India: where mobile-first became messaging-first
India is the clearest leapfrog case in the world. WhatsApp is not one channel among many there; for a huge share of small businesses it is the customer relationship. Meta has cited tens of thousands of Indian businesses a month joining the Cloud API, and the platform’s support use cases – order status, returns, appointment confirmations – are concentrated in exactly these markets. The pattern holds across classified and directory services too, from Bangalore escorts listings to neighbourhood retailers: the app is where the customer already is, so the business follows, even when a phone number would technically work just as well.
Telegram Business is a feature, not a platform
There is a structural difference between the two apps that catches small teams out. WhatsApp has two products: a free app for a single phone, and the WhatsApp Business Platform (the API) for anything automated or at volume. The API is where the money and the complexity are – Meta moved to per-delivered-template pricing on 1 July 2025, new portfolios start capped at 250 unique customers per 24 hours, and a number can be registered to only one of the two products at a time.
Telegram Business is cheaper to start and shallower to scale. It is a mode inside your existing account, free for Premium subscribers at $4.99 a month, and it does presentation and first-touch well: opening hours, a start page, quick replies, automatic greetings. What it deliberately does not include is the actual selling. Catalogues, checkout, booking and delivery live in bots and Mini Apps, which are a separate build. Treat Telegram Business as a nicer front door, not as a commerce stack.
The regulatory ground is moving under both apps
If you are building a customer channel on WhatsApp in Europe, your roadmap is partly written in Brussels. Under Article 7 of the Digital Markets Act, Meta must let rival messaging services interoperate with WhatsApp, and the Commission’s interoperability requirements phase in by functionality – one-to-one messaging from March 2024, groups from September 2025, calls scheduled for 2027. The first third-party apps, BirdyChat and Haiket, began rolling out to European users in late 2025.
Competition enforcement is moving quickly in the same space. In June 2026 the European Commission imposed interim measures ordering Meta to restore free WhatsApp Business API access for rival AI assistants, after finding at first sight that Meta’s policy change – charging rivals effectively prohibitive fees – abused a dominant position. Whatever you think of the merits, the practical lesson for a business is that the terms of the channel can change by regulator’s order, not just by product update. A messaging strategy with no exit ramp is a fragile strategy.
What I would actually do
Pick the channel by where your customers already are, not by which app has the better privacy reputation. In Brazil, India, Indonesia and much of Europe, that is WhatsApp. In Russia, Ukraine, and parts of Central Asia and India’s tech communities, Telegram’s channels and bots are the stronger fit. In the US and Germany, where RCS now reaches the majority of modern phones and is on a steep adoption curve, the native inbox is the layer most customers will actually see.
Then be honest in your own copy. Say “messages are encrypted in transit” if that is true, and do not let a support page imply that a channel is confidential when your agents and your CRM can read every thread. Customers who discover the gap themselves rarely come back – and the businesses that lose the most from that gap are the ones selling discretion.
One genuine dilemma remains, and it is the one most teams get wrong. Do you consolidate everything into one app so your agents live in a single screen, or spread across channels to match each market’s default? Consolidation is cheaper and easier to supervise. Distribution reaches more people. I would consolidate first and expand only when a market’s volume justifies it, because a half-managed channel on four apps is worse than an excellent one on two.
Frequently asked questions
Is WhatsApp actually end-to-end encrypted for business chats?
The transport is. Messages between a customer and a business are encrypted end-to-end by default using the Signal protocol, so Meta cannot read them in transit. What that does not cover is your own access: your agents, your exports, and your CRM all see the content. End-to-end encryption says nothing about how you store what you receive.
Is Telegram end-to-end encrypted?
Only in Secret Chats, which must be enabled manually for each one-to-one conversation and cannot be used in groups or channels. Default cloud chats are encrypted between the client and Telegram’s servers, which hold the keys. For business messaging, assume Telegram’s servers can access the thread.
Can I use both WhatsApp and Telegram for the same support team?
Yes, and many teams do, but the tools are not symmetrical. WhatsApp’s Business Platform is built for ticketing, routing and automation; Telegram leans on bots and channels that you build or connect separately. Budget for two workflows, not one.
Which is better for reaching a lot of customers cheaply?
WhatsApp for one-to-one and support at scale, Telegram for broadcast channels and large groups. WhatsApp’s costs rise with volume because the Business Platform bills per delivered template; Telegram channels cost nothing to broadcast to, which is why they attract media and community operators despite the weaker privacy defaults.
What is replacing SMS for customer contact?
Mostly RCS in markets where it is supported, with SMS as the automatic fallback underneath it. RCS puts branding, images and buttons inside the native messaging app and reports far higher click-through rates than SMS, but it is not end-to-end encrypted for business messaging, and it needs a supported device and a data connection. SMS remains the universal floor.
Do customers really prefer messaging to phone calls?
Broadly yes, and consistently in the platform research. WhatsApp’s 2026 Consumer Report, based on 11,056 respondents across 22 markets in September 2025, found 73.3 percent prefer messaging when contacting a business. Independent survey work has pointed the same way for years, though preference and behaviour still diverge for urgent or complex problems.
How this article was put together
I based the usage and business-messaging figures on Meta’s own earnings-call and product announcements, Telegram’s founder and product blog, and WhatsApp’s published consumer research, and I checked the encryption claims against independent cryptographers rather than vendor marketing. Cost and response-time benchmarks are drawn from industry compilations of Gartner and Juniper Research data and should be treated as directional, not audited. The EU positions were read from the Commission’s own Digital Markets Act developer portal and its June 2026 interim-measures announcement. All figures were verified in September 2026; WhatsApp’s user numbers and the DMA interoperability timeline in particular will need rechecking as both move.
