Skip to main content
Yes. WhatsAble sends Meta-approved WhatsApp template broadcasts to a CSV (or audience) list from your connected WhatsApp Business number. Broadcasting is the main job of the Bulk Message plan and is also on Pro and Agency. Use this page when you need the operator path: prepare the CSV, test, choose a delivery mode, launch or schedule, and read basic delivery stats. Broadcasting is not the same as creating templates, and it is not a native multi-day drip builder. Templates are a separate topic; day-0 / day-3 / day-6 sequences run only through Make, Zapier, or n8n.

​
Prerequisites

  • WhatsAble account on Bulk Message, Pro, or Agency — sign in at dashboard.whatsable.app/signin.
  • WhatsApp Business number connected through WhatsAble (Embedded Signup / Coexistence supported — keep the WhatsApp Business app; do not uninstall it after connect).
  • At least one Meta-approved message template for that number. Only super-admins create templates; Meta must approve before the template appears in send flows. Editing an existing template is not supported — recreate and resubmit if you need changes.
  • Meta payment method on the WhatsApp / Business Manager side. Template sends fail when Meta has no billing method for the number.
  • Active plan (or trial) with enough unique-contact headroom for the recipient list. WhatsAble bills unique contacts per month; Meta bills delivery fees separately at Meta rates (WhatsAble 0% markup).
  • CSV ready (or list you will export): phone numbers with country code. Exact column rules are below.
How-to video (EN): How to broadcast. Broadcasting and templates are different topics — do not swap the videos.

​
Operator path — send a template broadcast

Open Broadcasts in the WhatsAble console and follow the steps below. Menu labels can vary by workspace; use the Broadcasts area you see in the console.

​
1. Open Broadcasts and pick an approved template

In the WhatsAble console, open Broadcasts. Start a new broadcast and select a Meta-approved template only. Pending templates will not send reliably; Graph “unsupported post request” on test send is often an unapproved template, not a disconnected number. If the template uses body variables ({{1}}, {{2}}, …), you will map them from CSV columns in the next step.

​
2. Prepare the recipient CSV

WhatsAble expects a CSV whose phone column is named exactly phone_number. Include the country code. Support troubleshooting locks this name; if the broadcast fails after upload, check formatting first. Required Optional (when the template needs them) Example:
After you select a template in the console, download the template CSV from the broadcast UI when available — that file matches the variables Meta approved for that template. Upload behavior:
  • Duplicate phone numbers in the same CSV are deduplicated (kept once).
  • Re-uploading recipients for the same broadcast replaces the previous list.
  • The system returns unique recipient count and an estimated cost of broadcast (Meta-side country pricing) before you finalize.
Use the phone_number header above — do not substitute alternate names such as camelCase phoneNumber.

​
3. Send a test message

Before the full list, send a test to a number you control. Confirm the template renders (variables, media, buttons). Fix CSV or template issues here — not after a 10k launch.

​
4. Upload recipients and review counts

Upload the CSV. Confirm:
  • Unique numbers match expectations (duplicates dropped).
  • Estimated cost looks sane for the countries on the list.
  • Unique count fits your WhatsAble unique-contact tier (or accept overage — see plans page).
Some console flows let you scope recipients with labels when that control is present. Use the labels UI in your console when available.

​
5. Choose delivery mode

WhatsAble paces outbound template traffic with three delivery modes (API/console values): Do not invent a WhatsAble numeric RPM or “messages per second” product limit on this page. Meta messaging tier caps (business-initiated conversations per 24 hours) still apply — see rate-limits docs when published and Meta’s own tier rules.

​
6. Launch now or schedule

  • Send / launch is available on Bulk Message, Pro, and Agency.
  • Scheduled broadcasts (future send time) are available on Bulk Message, Pro, and Agency. Scheduling is not the same as a native drip delay chain.
Schedule strings on the finalize path use DD/MM/YYYY HH:mm. Timezone resolution can follow the caller’s environment — always verify the resulting time in the console after you save.

​
7. Monitor basic delivery stats

After launch, WhatsAble shows basic delivery analytics: sent / delivered / read (Bulk Message and up). Block rate is not a WhatsAble dashboard metric — check Meta Business Manager. Advanced analytics are a Pro / Agency surface, not Bulk Message. Pause, resume, and cancel for an ongoing broadcast are not available in the current console path. Track basic sent / delivered / read stats and download results when your role allows. Upcoming scheduled sends can be removed on the API path when that endpoint is in use.
Canonical money and full unique-contact tiers: whatsable.app/pricing. Plan matrix docs: plans Bulk Message / Pro / Agency.

​
Cold outreach and deliverability (Meta)

For cold lists (contacts who have never messaged the business), especially US numbers, Meta may choose not to deliver if the recipient has not engaged before. Ideally the contact has messaged first. European numbers often fare somewhat better than US for cold reach, but any fully cold list still risks poor deliverability or flags. Warm gradually: for cold or new-number campaigns, prefer smart (or modest regular) pacing over risk blasts. Gradual send helps warm the number and reduces throttling / block risk. This is Meta deliverability behavior — not a WhatsAble “US block” product toggle.

​
Limits and what broadcasts are NOT

Scheduled broadcast ≠ drip. Future send time is available on broadcast plans; multi-day drip delays are not “schedule” — see below.
  • No native drip builder. Day-0 / day-3 / day-6 (or similar) sequences are built in Make, Zapier, or n8n; WhatsAble sends each template when the automation fires. Do not describe an in-product drip / delay campaign builder.
  • No typing-indicator dots claim for broadcast (or product-wide as a WhatsAble surface).
  • Do not invent WhatsAble RPM numbers here.
  • Do not invent UI chrome (library redesign tabs, Craft wizard labels, Upcoming wrap, Switch, Numbers Meta reports) that is not present in your console.
  • Broadcast ≠ templates. Creating / approving templates is a separate operator page. Only approved templates send.
  • Bulk Message has no team inbox, AI, or integrations — replies to broadcast recipients are not a Bulk Message inbox workflow.
  • Group Messaging is unavailable / waitlist only — not a live broadcast substitute.
  • Competitor comparisons and Meta per-country cent tables are out of scope; Meta fees pass through at 0% markup.

Plans: Bulk Message, Pro, Agency

Who gets broadcast, schedule, inbox, AI, and unique-contact billing.

Pricing (canonical money)

Live prices, contact tiers, overage, and annual toggle.

Message templates

Create and approve WhatsApp templates (separate from broadcasting).

API: send template message

Programmatic single-recipient template send (not the CSV broadcast wizard).

Make overview

External sequences / drips — Pro and Agency.

Zapier overview

External sequences / drips — Pro and Agency.

Connect WhatsApp (Coexistence)

Keep the Business app while using the API.

Team inbox

Shared 2-way inbox on Pro and Agency (not Bulk Message).

​
FAQ

​
Which plans can send CSV / template broadcasts?

Bulk Message, Pro, and Agency. Broadcasting is the main Bulk Message use case. Scheduled future sends are included on those plans.

​
What CSV columns does WhatsAble require?

The phone column must be named exactly phone_number (country code; omit + on the upload path). Add body1, body2, … for template variables, plus media or button_dynamic_url_value when the template needs them. Prefer the downloadable template CSV from the broadcast UI after you pick a template.

​
Why did my broadcast fail after I uploaded a CSV?

Almost always CSV formatting: wrong header (not phone_number), missing country code, or variable columns not named body1, body2, …. Also confirm the template is approved and Meta has a payment method.

​
Can I build a day-0 / day-3 / day-6 drip inside WhatsAble?

No native drip builder. Build the delays in Make, Zapier, or n8n; WhatsAble sends each message. Scheduled broadcast is a single future send time, not a drip chain.

​
Will Meta deliver cold US campaigns?

Meta may not deliver cold outreach to US numbers when recipients have never engaged. Warm gradually (prefer smart / modest regular over risk blasts). Ideally contacts message you first.

​
Where do I see block rate?

In Meta Business Manager, not as a WhatsAble analytics metric. WhatsAble basic stats = sent / delivered / read.

​
Is broadcasting the same as the template API?

No. The console CSV broadcast flow uploads a list and paces delivery. The template message API sends to one recipient per request. Agent-skills / automation scripts can orchestrate the same three backend steps the console uses; that is advanced automation, not a substitute for reading this operator page.