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 controls in the Run window, which opens from the top of any published automation. There are two: Contacts per cycle, which splits the run's 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 run sends as fast as the channel allows.

      Role: any member with edit access to the workspace.

      Before you start

      • A published automation. Run exists on any live automation — with a Manual start trigger or an event trigger. The full walkthrough is in How do I run an automation for a contact, list, tag or segment?.
      • The run's source already chosen (Single contacts, List, Tag or Segment). The summary only shows the estimate once the audience has at least one contact.

      Steps

      1. Open the automation in the editor and click Run.
      2. Pick the source of the contacts and find Dispatch pace, right below the 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. Choose Now and click Run now, or Schedule for and click Schedule. The chosen pace is stored in the run.

      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-run, 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 affect a run already in progress? No. The audience, the batching and the pace are frozen when the run starts. A new value only applies to the next run.

      Does a scheduled run use these controls too? Yes. The pace is chosen in the same window, before confirming Schedule for, and applied when the run fires on the scheduled date.

      Does the pace apply to automations that start from an event? Only to runs. Contacts who enter through the event (a tag applied, a purchase) enter one by one, at the moment of the event, without going through cycles.

      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.