ChatBridge24

MARKETING CAMPAIGNS

Send an approved template to a built audience

A campaign is an approved template, an audience you can stand behind, and a send that reaches each recipient once. What matters is not how fast it sends — it is that a retry never sends anybody a second copy.

WhatsApp marketing campaigns in ChatBridge24 send an approved template to an audience you build. Every message a campaign sends is one somebody is charged for and a real person receives, so everything below is about reaching each person once, at the pace you set, and stopping when something is wrong — not about speed. Who receives a campaign is decided by audience segmentation, and what each message costs follows Meta’s per-message pricing.

Campaigns send from numbers connected to the WhatsApp Business API and are included in the Enterprise plan; see ChatBridge24 pricing.

Campaign October price list October price list Audience: Marina enquiries, last 90 days · 1,284 people SENDING · PACED 778 of 1,284 attempted · about 14 minutes left at 37.5 a minute Delivered 731 OK Read 402 LIVE Failed 12 ERROR Opted out 4 STOP EVERY RECIPIENT, WITH ITS OWN OUTCOME +971 50 ●●● 4182 Delivered 09:12 READ +971 55 ●●● 9930 Delivered 09:12 DELIVERED +971 52 ●●● 7741 No WhatsApp account FAILED +971 56 ●●● 2065 On the do-not-contact list SKIPPED
A campaign mid-send: the audience it was built from, a progress meter, per-outcome counters and the result recorded against every single recipient. A drawing of the product; the figures are invented.

How a campaign is assembled

Six steps, and the audience is chosen after the message, not before.

01

Pick the number it sends from

A campaign belongs to one connected number, so its sending limits, its quality rating and its template library are that number’s.

02

Pick an approved template

Only templates WhatsApp has approved are offered, and each is sent in the shape it was approved in. An approved template the campaign cannot fill is shown disabled, with the reason.

03

Fill its blanks

Each blank is filled in place, on the message itself. A value is either the same for everyone or taken from each contact’s own data, and you choose which, per blank, before you choose the audience.

04

Build the audience

From a spreadsheet, a pasted list, the number’s own contacts, an earlier campaign, a saved audience or, in the Bitrix24 app, your Bitrix24 CRM records. The build refuses rather than guesses: if the do-not-contact list cannot be read, nothing is built.

05

Set the pace and the hours

An optional per-campaign rate, which never exceeds the number’s own sending rate, plus the hours you are willing to send in and a cap on how often one person may be contacted.

06

Start it, and watch per recipient

Every recipient carries its own outcome and its own reason, and failures are grouped by reason so a pattern is visible at a glance.

Why a retry cannot send twice

Each recipient is reserved once, before anything is sent.

A message that is sent twice is charged twice and lands twice on a real person’s phone. So a recipient is taken for sending in the same step that selects them: two servers working through the same campaign can never be handed the same person.

Each send is recorded before the message goes to WhatsApp. If a send is interrupted — a server restarting mid-batch, for example — a recipient whose message may already have gone is marked for you to check and is never sent again automatically, while a recipient who was never reached is simply tried again.

Where a campaign stops itself

Each one pauses the campaign with its list intact, rather than burning through it.

The do-not-contact list is unreadable

The build and the send both stop. Sending around a do-not-contact list because it could not be read is the one failure here that cannot be taken back.

The template changed under the campaign

If the template no longer takes the values the recipients carry, the campaign pauses instead of failing contacts one at a time.

The plan or the payment will not cover it

If the number’s plan no longer includes campaigns, or WhatsApp refuses because of a payment problem on the WhatsApp Business Account, the campaign pauses and every unsent recipient waits for Resume.

The number is not available

A number that is suspended, disconnected or not yet live pauses its campaigns rather than failing every recipient against it.

What the pace means

You can give a number its own hourly sending rate, shared by every campaign on it, and give each campaign a per-minute rate of its own; a campaign never sends faster than either. Sending hours and days keep a campaign to the times you choose, and the frequency cap skips anyone who already received a campaign from the same number within the days you set.

Anyone who opts out, or whom your team blocks, while a campaign is running leaves the queue before their turn. A time-to-finish estimate appears only once enough recipients have been attempted to measure a real sending rate.

Where it sits

WhatsApp audience segmentation

The filters a campaign audience is built from, and the checks that stop a wrong list.

WhatsApp message templates

Getting the message approved before a campaign can carry it.

WhatsApp Business API pricing

Who bills you for a marketing message, and on what unit.

ChatBridge24 pricing

Marketing campaigns are in the Enterprise plan, per connected WhatsApp Business API number.

From the blog

Further reading on this subject.

WhatsApp marketing from your Bitrix24 CRM

Campaigns to CRM segments, automation by deal stage and UTM lead tracking.

Campaigns that keep a number healthy

Consent, audience segmentation and pacing that keep campaigns working.

Templates approved first time

The three categories and the rejection reasons that cost the most time.