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/features/automations/mass-send-rhythm.md.
  • English

      • How do I control the pace of a mass send?

      Use the Dispatch pace card, which appears on the trigger when the automation sends to a list or to contacts with a tag. It has two controls: Contacts per cycle, which splits the audience into batches, and Interval between cycles, which decides whether there is any wait between one batch and the next. By default the interval is No wait — the automation sends as fast as the channel allows.

      Role: any member with edit access to the workspace.

      Before you start

      • An automation whose trigger is one of the mass sends: Manual start, Bulk Send to Tagged, Scheduled start or Scheduled Tag.
      • The list or tag already selected on the trigger. The card only shows the estimate once the audience has at least one contact.

      Steps

      1. Open the automation in the editor and click the trigger card.
      2. Find the Dispatch pace card, right below the selected audience.
      3. Drag Contacts per cycle to your batch size. Stops run from 10 to 10,000 contacts, with finer steps at the start (10, 20, 30, 40, 50, 100, 250, 500, 1,000, 1,500, 2,000, 3,000, 5,000 and 10,000). The default is 250.
      4. Drag Interval between cycles to the wait you want. The first stop is No wait (the default) and the rest run from 1 minute to 1 day.
      5. Check the summary below the controls: it shows how many cycles the audience was split into, the estimated duration, and the total contacts.
      6. Activate the automation. The setting saves on its own as you drag — there is no save button.

      What each control does

      The two axes serve different purposes, and they are easy to mix up.

      Contacts per cycle is the granularity of the send, and it applies even with no wait at all. Each cycle is an independent batch: if something fails mid-send, only that cycle is affected — what already went out is not resent, and the following cycles carry on. Smaller batches isolate a failure more tightly; larger batches cut the number of cycles.

      Interval between cycles is a clock-based brake, and it is optional. On No wait, every cycle is ready to go at once and what sets the pace is the channel's own limit — not the interval. Raise the interval only when you deliberately want to spread the send across hours, for instance to follow up on replies gradually or to avoid concentrating everything in one time slot.

      Reading the estimated duration

      The duration is the time until the last cycle starts going out — it measures the wait you configured, not how long delivery takes.

      With the interval on No wait, the duration reads immediate: there is no scheduled wait between cycles. That does not mean every message arrives at the same instant — actual speed depends on the limit of the channel used for the send.

      FAQ

      Does changing the values after activation affect a send already in progress? No. The audience and the batching are frozen at activation time. Changing the controls afterwards only applies to the next activation.

      Does the scheduled automation use this card too? Yes. All four mass-send triggers — manual, manual by tag, scheduled and scheduled by tag — share the same rhythm.

      I left the interval on No wait. Do I risk getting blocked on the channel? The send respects the connected channel's limit, so it never goes faster than the channel accepts. Use the interval when your goal is to spread the send across the day, not as protection against blocking.