Back to all articlesCampaign scheduling

Choose Between One Large Send and Staggered Campaign Waves

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A campaign expires tonight. Contacting everyone together gives customers more time, but concentrates questions and purchases. Staggering releases creates opportunities to reassess staffing and stock, yet later customers may receive an offer too late to use.

The decision is not simply whether smaller sends feel safer. Choose one release when local timing, concentrated response work, and inventory exposure all fit. Choose waves when checkpoints can change subsequent releases without sacrificing the customer’s usable window. If neither passes, reduce the audience or change the offer.

The filled worksheet below demonstrates that decision. It treats a scheduled release as neither proof of receipt nor permission to proceed when a checkpoint fails.

1. Calculate the latest useful release first

Start with the expiry and work backward. Customers may need time to notice the message, ask questions, get answers, and complete the purchase. Support closing before the offer expires can shorten that usable window.

Record the expiry in customer-local time, your chosen contact hours, the time needed to act, and any additional allowance for delayed receipt or noticing the message. Do not silently count the same allowance twice—or omit it entirely.

For this article’s hypothetical campaign, customers need five hours after noticing the offer. A separate 30-minute receipt-and-noticing allowance makes the required release-to-expiry interval five and a half hours. With expiry at 18:00 UTC, the latest useful release is therefore 12:30 UTC, not 13:00.

This allowance is a planning choice, not a delivery promise. If uncertainty requires more slack, release earlier. Use known customer time zones and the offset applicable on the campaign date. As a conservative operating practice, do not infer current location from a telephone country code alone; hold uncertain records outside a tightly timed plan until their suitability can be established.

2. Model workload across the whole next interval

Audience size is only a starting point. Estimate the handling work likely to fall within a defined planning interval:

New-wave workload = recipients released × assumed reply rate during the interval × handling minutes per reply.

Compare that with usable agent minutes after other duties and reserve. Then add earlier-wave work. An empty queue at a checkpoint does not mean earlier recipients have finished responding.

The complete release test is:

Existing backlog + expected additional work from earlier recipients during the next interval + uncertainty allowance + new-wave workload ≤ usable capacity.

Count each task once. Existing backlog means handling effort still outstanding at the checkpoint, not the original effort for conversations already partly resolved. Additional earlier-recipient work includes replies not yet received and anticipated follow-up effort not already in that backlog.

If delayed replies cannot be estimated credibly, retain more capacity or shrink the next wave. Staggering reduces concentration only when the spacing and available coverage actually absorb the work; it does not reduce total campaign workload.

3. Define inventory quantities before comparing schedules

A useful stock gate separates physical availability from planning allowances:

  • Remaining sellable stock: opening stock less completed purchases, actual holds, and other-channel consumption.
  • Remaining protected stock: stock still reserved for other purposes, if it has not already been excluded from the sellable figure.
  • Outstanding-demand allowance: possible purchases from earlier recipients that are not already completed or held.

Subtract remaining protected stock and outstanding-demand allowances from remaining sellable stock before testing a new wave. A hold must not also appear in the outstanding-demand allowance. If another channel consumes protected stock, reduce both the physical stock balance and the remaining protected allocation appropriately; do not subtract the original protection again.

Use a higher-demand scenario as well as a central estimate. Neither guarantees availability. Their purpose is to expose the amount at risk and create a defensible stop point. If stock records are stale, the apparent precision of a recipient limit is misleading.

4. Filled worksheet: compare three release patterns

Fictional worked example: Every number, time, assumption, and outcome below is hypothetical, not an Alactic customer result or benchmark. These are alternative schedules for the same audience, not experimental audience splits.

Shared inputs

  • Audience: 1,200 permissioned recipients; 600 in UTC+0 and 600 in UTC+2, with known time zones.
  • Expiry: 18:00 UTC, equivalent to 18:00 and 20:00 locally.
  • Chosen contact hours: 09:00–17:00 locally. These are business choices, not platform rules.
  • Customer time: five hours to act after noticing, plus 30 minutes of release-to-noticing slack. Latest useful release: 12:30 UTC.
  • Coverage: five agents from 09:00–18:00 UTC. In each 105-minute planning interval, each provides 90 usable campaign minutes after other duties and reserve: 450 minutes combined.
  • Reply assumption: 12% reply within the first 105 minutes; eight handling minutes per reply. Later replies are additional gate inputs.
  • Stock: 220 opening sellable units, including 30 protected units.
  • Purchase scenarios: 8% central demand and 15% higher demand, assuming one unit per purchase.

Alternative A: all 1,200 at 09:00 UTC

Local release times are 09:00 and 11:00, both acceptable. Everyone has nine hours until expiry. The early workload is 1,200 × 12% × eight = 1,152 minutes, against 450 usable minutes in the first interval.

Central demand is 96 units; higher demand is 180, against 190 units after protection. Inventory narrowly passes that scenario, but staffing fails. There is no later release to withhold once the audience has been contacted.

Alternative B: 400 at 09:00, 10:45, and 12:30 UTC

Each proposed wave contains 200 recipients from each time zone. Local release times are 09:00, 10:45, and 12:30 for UTC+0; 11:00, 12:45, and 14:30 for UTC+2. All satisfy the chosen hours.

Release-to-expiry intervals are nine hours, seven hours 15 minutes, and five hours 30 minutes. The last release explicitly preserves the 30-minute noticing allowance before the five-hour action period.

Each full wave produces 400 × 12% × eight = 384 minutes of assumed early work. That leaves 66 minutes for existing backlog, future earlier-wave work, and uncertainty combined—not 66 minutes for the visible queue alone.

Checkpoints at 10:30 and 12:15 allow a decision before release. Each full wave represents 60 units under the higher-demand scenario. This alternative passes only conditionally.

Alternative C: 400 at 09:00, 12:00, and 15:00 UTC

All releases fit the chosen local contact hours, and wider spacing offers more time to clear replies and observe purchases. But the final group has only three hours until expiry. It fails the customer-time requirement even before allowing for noticing delay.

Selected design: Alternative B, subject to explicit authorisation at each checkpoint. The business is not committing to contact all 1,200 people. A failed gate reduces or stops a release; it does not move the final wave beyond 12:30.

5. Apply the reply gate with delayed responses included

At the first checkpoint, use the interval from the proposed 10:45 release to 12:30. Conservatively retain all checkpoint backlog in the calculation rather than assuming it will clear before release.

Hypothetical componentHandling minutes
Existing earlier-wave backlog18
Additional earlier-wave work expected during the next interval24
Additional uncertainty allowance16
New 400-recipient wave384
Total planned workload442
Usable capacity450

The full second wave passes by eight minutes. This is a narrow margin, not reassurance that the assumptions are correct. The 24-minute estimate represents three additional eight-minute handling equivalents; the 16-minute allowance represents two more. These are fictional planning choices that an operator must replace with a defensible estimate.

At the second checkpoint, suppose backlog is 24 minutes, expected additional earlier-wave work is 80, and uncertainty allowance is 32. Earlier-recipient work totals 136 minutes. A full wave would require 520 minutes and fail. A 160-recipient wave requires 153.6 new handling minutes, bringing the total to 289.6 and passing the staffing test. Stock must still pass independently.

6. Reconcile stock and calculate the final audience

The following ledger makes both checkpoints auditable. Actual holds are unavailable for sale but are not completed purchases.

Hypothetical stock entryFirst checkpointSecond checkpoint
Opening sellable units220220
Cumulative completed campaign purchases2958: 29 per earlier wave
Current actual campaign holds36: 3 per earlier wave
Cumulative other-channel consumption046
Remaining sellable stock188110
Remaining protected allocation3030
Outstanding-demand allowance, wave one2828
Outstanding-demand allowance, wave twoNot released28
Stock available for next-wave planning test13024

Each 400-recipient wave has a 60-unit higher-demand scenario. With 29 purchases completed and three units held, its remaining allowance is 60 − 29 − 3 = 28 units. At the second checkpoint, two earlier waves therefore require 56 units. This is a conservative scenario remainder, not a forecast of exactly 56 future purchases.

The second balance is 220 − 58 − 6 − 46 = 110. In this fictional ledger, the 46 other-channel sales consumed unprotected inventory; none consumed the protected allocation. Thus 30 protected units remain inside the 110 and must still be deducted once. If the stock report already excluded those units, subtracting 30 again would be wrong.

The first checkpoint allows 188 − 30 − 28 = 130 units, enough for the second wave’s 60-unit stress case. The second allows 110 − 30 − 56 = 24 units. At 15% demand, the boundary is 24 ÷ 0.15 = 160 recipients.

The filled decision is therefore: release 400, then 400, then at most 160 at 12:30, subject to refreshed authorisation. That contacts 960 and withholds 240. The owner may choose fewer than 160 if uncertainty warrants it; the boundary is not an availability guarantee.

7. Assign decisions and record what actually happens

Give one campaign owner authority to approve each release after receiving staffing and stock reports. If a checkpoint is missed, hold the release. If the latest useful release time passes, leave the remaining recipients uncontacted for this offer rather than completing the list late.

For WhatsApp, scheduling does not replace readiness. Recipient permission matters, and opt-outs must be honoured. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Approval does not guarantee delivery. Check the current WhatsApp Business Messaging Policy for precise requirements, and provide a clear human escalation path for automated conversations.

Keep campaign preparation, template review, release authorisation, and actual delivery as separate operating states. These are recommended workflow distinctions, not claims about available product controls.

Afterward, record actual release times, delivery information where available, peak backlog, delayed-reply workload, handling effort, stock reconciliation, and recipients withheld. Compare these observations with the worksheet assumptions. The useful outcome is knowing which constraint governed the decision—and whether the next campaign needs more coverage, smaller waves, better stock information, or a longer customer window.

Campaign schedulingWhatsApp operationsCapacity planningInventory planning

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications