WhatsApp outreach
Partly liveWhatsApp is one click away. It isn't a channel yet.
Staff and donors already open WhatsApp from a donation record, a receipt, a campaign, or a checkout — every message pre-filled, every send manual. There's no broadcast list, no template library, and no delivery reporting inside DonorCARE today.
Not a cold start
- 9
- signed webhook events DonorCARE already fires
- 2
- sibling apps already wired: FormCARE, MyInvois
From a donation
Message a donor from their own donation record
Open a donation in the admin console and a WhatsApp link is right there, with the message text already written. Staff review it, hit send, and it opens in WhatsApp — nothing leaves DonorCARE on its own.
- Pre-filled message, one donor, one click
- Opens WhatsApp itself — DonorCARE never sends the message for you
On the receipt
Every receipt carries an enquiry link to your own number
A generated receipt includes a wa.me link to your organisation's own WhatsApp number, pre-filled with the receipt number, so a donor with a question can reach you in one tap.
- Links to your organisation's own WhatsApp number, not DonorCARE's
- Pre-filled with the receipt number for faster follow-up
Sharing
Campaigns and receipts both share to WhatsApp
A campaign page can be shared to WhatsApp from your admin console, and a donor can share their own receipt the same way from their dashboard. Both are share actions, not sends from DonorCARE.
- Campaign share button opens WhatsApp with the campaign link
- Donor-side receipt share works the same way
- Your public site also shows your organisation's WhatsApp number
What this isn't
No broadcast, no templates, no consent ledger, no reporting
Say the gap plainly: there is no WhatsApp campaign engine in DonorCARE, no way to send one message to many donors, no approved-template library, no record of who opted in, and no delivery or read reporting. Every WhatsApp touch today is one staff member, one conversation, one manual click.
Design intent — not built yet
How we intend the trigger, the consent, and the return trip to work
The interesting engineering isn't the sending — BizCARE CRM's Outreach module already sends. It's three questions that only DonorCARE can answer, sketched here as intent, not as shipped behaviour: what fires the message, where consent lives as the one authoritative record, and how a delivery result finds its way back. See /features/care-suite for the identity link this would ride on, and how it compares to the other CARE-app bridges.
- The trigger: DonorCARE already emits donation.completed and donor.tier_changed as signed webhooks. Those are exactly the shape of signal an outreach module consumes — a gift lands, a donor crosses a tier, and a follow-up fires from that event instead of a staff member opening WhatsApp by hand.
- The consent record: it would need to live in one place, not two — most likely the BizCARE CRM contact record Outreach already treats as ground truth, with DonorCARE's donor record referencing it rather than keeping a second, disagreeing copy.
- The pacing: any send still has to respect Meta's Cloud API rate limits, which is exactly what BizCARE CRM's Cloudflare Queues already do — DonorCARE would hand off the trigger, not reimplement the queue.
- The return trip: a delivered, read, or failed result has to land back against the donor record that raised the trigger in the first place — that write-back is the actual unbuilt bridge, more than the send itself.
What's live, what's via BizCARE CRM, what's not built
Click-to-chat is real and shipping. A true outreach channel — broadcast, consent, delivery reporting — is a different product, and it isn't DonorCARE's. Connecting a sibling CARE app isn't a new idea for this platform: DonorCARE already does it with FormCARE for forms and with BizCARE's own MyInvois API for e-invoicing. BizCARE CRM is the same pattern — and everything above about triggers, consent, and delivery write-back is how we intend to build it, not a description of something already running.
Click-to-chat, everywhere it belongs
One conversation at a time, always opened by a person, never sent by DonorCARE.
- From a donation record
- Staff open WhatsApp to one donor with the message pre-filled.
- On the receipt
- An enquiry link to your organisation's own WhatsApp number, pre-filled with the receipt number.
- Campaign and receipt sharing
- Staff share a campaign, and donors share their own receipt, to WhatsApp.
- On your public site
- Your organisation's WhatsApp number appears on your site footer and navigation.
A real outreach channel, in a sibling app — not connected yet
This is the next bridge we build. The broadcast channel itself is real and running today; what does not exist is the link from DonorCARE to it, which is why our own Integrations screen still lists BizCARE CRM as coming soon.
- Automated engagement workflows & follow-ups
- BizCARE CRM's own listed feature set — unified relationship management with 360° contact profiles, memorial and membership modules, and automated follow-ups, which is where WhatsApp Outreach lives.
- WhatsApp Business Cloud API
- Outreach sends direct through Meta's Cloud API, with Cloudflare Queues pacing the sends, and consent recorded on the CRM contact — none of it inside DonorCARE.
- A separate product, a separate sign-up
- BizCARE CRM is its own application at crm.bizcare.my. Signing up for it today doesn't connect it to your DonorCARE donor data.
- No bridge yet
- DonorCARE doesn't hand donor data to BizCARE CRM today, in either direction. Connecting the two is work still ahead, not a flag you can flip.
Not built, no date
- Broadcast lists and templates inside DonorCARE
- No plan to build a WhatsApp send engine inside DonorCARE itself while BizCARE CRM already owns that job.
- jomcare-messaging
- A shared WhatsApp and email service used elsewhere in the CARE suite. DonorCARE doesn't consume it yet.
Frequently asked questions
Can DonorCARE send a WhatsApp message to a donor automatically?
No. Every WhatsApp touch in DonorCARE opens a chat for a person to review and send themselves — donation follow-ups, receipt enquiries, and campaign or receipt shares all work this way. Nothing sends on its own.
Is this the same BizCARE that does our MyInvois e-invoicing?
No — different product, same family. The BizCARE Books API is DonorCARE's LHDN e-Invoicing (MyInvois) middleware and is live today. BizCARE CRM is a separate application with its own Outreach messaging module. DonorCARE using one does not mean it's connected to the other. See /features/care-suite for how the whole family of CARE-app bridges fits together.
Can I run WhatsApp broadcasts today if I sign up for BizCARE CRM too?
You'd be running two separate products with no data flowing between them. BizCARE CRM's Outreach module handles the broadcast, consent, and Cloud API sending on its own contact records — but DonorCARE doesn't hand it donor data today, which is also why our own Integrations screen lists BizCARE CRM as coming soon rather than connected.
Does DonorCARE track who has opted in to WhatsApp messages?
Not inside DonorCARE. Consent tracking for outreach messaging lives on the BizCARE CRM contact record, not on the DonorCARE donation or donor record.
Why not just build broadcast WhatsApp into DonorCARE directly?
It's a different job — pacing sends against Meta's Cloud API limits, managing approved templates, and holding a consent ledger is what BizCARE CRM's Outreach module already does. Duplicating it inside DonorCARE would mean maintaining two of the same thing.
Is the trigger-and-consent design above already built?
No. It's design intent — how we mean to wire donation.completed and donor.tier_changed into BizCARE CRM's Outreach module, with consent held once and a delivery result written back to the donor record. None of it exists today; the status ledger above is the accurate, current picture.
Use WhatsApp the way DonorCARE ships it today
Click-to-chat from donations, receipts, and campaign shares is available now. A broadcast channel is a BizCARE CRM conversation.