Schedule Separate Campaigns That Share One Reply Team
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Two campaigns can target completely different customers and still compete for the same scarce resource: the people answering their replies. Moving one send an hour later may change nothing if both campaigns generate questions throughout the afternoon.
To schedule multiple campaigns with one response team, put their expected reply work on the same calendar as routine service work. Compare the combined demand with usable team capacity in each time block, then move campaign starts until the likely reply waves fit. Keep room for uncertainty, and check actual unfinished work before releasing the next send.
The calendar below shows how to do that without assuming that audience separation creates workload separation. It plans shared team capacity, not inbox routing or individual assignments.
1. Choose a planning unit that exposes collisions
A daily total can hide an unmanageable morning. If both campaigns start at opening time, spare afternoon capacity does not help customers who are already waiting.
Use time blocks short enough to reveal the reply peaks you expect and long enough to estimate sensibly. Two-hour blocks are a practical starting point when replies tend to arrive across several hours. Use shorter blocks if your own operating history shows a sharper surge.
Express demand in team work-minutes, rather than counting replies alone. A quick confirmation and a question requiring several exchanges do not consume equal effort. For scheduling purposes, estimate the active handling time needed to progress or complete a conversation, including likely follow-up work. Do not count time spent waiting for the customer as continuous staff work.
For each block, record:
- Usable team capacity after breaks, meetings, and other unavailable time.
- Routine work that will happen even if no campaign launches.
- Expected campaign reply ranges and their handling-time assumptions.
- Unfinished work carried in from earlier blocks.
- Remaining headroom and the condition for releasing the next campaign.
This is a demand calendar, not merely a list of send times. The important entry is what each send is expected to make the team do afterward.
2. Reserve capacity before allocating campaign work
Start with actual coverage, not the number of people on the roster. Someone scheduled for a meeting cannot simultaneously provide reply capacity. Routine service demand also has a prior claim on the team's time.
Keep a separate uncertainty reserve. Otherwise, a plan that fits exactly becomes overloaded as soon as one conversation takes longer than expected.
Fictional worked example: A small business has three people available during each of three two-hour reply blocks. Each block therefore contains 360 team-minutes. The planner protects 60 minutes for interruptions and variation, leaving a planning ceiling of 300 minutes per block. These figures are hypothetical, not staffing benchmarks.
Hypothetical baseline, repeated each working day Block Gross capacity Protected reserve Planning ceiling Routine work 09:00–11:00 360 min 60 min 300 min 150 min 11:00–13:00 360 min 60 min 300 min 120 min 14:00–16:00 360 min 60 min 300 min 180 min Campaign room before carryover: 09:00–11:00: 150 min 11:00–13:00: 180 min 14:00–16:00: 120 min
The lunch gap is not available reply capacity in this example. Any work left at 16:00 remains work for a later staffed block; it does not disappear when the calendar ends.
The protected reserve is also not extra space to fill with another launch. If the normal plan repeatedly needs it, either the demand estimate or the capacity ceiling needs revision.
3. Estimate a reply wave for each campaign
For each campaign, estimate how much work arrives in the first staffed block after the send, the next block, and subsequent blocks. Use a range rather than a single precise-looking count.
Where you have relevant operating history, use it to inform the shape of the wave. Where you do not, label the estimate as uncertain and begin with a smaller authorised batch. A new offer or a more complicated customer decision may create a different workload even if the recipient count stays unchanged.
In this fictional example, Campaign A is a renewal reminder and Campaign B is a new-service invitation. They reach different customers but share the same reply team. The planner assumes six active handling minutes per replying conversation for both campaigns, including expected follow-up effort.
Hypothetical reply-wave assumptions Wave position Campaign A Campaign B First staffed block 12–18 replies 14–22 replies Second staffed block 8–12 replies 8–14 replies Third staffed block 4–6 replies 4–8 replies Fourth staffed block 2–4 replies 2–4 replies At 6 handling minutes per conversation: A work by block: 72–108, 48–72, 24–36, 12–24 minutes B work by block: 84–132, 48–84, 24–48, 12–24 minutes
These are workload allocations, not a claim that every conversation finishes in the block where it begins. If substantial follow-up falls later, move that portion of the work into the later block rather than counting it twice.
The example also simplifies timing by placing demand into successive staffed blocks. In a real plan, map replies to the hours when customers are likely to respond, including overnight accumulation. Moving a send can change its reply pattern; shifting an old estimate mechanically is only a provisional assumption.
4. Combine the campaigns before approving either start
The original proposal starts both campaigns on Monday at 09:00. Each campaign looks manageable alone: routine morning work plus Campaign A's upper estimate is 258 minutes; routine work plus Campaign B's upper estimate is 282 minutes. Both fit beneath the 300-minute ceiling.
Together, they do not.
Original hypothetical schedule: both campaigns start Monday 09:00 All figures below are team work-minutes. Block Routine A range B range Combined range Upper headroom Mon 09–11 150 72–108 84–132 306–390 -90 Mon 11–13 120 48–72 48–84 216–276 +24 Mon 14–16 180 24–36 24–48 228–264 +36 Tue 09–11 150 12–24 12–24 174–198 +102 Planning ceiling: 300 minutes per block. Upper headroom = 300 minus the upper combined estimate. These rows show new demand only, before unfinished work carries forward.
Even the lower morning estimate exceeds the planning ceiling. At the upper estimate, the first block produces 90 minutes more work than planned capacity can absorb.
If that excess rolls forward, Monday's second block is no longer a comfortable 276-minute block. It has up to 366 minutes to handle: 276 new minutes plus 90 unfinished minutes. Using only the planning ceiling, that leaves 66 minutes for the afternoon, where another 264 minutes arrive. The day ends with 30 minutes unfinished.
Those figures assume the upper estimates occur together and the protected reserve remains protected. They are a stress check, not a prediction. They show why looking only at each row's new demand understates the collision.
5. Move starts to protect the whole reply wave
Moving Campaign B to Monday at 11:00 would remove the first-block collision but create another one. Its upper first-wave estimate of 132 minutes would join 120 routine minutes and 72 minutes from Campaign A: 324 minutes before any carryover.
The revised plan keeps Campaign A on Monday at 09:00 and moves Campaign B to Tuesday at 11:00. That gives the first wave time to subside and avoids Tuesday's heavier routine morning demand.
Revised hypothetical shared-capacity calendar Campaign A: Monday 09:00 Campaign B: Tuesday 11:00 Planning ceiling: 300 team-minutes per block Block Routine A range B range Combined range Upper headroom Mon 09–11 150 72–108 — 222–258 +42 Mon 11–13 120 48–72 — 168–192 +108 Mon 14–16 180 24–36 — 204–216 +84 Tue 09–11 150 12–24 — 162–174 +126 Tue 11–13 120 — 84–132 204–252 +48 Tue 14–16 180 — 48–84 228–264 +36 Wed 09–11 150 — 24–48 174–198 +102 Wed 11–13 120 — 12–24 132–144 +156 Wed 14–16 180 — — 180 +120 Release check for B: Tuesday 10:30 Confirm unfinished work, coverage, and the remaining reply-wave estimate. Do not release solely because the calendar says 11:00.
This version fits the upper estimates without spending the protected reserve. Its tightest campaign block is Tuesday afternoon, with 36 minutes of headroom beneath the planning ceiling. That is the block to watch if conversations become more involved than expected.
The trade-off is a later start for Campaign B. If that delay makes the campaign less useful, consider reducing its initial batch, securing genuinely available additional coverage, or changing the offer's timing. Do not solve the arithmetic by simply assuming fewer people will reply.
6. Make the next send conditional on current workload
A calendar built earlier in the week cannot know Tuesday's actual backlog. Add a release check shortly before each later campaign starts, with a named person authorised to proceed, reduce the batch, or postpone it.
At the check, replace assumptions with what is now observable:
- Count unfinished work in estimated handling minutes, not just open conversations.
- Confirm that planned team coverage still exists.
- Update the remaining workload from campaigns already running.
- Add the proposed campaign's upper workload estimate to every affected block.
- Release only if the revised plan fits the chosen ceiling, or explicitly revise the plan first.
For example, if 55 unexpected minutes of work must be handled during Tuesday afternoon, the revised calendar's 264-minute upper estimate becomes 319 minutes. That exceeds the planning ceiling. The response is to hold or reduce Campaign B before release, not to assume its first block's spare time will automatically solve the afternoon problem.
Keep operational readiness separate from workload readiness. For WhatsApp campaigns, recipient permission and opt-outs still matter. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Template approval does not guarantee delivery. Check the current WhatsApp Business Messaging Policy for precise requirements.
A prepared campaign, an approved template, and actual delivery are separate states. If delivery shifts, rebuild the expected reply wave around the changed timing rather than leaving the original capacity reservation untouched.
7. Recover from overruns without creating a second collision
If replies exceed the range, pause upcoming discretionary starts first. Work already generated still needs capacity; delaying a future campaign prevents adding more demand while the team catches up.
- More replies than expected: Increase the remaining wave estimate and carry unfinished work into the next staffed block.
- Longer conversations: Revise handling minutes even if reply counts look normal. Counts alone can hide the overload.
- Reduced coverage: Lower the capacity ceiling immediately. Do not leave an absent person's minutes in the plan.
- Late delivery or delayed customer response: Move the workload reservation. A quiet launch block is not evidence that later capacity is free.
- A fixed campaign deadline: Reduce the authorised send scope or arrange real additional capacity. Splitting a send helps only if the resulting reply waves are separated enough.
For the next planning cycle, record three operational checks: whether any block exceeded its ceiling, how many unfinished work-minutes reached the next day, and whether each release check led to a proceed, reduce, or hold decision. These observations help improve the calendar's assumptions without turning the exercise into a separate reporting project.
Tomorrow's practical step is to place the next two campaigns on one calendar with routine work and carryover included. Calculate the tightest block at the upper reply estimate. If it does not fit, change the start or scope before either campaign is released.
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