Bouncer DocsBroadcast via Bouncer Direct
Send a one-time campaign from a Bouncer Direct WhatsApp connection
Use this campaign type when your WhatsApp number is connected through Bouncer Direct and you want to send a one-time message to a group of contacts.
This option is separate from Meta Cloud API because the connection model is different. Bouncer Direct uses a QR-based WhatsApp connection, so setup, behavior, and sending constraints are not the same as Meta's official API.
Broadcasting through Bouncer Direct is not recommended for most businesses. Meta is increasingly cracking down on unofficial or high-risk sending patterns, and using QR-based broadcast flows can increase the chance of account restrictions or bans. If you need a stable long-term setup, use Broadcast via Meta Cloud API instead.
Recommended option first
If you are choosing a sending method today, Meta Cloud API is the best option.
Use Meta Cloud API if you want:
- the official WhatsApp Business sending path
- better long-term stability for outbound messaging
- template-based broadcasting with Meta-approved flows
- the lowest risk setup for business use
Use Bouncer Direct only if you understand the tradeoffs and are intentionally accepting the added account risk.
When to use this
Use Broadcast via Bouncer Direct when you want to:
- send a one-time message from a QR-connected number
- run simple outbound outreach without building a multi-step sequence
- use a number that is already connected through Bouncer Direct and cannot move to Meta Cloud API yet
Before you start
Make sure you have:
- a working Bouncer Direct connection
- the correct recipient list or filtered audience
- the final message content ready to review
How sending works
The typical flow is:
- Open the Campaigns area in Bouncer
- Choose Broadcast via Bouncer Direct
- Select the connected Bouncer Direct number
- Write or review the message content
- Choose the audience or contact list
- Review the campaign summary
- Send the broadcast
When people still use this
Some teams still use Bouncer Direct when:
- your number is already operating through Bouncer Direct
- your sending flow is already built around a QR-connected number
- you are working around short-term operational constraints
These are convenience reasons, not recommendation reasons. If you can move to Broadcast via Meta Cloud API, you should.
What to review before sending
Before sending, confirm:
- the connected number is online and healthy
- the message content is final
- the audience is correct
- the send is going through the intended connection type
Common things to watch for
| Problem | What to check |
|---|---|
| Wrong connection selected | Confirm you're using the intended Bouncer Direct number |
| Number connection is unstable | Check the connection status before starting the broadcast |
| Incorrect audience | Review your selected contacts or filters |
| Message looks incomplete | Re-read the final message before launching |
| Account restrictions or bans | Move high-volume or business-critical sending to Meta Cloud API |
Use this instead of drip campaigns when...
Choose Broadcast via Bouncer Direct when you want a one-time send from a Bouncer Direct number. Choose Drip Campaigns when you need a sequence with multiple timed steps.