Why WhatsApp groups are missing from almost every shared inbox

If you sell through dealers or distributors in India, a good deal of your business happens in WhatsApp groups. The order comes in a group. The complaint comes in a group. The photograph of the damaged carton comes in a group.

So when a company goes looking for a tool to put its WhatsApp on a proper footing — a shared inbox, several agents, somebody accountable for a reply — the groups are usually the first thing they ask about and the last thing they check. It is normally after the purchase that somebody notices the groups are not there.

Here is why, and it is not a gap in any particular vendor’s roadmap.

There are two completely different WhatsApps for business

A business number can be connected to software in one of two ways, and they are not two tiers of the same thing. They are different products with different capabilities.

The official Cloud API is Meta’s own Business Platform. You apply, Meta verifies the business, and you get programmatic access to send and receive. It is what gives you approved message templates, high broadcast volume and the verified badge. It is the respectable path, and for outbound marketing at volume it is the only path.

A linked device is the mechanism WhatsApp Web already uses. You open WhatsApp on the phone, go to Linked devices, and scan a QR code. The number you have been giving customers for years is connected in minutes, with no application, no verification queue and no per-message fee.

Only one of them carries groups

The Cloud API does not expose group messages. Not “not yet”, not “on a roadmap” — group conversations are simply not part of that surface. A product built purely on the official API therefore cannot show you a group, because nothing is being delivered to it.

This is why the feature grids look the way they do. A vendor on the Cloud API is not choosing to leave groups out. They have nothing to build with.

A linked-device connection sees what the phone sees, which includes every group the number is in. That is the entire explanation for why some tools have groups and most do not.

The trade is real, and it goes both ways

The linked-device path is not strictly better, and anyone telling you it is has something to sell.

It is an unofficial route: you are connecting a device, which is how WhatsApp Web works, but it is not a partnership and it carries no approval from Meta. There is no verified badge at the end of it. Most importantly, it is a terrible channel for bulk outbound — sending marketing to a list from a linked device is the single quickest way to lose the number.

The Cloud API is the opposite. It is slower to set up, it charges per conversation, and it puts you inside the twenty-four-hour window — after a day of customer silence you can only send a template Meta approved in advance. In exchange you get volume, templates, the badge and a sending path that is designed to survive a campaign.

What this means if you are choosing a tool

Work out which of the two jobs you actually have.

If customers message you and you reply — sales questions, support, order chasing, dealer groups — the conversational job is the one you have, and a linked-device connection does it today with no application to file.

If you need to send approved templates to a list of thousands, that is the broadcast job, and it needs the Cloud API.

Plenty of businesses have both. The thing to check before you buy is whether a product can run both at once, and whether it will stop you doing the dangerous thing: sending a campaign over the number that holds all your conversations.

How we handle it

Comsky Chat runs both. The QR connection is the conversational channel and carries groups as ordinary conversations — participant roster, system events, assignment, tickets, the lot. The Cloud API path exists for template broadcast.

And a campaign cannot be sent over a QR-connected number. That is enforced twice: once in the type system, so the code that sends a broadcast cannot be handed a linked-device number, and again as a database constraint, so no path around the first check helps. It is not a warning somebody can click past, because the cost of getting it wrong is the number every one of your customers has saved.

One honest caveat, since this is a post about things people find out after buying: connecting a Cloud API number with us is not self-serve yet. The broadcast engine, the sending brakes and template management are all built and running, but there is no connect screen — today we set the number up with you.

---

Comsky is not affiliated with, endorsed by or a partner of Meta. WhatsApp and WhatsApp Business are trademarks of Meta Platforms, Inc., used here descriptively.