For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/guides/safe-bulk-sending.md.
  • English

      • How do I run a bulk send without burning my channel?

      A badly run broadcast does not just cost you the campaign: it costs you the channel. A number restricted by Meta and a domain marked as spam take weeks to recover, if they recover at all.

      In Clickmax, a bulk send goes out through one of two paths, and the rules below apply to both:

      Before you start

      • Role: Owner, Admin or Editor.
      • A connected channel in Messaging.

      1. Pick an audience, not the whole base

      Start from a segment, not from "everyone". Sending to people with no relationship to the subject produces blocks and unsubscribes — exactly the signals that sink your reputation.

      2. Check the size

      The broadcast screen shows the recipient count before you confirm, and the Run window shows how many contacts will enter the run. Check it matches the audience you expect before sending. In the run, the window also says how many contacts will be skipped because they went through the automation recently — keep that protection on unless the repeat is intentional.

      3. Respect the channel's limit

      ChannelThe limit that matters
      WhatsAppNew conversations started per day, set by Meta according to your number's quality
      EmailSender domain reputation; a sudden spike in volume sinks delivery
      SMS and voiceTime-of-day rules

      See official WhatsApp from scratch and email nurture sequence.

      4. Release it in batches

      Do not send everything at once. In a run, use the Dispatch pace — Contacts per cycle and Interval between cycles — to release a smaller slice, watch delivery and reaction, then widen; see How do I control the pace of a mass send?. In a broadcast, use batch sending. Batching turns a mistake into a small incident instead of a whole-base catastrophe.

      5. Test first

      Send to yourself and to someone on your team. Check the links, the personalisation fields and how it looks on a phone. A field name showing up raw in the message is the most visible and most avoidable error there is. In an automation, use the Test button with your own contact before publishing.

      6. Make it easy to opt out

      An easy way out protects the channel. Someone who does not want your messages and cannot leave will mark you as spam or block you — and that weighs far more than an unsubscribe.

      7. Follow it afterwards

      Send, then watch. If delivery drops or blocks climb, stop the rest before the campaign completes: cancel the run from its card (what has not gone out does not go out) or cancel the broadcast in progress.

      If it didn't work

      • WhatsApp was restricted: see the Meta sending limit (Portuguese).
      • The message went out with a blank field: that contact had no value stored for it — set a default value.
      • The Run button refuses another run: only one run can be scheduled or in progress per automation — wait for it to complete or cancel the current one.