WhatsApp for charities

WhatsApp for Charities: Rules, Costs and What Works (2026)

August 03, 20269 min read
Custom HTML/CSS/JavaScript

Most charities looking at WhatsApp get stuck in the same place. They can see supporters are on it, they can see messages get read, and then they hit a wall of Meta documentation written for retailers and give up. The gap is not enthusiasm. It is that nobody explains which WhatsApp product a charity needs, what it costs, and the one rule that governs everything you are allowed to send.

WhatsApp works for charities as a two-way supporter channel, not a broadcast list. UK charities need either the free WhatsApp Business App for small-scale, manual conversations, or the WhatsApp Business Platform (the API) for automated supporter journeys. The Platform is where fundraising happens at any scale, and its 24-hour messaging window is the constraint that shapes every journey you design.

Can charities use WhatsApp?

Yes. Meta permits charities and nonprofits on both WhatsApp Business products, and there is no charity-specific approval process. The practical decision is not whether you are allowed, it is which of the two products fits how you want to work. The free app suits a small team replying by hand. The Platform suits anything triggered, timed or automated.

The confusion comes from the naming. WhatsApp sells three things, and only two of them are relevant:

  • WhatsApp Messenger is the consumer app. Not for organisational use.

  • WhatsApp Business App is free, runs on a phone, and is designed for a person replying to messages themselves.

  • WhatsApp Business Platform (still widely called the API) has no app at all. You connect it to a system that sends and receives on your behalf.

If you want a message to fire when someone hits 50% of their fundraising target, you need the Platform. No amount of effort with the free app gets you there.

The five WhatsApps, and which one you need

"WhatsApp is WhatsApp" is the assumption that causes most of the trouble. There are five distinct products, and choosing the wrong one either limits what you can do or creates a compliance risk.

Custom HTML/CSS/JavaScript

Quick decision guide:

  • Personalised messages to individual participants at scale → Business API

  • One-way updates to a large following → Channels

  • Group chat for walking teams or regional groups → Communities

  • A handful of conversations, handled personally → Business App

  • Urgent reminders where reach must be guaranteed → SMS

What "Business API" actually means in practice

You cannot log in and start sending. The API is only reachable through a Business Solution Provider (BSP), a company certified by Meta to provide access. To go live you need a WhatsApp Business Account approved by Meta, pre-approved message templates for anything outbound, a clear opt-in process, and a platform managing the connection. Thread is a BSP, as are Cymba, Convrs and Social Sync.

This is the step that stalls most charities, because it looks like a technical project rather than a fundraising one.

The 24-hour rule, and why it matters

WhatsApp's 24-hour rule means you can only send free-form messages to someone within 24 hours of their last message to you. Outside that window you may only send pre-approved template messages. This single constraint determines how every charity supporter journey on WhatsApp has to be built.

This is the thing that catches teams out, and it is the reason a WhatsApp journey cannot be designed like an email journey.

Inside the 24-hour window, often called the customer service window, you can say anything: answer a question, have a conversation, send a personal thank-you. The moment that window closes, you are restricted to templates you submitted to Meta in advance and that Meta approved.

Two practical consequences:

  • Templates need planning, not improvisation. If you want to message supporters on event day, that template has to exist and be approved before event day. You cannot write it that morning.

  • Every reply from a supporter reopens the window. So journeys that invite a response are not just warmer, they are structurally more useful. A message that asks a genuine question buys you another 24 hours of free-form conversation.

That second point is where fundraising instinct and platform mechanics happen to agree. The messages that build relationships are the same ones that keep the channel open.

What SMS and WhatsApp actually cost

The WhatsApp Business App is free. The API is charged per message, and the price depends on what kind of message you send. SMS runs 3p to 8p per message segment.

WhatsApp changed how this works on 1 July 2025, moving from conversation-based pricing (a flat charge per 24-hour window) to per-mxessage pricing. Plenty of guidance still describes the old model. Here is what a UK charity actually pays now:

Custom HTML/CSS/JavaScript

Rates are set by Meta and billed in US dollars ($0.0667 and $0.0231 respectively). Sterling figures above use an exchange rate of 1.3, so they move with the currency. Marketing rose about 20% for the UK in July 2026, so treat all of this as current rather than permanent. This is also the cost before the costs of the platform you use to send add on their fee.

Three consequences worth designing around:

  • A marketing message costs roughly three times a utility one, 5.1p against 1.8p. Event-day logistics classified correctly as utility is meaningfully cheaper than the same content sent as marketing. Getting your template categories right is a real cost lever, not admin.

  • Conversation is free. Once a supporter messages you, everything you send back inside 24 hours costs nothing. The journey design that builds better relationships is also the cheaper one, which is great for relationship fundraisers stewarding supporters.

  • WhatsApp marketing sits at the low end of the SMS range, 5.1p against 3p to 8p. The difference is that WhatsApp replies are free and SMS replies are not, so WhatsApp wins on any journey where supporters actually respond.

For comparison at event scale: a 500-person event with five SMS touchpoints costs roughly £75 to £200 in message costs. Set that against the participants who set up a fundraising page because you nudged them.

Budget for two more things beyond messages: your provider's platform fee, and the setup work to connect messaging to the systems you already run.

Does Meta for Nonprofits make WhatsApp cheaper?

No. Meta for Nonprofits is a fundraising-tools programme, not a messaging discount. It gives UK charities the Donate button, Facebook and Instagram fundraisers, and approved donation links to their own website. None of it reduces what you pay to send WhatsApp messages.

This trips people up because the names sound related. If you are searching for Meta for Nonprofits hoping to find free or discounted WhatsApp messaging, it does not exist. Meta Verified, which covers WhatsApp accounts among others, is charged at its standard rate with no charity discount.

Consent: what changed, and what Meta still demands

The soft opt-in provisions in the Data (Use and Access) Act 2025 mean UK charities no longer always need explicit opt-in to send fundraising messages by SMS or WhatsApp. But Meta requires opt-in for every outbound WhatsApp API message regardless of what UK law permits, and that is enforced at platform level.

Those are two separate gates, and you have to clear. This is the part most guides get wrong, usually by only describing one of them.

Gate one: PECR and the charity soft opt-in

You can rely on soft opt-in only if all of these hold:

  • You got the number directly from the individual. Not from a list, not from a third party.

  • It was collected during sign-up to a fundraising or marketing product, event or similar.

  • The message is about your own similar products or services.

  • The first message offers a way to opt out, and every message after it makes unsubscribing easy.

Your privacy policy also has to permit it. If any condition fails, you are back to explicit opt-in: one clearly worded checkbox on the registration or donation form.

Gate two: Meta's own rule

WhatsApp Business API outbound messaging requires collected opt-in, and it is non-negotiable. You cannot infer it from an event sign-up unless your data policy and terms made the WhatsApp channel explicit. Clearing the PECR gate does not clear this one.

Channels and Communities are different: both are opt-in by nature, because people choose to follow or join.

What good consent looks like

Freely given rather than bundled into terms, specific about channel and content type, informed about who is contacting them and why, and active rather than pre-ticked. Keep mobile messaging consent separate from email consent. Channel-specific is cleaner and gives you more room later.

A workable registration-form line:

Yes, I'd like to receive support, fundraising tips and event updates from [Charity] by SMS.

Then store the consent record with date, source and exactly what was agreed. Mobile numbers are personal data under UK GDPR, so you also need a Data Processing Agreement with your platform provider.

This is practitioner guidance, not legal advice. Confirm your wording with your data protection lead before launch.

WhatsApp Channels are not the same thing

WhatsApp Channels is a one-way broadcast feature, closer to a public noticeboard than a conversation. Followers receive your updates and cannot reply, and you do not get their phone numbers. It is genuinely useful, but it is a publishing tool, not a fundraising channel.

Channels suit campaign updates, appeal milestones and supporter communities where reach matters more than dialogue. What Channels cannot do is carry a supporter journey, because there is no individual relationship underneath it and no data flowing back.

Most charities that succeed with WhatsApp end up using both: Channels for the many, the Platform for the individual.

Five uses that earn their place

The charities getting value from WhatsApp are not broadcasting more. They are using it for the moments where a supporter is already active and a reply is genuinely welcome.

  1. Registration welcome. The moment someone signs up for a challenge event, when their motivation is highest and they have questions.

  2. The page setup nudge. A large share of registered fundraisers never set up a fundraising page. A single well-timed message moves that number.

  3. Milestone celebration. Triggered when a fundraiser passes 25%, 50% or 80% of their target. These get replies, which is the point.

  4. Event day logistics. Where to go, what to bring, what happens if it rains. Genuinely useful, and read immediately.

  5. The thank-you. Not a receipt. A message that sounds like a person, sent when the experience is still fresh.

Notice how few of these are asks. WhatsApp punishes charities that treat it as another broadcast list, because supporters experience it as a personal space and leave when it stops feeling like one.

How SMS and WhatsApp work together

Where to start

If you are testing the idea, start with one journey on one campaign rather than a channel-wide rollout. A challenge event is the natural first candidate: fixed audience, clear milestones, an obvious reason to be in touch.

Thread is a Meta-certified BSP. We manage the WhatsApp Business API connection, handle template creation and approval, and build the event journeys, so your team works on the supporter experience rather than the plumbing.

See how Thread's messaging platform works

Custom HTML/CSS/JavaScript

Frequently asked questions

Custom HTML/CSS/JavaScript

Custom HTML/CSS/JAVASCRIPT
Back to Blog