Skip to main content
A campaign can’t send until it’s ready on every channel. The send checklist names the missing piece before you press Send, rather than refusing afterwards, and every item has a button that takes you to the fix. You’ll see the checklist in two places: in the composer while you build the campaign, and on the campaign’s page once it’s scheduled.

In the composer

The Before you send panel on the right of the composer shows Ready when everything is in place, or how many items are left. Send and Schedule stay disabled until it’s clear.

Campaign setup

Content for each channel

These items appear only for the channels you’ve selected. Organizations in WhatsApp early access also see Choose an approved WhatsApp template and Set the WhatsApp business number.

Credits

Once the audience is chosen and the send costs credits, a credits item appears:
  • Cost within balance, with the estimate and your available credits, when the wallet covers it.
  • Top up, followed by the shortfall and credits to cover this send, when it doesn’t. Select Top up to buy credits without leaving the composer.
See Credits: estimates and holds.

Checks from your account

Once the draft has saved, Brudcast adds the checks only it can answer: your domains, sender approvals and business address. They show the message below, with a button to the fix.

On the campaign page

A scheduled campaign’s Overview tab shows a Before you send list. Each row is marked as passing, as a warning, or as blocking, with a button to the fix. When something blocks the send, hovering over the disabled Send button tells you why. For example, Add at least one list or segment before sending. or Top up your credits to cover this send.

Checks when the campaign sends

When you press Send, or when a scheduled campaign’s time arrives, Brudcast checks again:
  • Your organization is allowed to send. A sending review or a suspension stops it.
  • Every channel’s product is still available, and email and push are still subscribed.
  • Someone in the audience can be reached on at least one channel.
  • Every item in the checklist above.
  • The wallet covers the estimate. Credits are reserved at this point.
If a check fails when you press Send, the send is refused with the same message, and nothing is reserved. If it fails for a scheduled campaign, the campaign stays Scheduled and Brudcast tries again about every 30 seconds until it can send or you cancel it.
Unknown merge tags don’t block a send. They show a warning in the Content section, because a tag that doesn’t match a field sends as empty text.

Test and preview

Check a campaign before your audience does.
  • Preview the email. Once the body is designed in the visual builder, the Email block shows a summary with a Preview button. It opens the message the way a mail app shows it, with the subject, the sender and the compliance footer. Inside the builder, Preview at the top right and the Desktop preview and Mobile preview switches do the same job.
  • Review every channel. Once a campaign is scheduled or sent, its Content tab shows each channel in one pass down the page, marked Ready or Draft: the email’s subject, From, Reply-to and rendered body; the SMS message, Sender ID and Length; and the push notification with its Apps, Expires after, Priority, Click URL and Data. Tracking & tagging underneath shows what the send was set up to record. Drafts open in the composer instead, so there’s no Content tab until the campaign is scheduled.
  • Send a test push. On a scheduled campaign, open the More actions menu (the ⋯ button) and select Send a test. Choose an active Push app, paste the Device token for your device, and select Send test. The test sends the campaign’s saved notification with its image, click URL, data, expiry and priority. Merge tags are left as written, because there’s no contact to fill them from, and test sends don’t count toward your campaign statistics.
There’s no email test send. An email test is only written to your logs and never delivered, so it’s no proof that a message arrives. To check email end to end, preview it, then send the campaign to an audience that contains only your own contact.

Credits: estimates and holds

Before a campaign sends, Brudcast estimates what it will cost in credits. When it sends, it holds that amount for every channel at once. When each channel finishes, it charges what was actually sent and returns the rest. You see the estimate in the composer’s Live summary, at the bottom of the audience picker, in the checklist’s credits item, in the send confirmation, and as an Estimated cost tile on the campaign page, which reads Free when the send doesn’t use credits. The estimate starts from reach: how many people each channel can actually get to. Email and push cost credits only for messages beyond what’s left of your plan’s allowance for the period, so a send that fits inside the allowance costs nothing. SMS costs the destination’s rate per segment, for every segment of every message, and the segment count includes the “Reply STOP to opt out” line. Credits are reserved when the campaign starts sending, not when you schedule it. Every channel is reserved together: if the wallet can’t cover all of them, nothing is held, the send is refused, and the campaign stays in draft or scheduled. The SMS hold carries a safety margin, because merge tags make message lengths vary, and the extra comes back when the channel finishes. When a channel finishes, its hold settles to what it actually sent, and whatever’s left goes back to your wallet in the same mix of purchased and bonus credits it came from. The campaign page then shows Credits used instead of Credits on hold. If a channel costs more than its hold, the difference is taken from your balance, which can leave it below zero because the messages have already gone out. The next campaign can’t reserve credits until you top up. Every reserve, settle and release appears in your wallet’s transaction history, against the campaign. See Credits and wallet.

Create a campaign

Build a campaign end to end.

Credits and wallet

Balances, bonus credits and the ledger.

Channels overview

Senders for every channel, and their approval.

Email builder

Why a business address is required.