Resolve Two Campaigns Competing for the Same Send Window
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Two teams want Thursday afternoon. One has an external cutoff; the other requested the slot first. Both need the same operations specialist and response team. Choosing by seniority or request order would settle the argument without establishing whether the schedule can work.
Instead, check readiness, compare the consequences of moving, and test the preferred allocation against capacity by role and time block. Give the displaced campaign a checked alternative. If neither plan fits, reduce or defer the work rather than declaring a winner the team cannot support.
The method below is a recommended operating design. All campaigns, scores, times, and workload figures in the worked example are hypothetical, not Alactic customer results.
1. Define the conflict and the comparison windows
A calendar overlap is not necessarily a resource conflict. Campaigns might run together using separate teams. Conversely, moving one send by an hour may accomplish nothing if both generate responses during the same afternoon.
Identify the send window, preparation period, response period, and follow-up deadline. Separate resource pools: spare general-support time cannot replace an unavailable order specialist.
Ask each campaign owner for:
- The requested window and one specific alternative to evaluate.
- What changes if the campaign moves, supported by a dependency or cutoff.
- Readiness status and outstanding work.
- Workload by constrained role and meaningful time block.
- Inventory or service availability across both candidate windows.
Use the same requested-versus-alternative comparison throughout each campaign's scorecard. If the alternative changes, update the entire comparison rather than introducing a more convenient substitute for one criterion.
Choose one calendar decision owner. Sponsors supply evidence; the owner applies the rule and records the allocation. Keep campaign objectives, audience eligibility design, and attribution outside this discussion. Record unresolved execution questions as readiness dependencies.
2. Establish readiness gates before awarding priority
Record each gate as passed, conditional, or failed:
- Preparation: Required assets, approvals, configuration checks, and operating instructions are complete.
- Fulfilment: The offer or service can be provided, with relevant inventory or operational commitments confirmed.
- Release responsibility: A named person can authorise the send after the final checkpoint.
A conditional reservation needs an owner, completion deadline, and consequence if a dependency remains unresolved. It should not block a ready campaign indefinitely. Capacity is a separate gate, checked against the proposed schedule after ranking.
For WhatsApp campaigns, distinguish campaign preparation, template review, and actual delivery. 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. Recipient permission matters, opt-outs must be honoured, and automation needs a clear human escalation path. Check the current WhatsApp Business Messaging Policy for precise requirements.
Finished copy is not necessarily an approved template, and an approved template is not a delivered campaign. Likewise, a calendar reservation is not release authorisation.
3. Rank the cost of moving without counting it twice
Agree on a short scoring rule before comparing totals. This proposed scale has a maximum of twelve points. Capacity remains a pass-or-fail test, not a source of priority points.
- Movement consequence, weight three: Zero means little practical loss; one means recoverable disruption; two means the alternative misses a documented external cutoff or loses a confirmed stock or service allocation. Deadline and inventory evidence belong together here: one expiring reservation earns one score, not two.
- Customer action time, weight two: Zero means no independent timing loss is established. One means the alternative leaves adequate time but compresses a documented customer task. Two means it removes time required for that task. State the task and supporting timing evidence. Do not award points for a consequence already captured under movement.
- Readiness, weight one: Zero means a material dependency remains unresolved; one means a bounded task has an owner and checkpoint; two means required preparation is complete. A failed gate still blocks release.
The largest weight goes to irreversible loss from moving. Customer action time must measure a separate consequence, not restate the same deadline. If the only timing loss is an expired allocation already scored under movement, award zero additional points.
For equal totals, compare movement consequence, then customer action time. If still tied, the calendar owner records a reasoned allocation and the alternative offered. A high score never overrides insufficient capacity.
4. Work the example through priority and capacity
Fictional scenario: Campaign A announces a seasonal stock allocation whose reservation ends Friday at 17:00, with no extension confirmed. Campaign B sends an evergreen product-care guide. Both request Thursday, 14:00–15:00.
For each campaign, the comparison is Thursday afternoon versus Tuesday next week at 10:00. Tuesday misses A's allocation, but B's guide remains useful. No independent customer-task timing loss has been evidenced for either campaign.
Filled priority scorecard
| Criterion | Campaign A | Campaign B |
|---|---|---|
| Comparison window | Thursday versus Tuesday next week | Thursday versus Tuesday next week |
| Movement consequence | 2 × 3 = 6: Tuesday loses the confirmed allocation | 0 × 3 = 0: the guide remains useful Tuesday |
| Customer action time | 0 × 2 = 0: no separate timing loss established | 0 × 2 = 0: no established action deadline |
| Readiness | 2 × 1 = 2: preparation complete | 2 × 1 = 2: preparation complete |
| Total | 8 out of 12 | 2 out of 12 |
A's allocation expiry explains its movement points completely. Adding customer-action points for that same expiry would double-count urgency. A still has the stronger claim, but the score does not establish feasibility.
In the following hypothetical capacity record, available hours are net of existing commitments. Each row is a separate role-and-time pool; hours cannot be borrowed across rows. The required reserve is part of the gate: demand plus reserve must not exceed availability.
Thursday demand and reserve
| Role and block | Available hours | A demand | B demand if concurrent | Required reserve |
|---|---|---|---|---|
| Operations, Thursday 13:00–15:00 | 2 | 1 | 1 | 0.5 |
| Order specialist, Thursday 15:00–17:00 | 2 | 1.5 | 1 | 0.5 |
| Order specialist, Friday 09:00–12:00 | 2 | 1.5 | 1 | 0.5 |
| General support, Friday 13:00–17:00 | 3 | 2 | 1 | 0.5 |
A alone fits every block, including reserve. For example, Thursday order-specialist demand plus reserve is 1.5 + 0.5 = 2 hours, matching availability.
Concurrent campaigns fail all four rows when reserve is included. Operations needs 2.5 hours against two available; each order-specialist block needs three against two; general support needs 3.5 against three. General-support demand alone fits, but consumes the required reserve. That is still a failed gate.
The estimates assume coverage throughout each response block. If responses concentrate more narrowly, subdivide the block before confirming.
Tuesday replacement checked separately
| Role and block | Available hours | B demand | Required reserve |
|---|---|---|---|
| Operations, Tuesday 09:00–11:00 | 2 | 1 | 0.5 |
| Order specialist, Tuesday 11:00–13:00 | 2 | 1 | 0.5 |
| Order specialist, Wednesday 09:00–11:00 | 2 | 1 | 0.5 |
| General support, Wednesday 13:00–15:00 | 2 | 1 | 0.5 |
B fits each replacement block with reserve, and its owner accepts Tuesday as useful. The proposed allocation is therefore A on Thursday and B on Tuesday. Both become conditional reservations pending named coverage confirmations—not confirmed bookings yet.
5. Record the allocation and its state changes
This filled record completes the hypothetical example. Reuse its fields, not its estimates. Store it in the team's existing scheduling system alongside the evidence.
- Decision owner: Calendar coordinator.
- Proposed allocation: A retains Thursday, 14:00–15:00; B receives Tuesday next week, 10:00.
- Comparison and scores: Both campaigns compare Thursday with Tuesday next week. A scores eight; B scores two. A receives no additional customer-action points for the allocation expiry.
- Reason: A has the higher evidenced cost of moving. A alone fits Thursday; concurrent campaigns fail every listed block with reserve. B fits the separately checked Tuesday schedule.
- Evidence retained: Stock reservation confirmation, readiness checklists, scorecard, and both capacity tables.
- Current state: Conditional reservations for both campaigns; coverage confirmation outstanding.
- Confirmation owners and deadline: Operations lead confirms operations coverage; support lead confirms order-specialist and general-support coverage for both schedules by Wednesday at 16:00 before A's Thursday send.
- Transition to confirmed: Coordinator records each booking as confirmed only after its named coverage confirmations arrive. Missing confirmation triggers reassessment of the affected allocation.
- Final checkpoints: A's owner reconfirms inventory, readiness, and coverage Thursday at 11:00. B's owner rechecks preparation and coverage Monday at 15:00 before Tuesday's send.
- Release authorisation: Each designated sender obtains explicit authorisation from the campaign's release owner after its final checkpoint.
- Reopen triggers: Lost reservation, changed readiness, higher workload, or reduced coverage that consumes required reserve.
The sequence is proposed allocation, conditional reservation, confirmed booking, then release authorisation after the final checkpoint. Confirmation protects a place in the calendar; it does not remove the need to check changed conditions before sending.
6. Reduce unsupported plans and recover from changes
If neither campaign fits, request a smaller operational proposal with revised workload estimates. Removing a labour-intensive follow-up or reducing scope may help, but do not assume halving send volume halves support demand. Preparation and escalation work may remain fixed.
Splitting the send window helps only if revised response loads fit every constrained block. If no workable version remains, defer both and record the business consequence of missing the cutoff.
When conditions change after allocation:
- Pause release authorisation for the affected campaign.
- Update changed evidence while preserving the original record.
- Recalculate affected scores and role-by-block demand, including reserve.
- Reconfirm the other campaign's readiness and capacity before offering it the vacated slot.
- Record the revised allocation and notify both owners before they act.
For example, losing Thursday order-specialist coverage invalidates A's capacity check. It does not automatically make B feasible: B uses that role too. Check the remaining capacity rather than transferring the slot by default.
7. Improve the next decision with observed workload
After both response periods, compare estimated and actual work by role and block. Record backlog carried forward, reserve consumed, missed readiness checkpoints, and unplanned calendar moves. These observations show whether the schedule was workable; they do not establish campaign effectiveness.
If estimates repeatedly miss a narrow response peak, shorten the planning blocks. If specialists absorb work assigned to general support, correct the role assumptions. If urgency rests on unsupported customer-timing claims, require clearer evidence before awarding those points.
Keep exceptions visible. A sponsor-directed priority override should name the authoriser, displaced commitment, and accepted consequence while preserving the original scorecard. It should not turn a failed readiness or capacity gate into a pass. Improve the evidence and estimating practice before changing weights simply because someone dislikes the result.
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