Back to all articlesCampaign scheduling

Choose Between Sending Before a Closure and Waiting Until Reopening

Alactic Editorial9 min read

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

A promotion sent just before a planned closure can create a problem the campaign calendar hides: customers reply after the team has left. If the offer requires advice, a stock check or help completing an order, the business has invited conversations it cannot support.

Choose the send time around usable staffed response time, not merely the opportunity to launch. Enough capacity across an afternoon is insufficient if most questions arrive just before closing. Waiting until reopening helps only when accumulated requests leave room for new demand.

The method below compares pre-closure, during-closure and reopening schedules. Its fictional worked example includes a reusable decision table and filled approval record.

1. Identify the service promise behind the message

A send time carries an implied service promise. An invitation to discuss options suggests someone will be available. A self-service purchase link makes a different promise, although customers may still need help.

  • Conversation-dependent: customers need a recommendation, quote, confirmation or human decision.
  • Mostly self-service: customers can act independently, but exceptions may require assistance.
  • Informational: customers mainly need closure dates, reopening times or future availability.

For a conversation-dependent promotion, the reply window is part of the offer. Recipients need a reasonable opportunity to ask questions and receive useful answers before staff leave.

For a mostly self-service promotion, examine the failure path. If a purchase cannot proceed without a staff member changing a detail, that journey still depends on staffing. Assess what happens when the intended action fails, not just when it works.

Keep operational notices separate from promotions. Customers may need closure information even when stimulating additional demand would be unwise.

2. Compare the windows and test the reason to hurry

Before closure: is there enough response time?

Work backward from the last staffed reply period, accounting for appointments and other commitments. Staff being present does not necessarily mean they are available for campaign questions.

Consider when recipients are likely to read the message. An afternoon launch can produce evening questions, extending demand across the closure even when the first replies receive quick answers.

During closure: does waiting reduce customer value?

Ask what specifically becomes worse if the campaign waits. An offer relevant only during the closure may create genuine urgency. An internal preference to finish marketing work before a break does not.

A during-closure promotion deserves consideration when the intended action works without staff and the service gap is clear. If the offer expires before customers can obtain essential advice, disclosing the closure does not repair the mismatch. Change the deadline, narrow the offer or do not send it.

After reopening: is opening time actually available?

The first staffed period may already be committed to accumulated requests. Treat reopening as several possible windows rather than one launch timestamp.

When the offer remains useful later, a capacity checkpoint followed by a smaller send may be better than launching to everyone at opening. Postponement or cancellation remains an option when essential assistance and the deadline cannot be reconciled.

3. Use one accounting convention for every option

Measure distinct conversations requiring assistance, rather than individual messages. For this planning model, one capacity unit means enough work to resolve one such conversation within the window. A brief acknowledgement does not count as resolution. Reduce assumed capacity for more complex questions.

  • Existing demand: non-campaign conversations pending at the start, plus ordinary assistance demand arriving within the window.
  • Campaign demand: campaign conversations pending at the start or arriving by the window's end.
  • Usable capacity: conversations staff can resolve after other commitments.

Campaign headroom equals usable capacity minus existing demand. Unresolved campaign demand at the window's end equals campaign demand minus campaign conversations actually resolved. For a forecast, demand above headroom is a minimum unresolved balance, not something that disappears when the window closes.

Keep later arrivals separate. Projected campaign work at the next checkpoint equals unresolved demand at window end, plus new assistance demand afterward, minus intervening resolutions. Do not assume customers stop needing help unless there is a defensible basis for that assumption.

Also test timing. Divide the window into meaningful periods and compare arrival forecasts with capacity available after those arrivals. Unused capacity before a question arrives cannot answer it later. Require headroom for a higher-demand estimate plus a reserve, then confirm those resources overlap with expected questions.

Where timing records are unavailable, label the forecast uncertain and consider a smaller audience. A precise-looking total cannot compensate for an unsupported arrival assumption.

4. Worked example: compare four candidate schedules

All business details, schedules, counts and forecasts below are hypothetical, not Alactic customer results. A fictional homewares retailer closes Friday through Monday and reopens Tuesday at 09:00. Its bundle offer prompts suitability questions but can remain available until Thursday at 17:00. There is no customer-facing reason to promote it during closure. All times are retailer-local.

The full audience contains 240 recipients with campaign permission. Each full-audience option assumes 24 central-case or 32 higher-case conversations requiring assistance by the assessed window's end. Equal totals are scenario assumptions, not evidence that send times produce identical demand. The half-audience estimates of 12 and 16 use provisional proportional scaling.

For options A–C, assume all available headroom is used to resolve campaign conversations. Their unresolved balances are therefore optimistic minimums if arrival timing prevents full utilisation. No demand is assumed to disappear without assistance.

Hypothetical closure-planning decision table; paired figures show central / higher demand
Option and staffed windowCapacity calculationCampaign demand by window endUnresolved at window endNew demand after windowProjected campaign work and decision
A: Thursday 15:00; 240 recipients. Staffed until 17:00.16 capacity − 6 existing = 10 headroom24 / 3214 / 224 / 6 before Tuesday 09:0018 / 28 at Tuesday opening. Reject: insufficient capacity and long unsupported wait.
B: Sunday 10:00; 240 recipients. First staffed window Tuesday 09:00–12:00.30 capacity − 20 existing = 10 headroom24 / 32, assumed pending at opening14 / 22 at noon4 / 6 during Tuesday 12:00–13:0018 / 28 at Tuesday 13:00. Reject: unnecessary closure wait and insufficient reopening capacity.
C: Tuesday 09:00; 240 recipients. Staffed window 09:00–12:00.30 capacity − 20 existing = 10 headroom24 / 3214 / 22 at noon4 / 6 during Tuesday 12:00–13:0018 / 28 at Tuesday 13:00. Reject: reopening workload leaves insufficient headroom.
D: Tuesday 13:00; initial 120 recipients. Staffed window 13:00–17:00.25 capacity − 5 existing = 20 headroom12 / 160 / 0 if timing assumptions hold2 / 4 before Wednesday 09:002 / 4 at Wednesday opening. Conditionally approve, with 4 capacity units reserved beyond the higher forecast.

The model assumes no assistance between Thursday closing and Tuesday opening, during Tuesday's noon-to-13:00 break, or overnight after Tuesday closing. The checkpoints differ because each option creates a different unsupported interval; read the projected work alongside its timestamp and waiting period.

For A, the central calculation is 24 − 10 = 14 unresolved, then 14 + 4 = 18 at reopening. The higher case is 32 − 10 + 6 = 28. B and C reach the same totals through the same accounting, but at Tuesday 13:00 rather than opening. Their later arrivals do not replace the unresolved balance.

D also needs a timing calculation. Its hypothetical campaign capacity is 12 conversations during 13:00–15:00 and 8 during 15:00–17:00. In the higher case, 12 questions arrive early enough for resolution in the first period; another 4 arrive by 16:00 and can be resolved before closing. That leaves 4 units of reserve.

If those questions instead arrive just before 17:00, D fails despite its aggregate headroom. Any unresolved conversations must be added to the forecast of 2 / 4 overnight arrivals. The retailer accepts a maximum projected carryover of 4 because Wednesday assistance still precedes Thursday's deadline. This is a scenario-specific choice, not a universal acceptable wait.

5. Use a filled approval record to govern the selected send

The following record is a reusable operating artifact. Replace its values, owners and checkpoints for another closure; retain the demand definitions and arithmetic.

  • Selected schedule: Option D, Tuesday 13:00, initial audience of 120. Offer ends Thursday 17:00.
  • Owners: Campaign lead authorises the send; service lead confirms capacity and expected arrival timing.
  • Tuesday 12:30 gate: Verify capacity of 25 and existing demand no greater than 5 for 13:00–17:00. Require headroom of 20, covering higher demand of 16 plus reserve of 4.
  • Timing gate: Confirm the period-level capacity and arrival overlap used in the worked calculation. Reject a predominantly near-closing arrival forecast.
  • Accepted wait: No more than 4 projected campaign conversations awaiting Wednesday 09:00 assistance, counting both unresolved work and new overnight arrivals. State staffed availability clearly in the message.
  • Release scope: Authorise only the initial 120 recipients when preparation and messaging requirements are satisfied.
  • Tuesday 17:00 review: Record actual assistance demand, resolutions, arrival periods and projected overnight carryover.
  • Remaining audience: Wednesday 09:30 decision for a proposed 10:00 send supported through 14:00. Hypothetical capacity is 25; existing demand must be at most 5, including Tuesday carryover. Require headroom of 20 and a fresh arrival-overlap check. Tuesday approval does not transfer.
  • Fallback: Defer unsent recipients if either gate fails; reconsider the offer deadline rather than compressing supported response time.

Before sending, establish recipient permission and honour opt-outs. Keep campaign preparation, required template review and actual delivery as separate states. For WhatsApp Business Platform messaging, approved templates are used to initiate conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Template approval does not guarantee delivery. Automation needs a clear human escalation path; check the current WhatsApp Business Messaging Policy for precise requirements.

This record is a recommended operating design, not evidence of an Alactic scheduling or approval control. Check the workspace and current plan for availability. An authorised person can also apply the record manually.

6. Watch for failure cases the totals can hide

  • Unequal audience halves: the first segment may need more advice than the remainder. Replace proportional forecasts when segment characteristics differ.
  • Longer conversations: suitability questions may require several exchanges. Recalculate resolution capacity instead of treating each staff response as completed work.
  • Partial execution: if a send stops midway, establish which recipients were already sent messages before considering the remainder. Include their expected demand; do not restart the full audience blindly.
  • Offer changes: a stock restriction or checkout problem can turn a self-service journey into an assistance-dependent one. Pause the unsent portion while reassessing demand.

These are scheduling decisions about unsent messages. Handling individual waiting customers belongs in the service workflow, outside this planning tool.

7. Measure arrival timing and carryover, not just launch completion

Compare forecast and actual campaign conversations requiring assistance by the window's end. Record arrival periods separately: a correct total can conceal a schedule that leaves customers unsupported.

Reconcile the next checkpoint explicitly: unresolved conversations at close, plus later assistance arrivals, minus any intervening resolutions. Record whether reserve capacity was used and whether the accepted wait matched what occurred.

Finally, note whether execution preserved the planned staffed response time and whether the remaining send was authorised or deferred. Use those observations to change a specific assumption next time: audience size, assistance rate, arrival distribution, resolution capacity or the reopening window.

Campaign schedulingBusiness closuresService capacityWhatsApp operations

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