WhatsApp Broadcast vs. Newsletter vs. Group — Which Path for Which Use Case? (with Coexistence)

SendSeven Team, Editorial Team

Four WhatsApp paths for businesses, plus Coexistence as the bridge: broadcast inside the app, newsletter via Cloud API, WhatsApp group and WhatsApp Channels. With limits, pricing, UK GDPR reality and a use-case matrix for UK SMBs.

1. The four paths at a glance

Most people who say "WhatsApp newsletter" mean one specific dispatch path. In fact there are four — plus one bridging feature. Each path has its own mechanics, its own scale ceiling and its own UK GDPR / PECR profile.

The table makes two things visible. First: reach and privacy stand in hard inversion. If you want private communication, you cap at 256. If you want unlimited scale, you either pay or give up dialogue. Second: there is no single right answer. The right path depends on the use case — and with Coexistence you don't have to pick a single one. More on that in section 6.

Background on the underlying terms in the glossary: WhatsApp broadcast, WhatsApp Cloud API and WhatsApp Business Platform.

2. Path 1: Broadcast inside the Personal or Business App

The oldest and simplest path. A broadcast list in the WhatsApp app — Personal or Business — is a saved address-book set that you send a message to. Each recipient gets it as a private chat and cannot see the other recipients.

Technical limits

• Max. 256 recipients per list (per the official WhatsApp documentation)¹.
• Recipients must have your phone number saved in their address book — otherwise the message will not arrive.
• No templates, no Meta review process, no central platform.
• No analytics. No open rates. Just delivery and read receipts per individual chat.
• No multi-user access. Whoever holds the phone sends.

Where this path works

Three profiles where 256 recipients is enough and the personal tone is an advantage:

• A bakery with a loyal customer base — daily specials, opening exceptions, custom-order pickups. The list grows by word of mouth.
• A vet practice — vaccination reminders, seasonal alerts for ticks and fleas, weekend out-of-hours. Highly relevant, small audience.
• A hair salon — last-minute openings, promotions, new treatments. A list of 100–200 regulars is realistic.

Where this path breaks down

The moment you grow beyond 256 recipients, you start doing manual work. Multiple lists in parallel, deduplication, ordering inside your head — none of that scales. And if the owner loses the phone, the list is gone.

Second problem: no Data Processing Agreement is possible. Using the Business App for a customer list means syncing the device-local address book with Meta. The Information Commissioner's Office (ICO) treats this consistently as non-compliant with UK GDPR and PECR for commercial communication with end customers, because Meta accesses third-party data (the customers') without those customers consenting to the transfer.⁵

Third: broad-cast marketing also violates Meta's Business Messaging Policy. Sending systematic promotional messages from the personal or business App risks number suspension. The Personal App is officially not approved for marketing.⁶

Bottom line for Path 1: a solid option for personal customer communication with a small, curated audience. Not the right lever for marketing at meaningful reach.

3. Path 2: Newsletter via WhatsApp Cloud API

The official path for businesses. The Cloud API is the Meta-hosted WhatsApp interface that lets you send templates to lists — with documented opt-in, analytics, multi-user access and a platform like SendSeven layered between you and Meta.

Technical logic

Two message types exist:

• Templates — message formats pre-approved by Meta, which you can send outside an existing 24-hour service window. Categorised as Marketing, Utility and Authentication.
• Free-form messages — free-text replies inside the 24-hour window following the customer's last message. These were free until 30 September 2026; since 1 October 2026 Meta charges them at the utility rate, with the first 1,000 per business phone number and month free.

Pricing since 1 July 2025

Meta retired the conversation-based model. Each delivered template message is now billed individually. The UK list prices (Meta rate card in effect since 1 October 2026)²:

Since 1 October 2026 Meta has charged €0.0526 per marketing template to UK numbers, up from €0.0438. All figures in this article come from Meta's EUR rate card.

A free-entry-point effect applies on top. When a customer messages you through a Click-to-WhatsApp ad or a Facebook Page call-to-action button and you reply within 24 hours, Meta charges nothing for your messages to that contact for 72 hours from your reply. Only Meta's fee is waived; SendSeven still bills these messages through your plan. More on this in our WhatsApp Business API Costs 2026 article.

No hard recipient cap, but dynamic throttles

In theory you can send to an unlimited number of recipients via the Cloud API. In practice, two throttles apply. Phone Number Quality Rating: every WhatsApp number has a reputation score (Green, Yellow, Red), shaped by block rates and complaints. Messaging Limit: business portfolios start at 250 unique recipients they can message proactively per rolling 24 hours (since October 2025 the limit applies per portfolio, not per individual number) and scale through 2,000, 10,000 and 100,000 to unlimited — provided quality and 24-h volume support it.⁷

Where this path works

• UK e-commerce store with 5,000+ newsletter subscribers — weekly drops, seasonal campaigns, abandoned-cart flows.
• Travel agency — last-minute offers, segmented by travel style and region.
• Mail-order pharmacy — re-order reminders for chronic medication, seasonal allergy and cold updates.

What Path 2 requires

• A verified Meta Business Account
• A WhatsApp Business number (free of Personal-App lock — or running in parallel via Coexistence)
• A platform like SendSeven sitting on top of the Cloud API to provide inbox, templates, campaigns, multi-user and DPA
• Documented opt-in per contact

Bottom line for Path 2: the standard solution for marketing at scale with a growth runway. Costs money per message — and in return is GDPR-capable, scalable and measurable.

For the full walkthrough of Path 2, from opt-in setup and template creation to sending cadence and cost, see our WhatsApp newsletter setup guide.

4. Path 3: WhatsApp group

The group is enormously widespread in the UK — sports clubs, school classes, parent chats. That familiarity is exactly what makes it tricky as a commercial channel.

Technical limits

• Max. 1,024 participants per group. The limit was raised from 256 to 512 in May 2022 and to 1,024 in October 2022 (phased rollout into 2023).³
• Communities (umbrella structure since November 2022) bundle up to 50 sub-groups under one announcement group with up to 5,000 members. Individual sub-groups remain capped at 1,024 participants.
• Every participant sees the phone numbers of every other participant. This is not a setting, it is product behaviour.
• Groups run from the app cannot be automated. Meta's Groups API only covers small groups of up to eight participants on Cloud API numbers with an Official Business Account, not Business App or Coexistence numbers. SendSeven has no group chat.

Where groups do work

Wherever the participants already know each other and the chat between them is part of the value:

• Sports club — training cancellations, match results, last-minute changes.
• School-class parents' committee — dates, polls, school-trip logistics.
• Dog-training course — fixed weekly cohort, training photos, homework.

Where groups do not work

In SMB deployments with end customers, groups are almost always the wrong tool. Three reasons:

First, UK GDPR. The moment you invite customers who do not know each other into one group, you disclose their phone numbers to every other participant. That is personal-data sharing without consent. The ICO has been consistent in treating that as non-compliant for consumer marketing.

Second, noise. Once the group grows it becomes unreadable. Mute, leave, side conflicts between participants — all of which reflect on your brand.

Third, no automation. In a group run from the app you cannot use templates or any Business API workflows. No platform sits between you and the participants.

Bottom line for Path 3: groups are a community tool, not a marketing tool. Businesses trying to reach customers are better served by newsletters or Channels.

5. Path 4: WhatsApp Channels

The newest path. WhatsApp Channels rolled out globally on 13 September 2023 in more than 150 countries⁴. The mechanic is deliberately one-way: the admin posts, followers cannot reply.

Technical specifics

• Unlimited follower count.
• One-way communication. Followers can react with emoji or vote in polls (polls since 17 January 2024).
• Phone numbers are not exposed by default. Followers cannot see the admin's number; admins do not see followers' numbers unless the follower is already saved in the admin's address book. Co-admins see each other's numbers.
• Channels are publicly discoverable via the channel directory, filterable by country and language.
• Updates are stored on Meta's servers for a limited time (around 30 days per third-party reporting) and then auto-deleted.
• The product is published privacy-by-design with its own Privacy Policy for the EEA (also referenced by ICO guidance for UK).

Where Channels work

• Local UK newspaper — daily headlines, breaking-news alerts, weather warnings.
• Sports club as an organisation (not as a training group) — match announcements, highlights, ticket drops.
• Freelance coach or influencer — content drops, event reminders, behind-the-scenes content without obligation to reply.
• Local council or municipality — resident updates, events, alerts.

Where Channels reach their limits

The one-way design is both strength and weakness. If you need a dialogue, transactional intake or individualised service, you are on the wrong path. Channels are broadcast pure — not a service channel.

The data-protection picture is more favourable than groups because follower data and phone numbers are not exposed. Some UK GDPR specifics around Channels — specifically how content storage by Meta fits into DPA obligations — are still being clarified by the ICO. Recommendation: deploy productively, monitor ICO guidance in your sector.

Bottom line for Path 4: ideal for high-reach one-to-many communication without dialogue. Pairs well with other paths — e.g. Channels for brand reach, newsletter via Cloud API for transactional contact.

6. Coexistence: two worlds on one number

Before Coexistence, the choice between App and Cloud API was a one-way street: if you wanted to migrate to the API, you had to remove your existing WhatsApp number from the App. Chat history was gone. Established workflows too.

With WhatsApp Coexistence, Meta has opened that one-way street. The feature launched in February 2025, initially without the EEA and the United Kingdom; businesses there have been able to use it since October 2025, and SendSeven activated its own implementation on 11 May 2026.⁸

What Coexistence does

• The App and the Cloud API run on the same phone number in parallel. The App stays on the owner's phone. The team works in parallel through the Cloud API in a shared inbox.
• Bidirectional real-time sync. A reply from the App appears in the team inbox; a reply from the inbox appears in the App.
• Up to six months of chat history can be backfilled into the Cloud API on activation. Plus two weeks of media history.
• App messages remain free. Only Cloud API templates are charged at the Meta rate card.
• WhatsApp's four-device limit still applies.

What Coexistence does not do

• Groups are not synced. Only 1:1 chats are inside the sync. If you have group workflows, they remain on the App only.
• The backfill decision (import chat history yes/no) is not reversible once made. The Coexistence link itself can be unlinked later — the Meta WABA tied to the number, however, persists.

Where Coexistence works

• Trades business with five team members — the owner has been chatting with regulars over WhatsApp from their phone for years. The App stays. Through the Cloud API, the office now gains a shared inbox where a service team member can triage enquiries, send template appointment confirmations and run campaigns — without the owner giving up their phone.
• Pharmacy — the owner keeps personal chats with chronic-condition customers. The pharmacy assistant works re-order reminders and seasonal templates through the API side.
• Veterinary practice — emergency chats stay in the App, vaccination and seasonal letters go out automatically as utility templates via the Cloud API.
• Recruiting — recruiters keep confidential direct messages in the App, the team coordinates routine templates through the shared inbox.

SendSeven implements Coexistence inside the platform's onboarding. Owners continue their 1:1 chats over the phone, the team works in parallel via the API in the shared inbox. Coexistence naturally requires the app on the phone. Without the app, the full Cloud API is the more direct route. For deeper background see our pillar article: WhatsApp Coexistence — the 2026 Guide. Glossary entry: WhatsApp Coexistence.

7. Use-case matrix: which path for which scenario?

Six typical UK SMB scenarios. Each row shows the primary path that fits, and a note where another path can usefully complement it.

The most important takeaway: there is no winner and no loser. There is a use case — and a path that fits it. Coexistence is not a separate path but a bridge between Path 1 and Path 2.

8. UK GDPR reality per path

WhatsApp is not generally banned in the UK — but every path has its own data-protection profile. Three dimensions decide: opt-in obligation, DPA availability under UK GDPR Art. 28 and phone-number exposure to third parties.

A clarification that often gets lost: the UK Information Commissioner's Office does not ban WhatsApp for businesses; it expects PECR-compliant opt-in, a documented lawful basis under UK GDPR, a Data Processing Agreement with your provider, and clear retention and sub-processor documentation. Private companies and councils may use WhatsApp Business if they meet these obligations.⁹ More on practical implementation in the glossary: GDPR-Compliant Messaging.

Working with a tech provider on the Cloud API side, you should specifically check: does the provider host data in the EU/EEA? Is there a signed DPA under UK GDPR Art. 28 (and EU GDPR equivalents)? Are sub-processors documented openly? SendSeven hosts the entire platform inside the EU, runs AI components in the EU and ships the DPA at no extra cost — more on the WhatsApp channel page.

9. Setup path: from App-only to hybrid (App + API in parallel)

If you are running the WhatsApp Business App today and want to add Cloud API access via Coexistence, you go through six steps. Order matters because some steps are not reversible.

1. Disable two-factor authentication in the Business App. Otherwise Coexistence cannot transfer the number into the Cloud API setup. Re-enable after onboarding.
2. Verify your Meta Business Account. In business.facebook.com — company name, address, website, company number. Verification takes hours to days depending on completeness.
3. Start the Coexistence activation through a Cloud API tech provider. At SendSeven this runs as a guided onboarding wizard with clear explanations of what each step does.
4. Make the backfill decision. Up to six months of chat history can be imported into the shared inbox. This decision is not reversible once confirmed. Choose backfill, and all 1:1 chats appear in the team inbox immediately. Decline, and you start clean.
5. Invite the team, set roles. Who can build templates, who can only reply, who sees reports. At SendSeven this is included — no per-seat add-on.
6. Submit and test the first template. A simple appointment confirmation as a utility template is typically approved in minutes to hours. Marketing templates usually take longer.

For an in-depth step-by-step with screenshots and a list of pitfalls, see our migration spoke: WhatsApp Business App to API: the Coexistence Migration Guide.

FAQ

Can I run broadcast and newsletter on the same WhatsApp number in parallel?

Yes, with Coexistence, which Meta also offers to businesses in the EEA and the UK. Through SendSeven it has been live in production since 11 May 2026. The App stays on the owner's phone for personal 1:1 chats, the Cloud API runs on the same number in parallel for templates, campaigns and multi-user inbox. Bidirectional real-time sync for 1:1 chats. Groups are not synced.

What is the maximum number of recipients in a WhatsApp broadcast list?

256 per list. That is a hard cap in the WhatsApp App — both the Personal App and the Business App. Running multiple lists in parallel is technically possible but operationally heavy (deduplication, ordering, no analytics). Anything beyond 256 recipients reliably requires the Cloud API.

What does a WhatsApp newsletter cost per message in the UK?

Since 1 October 2026 Meta has charged €0.0526 per delivered marketing-template message to a UK number. Utility and authentication templates cost €0.0182. Service replies inside the 24-hour window were free until 30 September 2026. Since 1 October 2026 Meta charges them at the utility rate, with the first 1,000 per business phone number and month free. If a customer messages you through a Click-to-WhatsApp ad or a Facebook Page call-to-action button and you reply within 24 hours, Meta charges nothing for your messages to that contact for 72 hours from your reply.

Is WhatsApp Coexistence available in the United Kingdom?

Yes. Meta has opened Coexistence to businesses in the EEA and the United Kingdom. SendSeven activated its own implementation on 11 May 2026. Activation runs through a verified Meta Business Account and can be deployed in production.

Will my WhatsApp groups be brought across by Coexistence?

No. Coexistence syncs 1:1 chats only. Groups stay in the App and are not mirrored into the Cloud API inbox. If you have group workflows, they remain on the owner's phone. Meta's Groups API does not work on Coexistence numbers either.

Which WhatsApp path is UK GDPR compliant?

Newsletter via the Cloud API is the only path that meets the standard UK GDPR obligations for commercial consumer communication in all three dimensions: documented PECR opt-in, DPA with the tech provider under Art. 28, no phone-number exposure to third parties. Coexistence inherits these properties on its Cloud API side. Broadcast in the App is not approved for marketing. Groups expose numbers to third parties and are practically non-compliant for consumer marketing. Channels are structurally favourable but ICO sector-specific guidance is still developing.

What is the difference between WhatsApp broadcast and WhatsApp Channels?

A broadcast is a list inside your address book to which you send a message. Recipients receive it as a private chat and can reply. Maximum 256 recipients. Channels, by contrast, are a public one-to-many channel. Followers cannot reply, only react via emoji or polls. Phone numbers are not exposed in either direction. Channels have no recipient cap and are publicly discoverable in the channel directory.

Can I post into a group via the WhatsApp Cloud API?

Only in a narrow case. Meta's Groups API lets Cloud API numbers with an Official Business Account run small groups of up to eight participants, joined by invite link, with text, media and template messages but no interactive messages, billed per message. It is not available for Business App or Coexistence numbers, and SendSeven has no group chat. If you want to reach 1,000 recipients, the right choice is Channels (one-way, unlimited) or newsletter via Cloud API (bidirectional, paid per template).

Sources

1. Meta / WhatsApp Help: Broadcast lists, maximum 256 recipients. faq.whatsapp.com/459807961386643
2. Meta Developers: WhatsApp Business Platform Pricing, rate card in effect since 1 October 2026 (EUR). developers.facebook.com/docs/whatsapp/pricing
3. Meta announcement on group-size increase to 1,024 participants, 2023. blog.whatsapp.com
4. Meta announcement: Channels Global Launch, 13 September 2023. about.fb.com/news/2023/09/whatsapp-channels-global-launch
5. Meta Business Messaging Policy — rules on bulk send and address-book sync. business.whatsapp.com/policy
6. WhatsApp Business Terms of Service — ban on marketing bulk send via the Personal App. whatsapp.com/legal/business-terms
7. Meta Developers: Messaging Limits and Quality Rating. developers.facebook.com/docs/whatsapp/messaging-limits
8. Meta Developers: Embedded Signup Onboarding Business App Users (Coexistence documentation). developers.facebook.com
9. ICO Direct Marketing and PECR guidance — UK position on consent for electronic marketing. ico.org.uk
10. WhatsApp Channels Privacy Policy for the EEA (referenced by UK guidance). whatsapp.com/legal/channels-privacy-policy-eea