Upload a CSV list and send a personalised WhatsApp campaign using an official Meta-approved template. 3650HQ runs on the real WhatsApp Business Cloud API, not a grey-market bulk sender, so you reach your list without risking your number.
Campaigns are WhatsApp-only: 3650HQ doesn't run email drip sequences. Every send uses an official Meta-approved template or Flow, so unlike unofficial bulk senders, campaigns respect WhatsApp's policies and don't put your number at risk. Each recipient costs credits from your shared wallet.
There are two ways to send WhatsApp messages to a list. One is the official Cloud API that Meta runs, where outbound messages outside an open conversation window use templates Meta has approved in advance. The other is a grey-market sender that drives a normal WhatsApp account through automation Meta did not sanction.
The second kind is cheaper, faster to start with, and advertised everywhere. It is also playing against a platform that is actively looking for exactly that pattern, and the penalty is not a warning. It is the number. For a business whose entire customer base knows it by that number, and whose order history lives in those conversations, losing it is not a setback, it is the business.
The broadcast list built into the WhatsApp Business app is the safe version of the same idea, and it caps out fast: a broadcast only reaches people who have saved your number, and the list limit means a real customer base is many manual sends. It is safe because it is small.
3650HQ sends through the official WhatsApp Business Cloud API using templates Meta has already approved, which is what makes reaching a list a normal thing to do rather than a risk you are absorbing.
Upload the list you already have. Recipients do not need to have saved your number for a template send to reach them, which is the ceiling a broadcast list runs into.
Columns in the CSV fill the variables in your template, so each message carries that customer's name, order or amount. It is a campaign that reads like a message rather than a mail-merge that reads like a campaign.
A campaign can send an approved template, or a published WhatsApp Flow, so a send can collect structured answers back rather than only delivering a message outward.
A campaign is not fire-and-forget. It can be paused partway and resumed, and every recipient carries its own status, so a partial failure is visible per person rather than as one number at the end.
Recipients are claimed atomically and sends are spaced with a delay, so a campaign cannot double-send to the same person and does not fire everything at once.
Each recipient draws credits from your shared workspace wallet. There is no campaign licence, no monthly minimum and no per-seat fee attached to sending, so the cost of a campaign is a function of its size and nothing else.
The practical consequence is that a small, well-targeted send to forty customers is genuinely cheap, rather than something you feel obliged to make large in order to justify a monthly fee. Balance is checked before the send goes to the provider, and a send that fails after being debited is refunded.
Campaigns are WhatsApp-only. 3650HQ does not run email drip sequences, and there are no multi-step nurture automations that branch on what a recipient did. A campaign is a deliberate send to a list you chose, not a machine that keeps messaging people on its own.
That is a narrower product than a marketing automation suite, and it is narrow on purpose. The ways to get a WhatsApp number banned mostly involve messaging people more than they expected, and an automation that decides on its own to send more messages is the wrong thing to hand a business whose number is its most valuable asset.
Not through 3650HQ. Every campaign uses the official WhatsApp Business Cloud API and Meta-approved message templates, the same compliant path Meta expects, not an unofficial bulk sender that risks a ban.
Yes. 3650HQ's bulk campaigns send from a CSV list of any size, well beyond WhatsApp's native 256-contact broadcast list limit, using approved templates.
Yes. Your CSV can include per-recipient variables (name, order number, anything you need) that get merged into the template or Flow.
Yes. Campaigns can be paused and resumed, and you can see delivery status per recipient at any point.
No. That is the limit a WhatsApp broadcast list runs into. Template sends through the official Cloud API reach your list whether or not each person has saved you as a contact.
Yes. A campaign can send a published WhatsApp Flow as well as an approved template, so a send can collect structured answers back rather than only delivering a message.
Every recipient carries its own status, so failures are visible per person rather than as a single number at the end. Recipients are claimed atomically, so a resumed campaign cannot double-send to someone it already reached.
No. Each recipient draws credits from your shared wallet and nothing else. There is no campaign licence, monthly minimum or per-seat charge, so a forty-person send costs what a forty-person send costs.
No. Campaigns are deliberate sends to a list you chose, not multi-step automations that keep messaging people based on their behaviour. Given that over-messaging is how numbers get banned, that restraint is deliberate.