Mass WhatsApp sends, the way Meta actually allows — on the official Cloud API.

Two rules, no shortcuts. One: send only through the official WhatsApp Cloud API, never through grey-tool browser automation or an unofficial gateway — that is what actually gets numbers banned. Two: use Meta-approved templates for anything sent outside an active conversation, and only message people who have a genuine relationship with your business. WhatsMark sends exclusively through the official Cloud API and only lets you broadcast on templates Meta has approved. Keeping a clean opted-in list is your responsibility as the business — Meta ties your quality rating and messaging tier to how recipients react, so a well-kept list is also what protects your deliverability.

A template broadcast uses a Meta-approved template and can be sent to any contact at any time — this is what you use for promotions, restocks, and notices. A session (message) broadcast sends free-form text with no template, but only to contacts who are inside the open 24-hour service window — i.e. people who have messaged you in the last day. WhatsMark automatically limits a session broadcast to exactly those in-window contacts, so you can push a quick free-form update to an active audience without waiting on template approval.

A single broadcast can reach as many contacts as you select from your list — there is no artificial per-broadcast recipient cap inside WhatsMark. Your total stored contacts are bounded by your plan quota (with contact add-ons available if you need more), and the number of broadcasts you can run each month is set by your plan: 5 template and 5 session broadcasts per month on Free, 100 of each on Professional, unlimited on Reseller. The deeper ceiling is always Meta's own messaging tier on your phone number, which grows automatically as your quality rating and volume improve.

You build the audience from your existing contacts. Narrow the contact picker by contact group (for example a "vip" or "cart-abandoned" group), by status, by source, or by contact type, then broadcast to the selection. A live count shows how many reachable contacts you have chosen before you launch. If you are sending on a specific connected number, the audience is automatically scoped to contacts reachable on that channel, and session broadcasts are further limited to contacts inside the open 24-hour window.

Yes. Choose send-now or set a future date and time, and a background job fires the broadcast the minute it comes due. A scheduled broadcast goes out at that single chosen time for the whole audience — WhatsMark does not stagger delivery to each recipient's local timezone today, so pick the time that suits the bulk of your audience. Once a broadcast is running you can pause it, resume it, or cancel it at any point.

Yes — this is one of the most useful controls. When a broadcast finishes, you can clone it down to just the contacts who replied, which creates a fresh draft targeting only those warm contacts for your follow-up. Separately, you can resend a broadcast to only the recipients whose message failed, without re-messaging everyone who already received it. Every recipient's delivery, read and reply status is tracked individually so these actions target exactly the right people.

No. You connect your own WhatsApp Business Account to WhatsMark, which means Meta charges the per-conversation fee directly to your Meta account — WhatsMark never sits between you and that fee. Our pricing is a flat subscription for the platform. On top of that, marketing broadcasts that qualify are routed through Meta's cheaper Marketing Messages Lite delivery path automatically, so eligible sends can cost less at Meta's end with no configuration from you.

Not today. WhatsMark does not currently ship a built-in A/B split-test with automatic winner promotion, and we would rather say that plainly than imply a feature that isn't there. What you can do right now is run two separate broadcasts to two contact groups and compare their real-time delivery and reply analytics side by side. Native variant testing is on the roadmap; it is not part of the product at the moment.