WhatsApp bulk messaging on the Meta Official API

Through the Meta Official API, and nothing else. You connect a number to the API, create a template and submit it for approval, build the list with each contact variables and send. Outside the 24-hour window Meta only delivers approved templates, and every delivered message is charged. The old route — an extension or bot automating WhatsApp Web — breaks the Terms of Service and is exactly what gets numbers dropped mid-campaign.

The Official API is the channel Meta itself provides for this, so volume within your granted limit is not a violation. What takes accounts down is quality: people blocking, reporting and opting out. Meta tracks that as a quality rating and, if it drops, your reach is cut long before any ban. That is why Pragmaz shows the opt-out rate per template and warns you when your number rating gets worse.

Meta charges per delivered message, priced by category and by country: marketing is the most expensive, utility and authentication cost far less, and service conversation inside the 24-hour window is not charged. You pay that directly to Meta — Pragmaz charges nothing per message sent, only the plan subscription. On the broadcast review screen you see the template category and the estimated campaign cost before confirming.

Meta messaging limit rules, counted in unique contacts per 24 hours. A new account starts at 250 and climbs in steps: 2,000, 10,000, 100,000 and unlimited. Business verification already takes you to the second step, and the next ones come automatically when you use a good share of your current limit while keeping quality high. Your number granted limit appears on the review screen, before you send.

No. Sending on the Official API goes out from Meta servers, not from your browser. You schedule the campaign, close the laptop and it runs at the set time. That is one of the most keenly felt practical differences against tools that automate WhatsApp Web, which stop the moment the tab closes.

Yes, through Coexistence: your phone number also starts speaking over the Official API, and you keep answering on the handset as usual. The other option is the Cloud channel, with a dedicated number hosted on Meta infrastructure. In both cases one-to-one sending goes out on the Official API; the practical difference is speed, which is higher on Cloud.

Pragmaz sends at the channel ceiling, with no artificial brake: up to 80 messages per second on Cloud and 20 per second on Coexistence, Meta own throughput figures. A 10,000-contact list on Cloud goes out in a few minutes. Pacing is controlled per account, so you use the full granted rate without hitting rate-limit errors.

It is the message Meta reviews and clears before you can send it to anyone who has not written to you in the last 24 hours. It exists to stop spam. You write the text with slots for variables, attach media and buttons, pick the category and submit; the answer usually comes back in minutes. At Pragmaz this happens inside the panel, and an approved template is immediately available when you build the broadcast.

Yes. Templates carry variables, and each row of your list can bring its own values: name, order number, date, amount, whatever the message asks for. You also set a default value for rows that come empty, so no message goes out with a gap. The list comes in pasted, via Excel or CSV spreadsheet, or pulled from the contacts already synced from a connected device.

Every broadcast has a report with sent, delivered, read and failed updating in real time, and one row per recipient. When something fails, the panel translates the Meta error code and states the real reason — number does not exist, over the limit, template paused. You export the lot to Excel colour-coded by status or to CSV, and opt failing contacts out in one click.

The reply lands in Pragmaz own multi-agent chat, in the same panel, and opens the 24-hour window where you talk freely, with no template and no message cost. Your team answers together on the same number, the conversation becomes a card in the Kanban CRM and, if you want, an AI agent replies first and calls the salesperson at the right moment. A broadcast with nobody to answer it is money thrown away.

Every platform plan. Essential already sends on the Official API, with 1 connected number and 1 agent. Pro opens 3 numbers and 6 agents and adds Kanban CRM, chatbots, an AI agent and team management — it is the plan for whoever sends to a big list and needs people and automation to handle the replies. Business goes to 8 numbers and 20 agents. On the annual plan all of them are 30% cheaper.