Back to all articlesCampaign scheduling

Schedule a Campaign Against Available Appointment Slots

Alactic Editorial9 min read

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

A campaign can go out on time and still arrive too late for the appointments it promotes. Empty calendar spaces are useful only when recipients can attend them and have enough time to request a booking.

Work backward from the appointment dates: subtract existing commitments and a reserve, estimate when requests might arrive, and size each wave against suitable capacity. Then refresh the calculation before authorising another send.

The worksheet below demonstrates that decision. All dates, quantities, audience characteristics, and outcomes are hypothetical. They are fictional planning examples, not Alactic customer results.

1. Count usable appointments, not empty spaces

Define one appointment offer: its duration, eligible staff or location, and intended dates. Combining unlike appointments can hide shortages. Ten short openings do not necessarily accommodate five longer appointments.

For each date, calculate:

Campaign capacity = gross capacity − confirmed bookings − other commitments − operating reserve

Other commitments include capacity held for existing customers or unavailable staff time not already reflected in the calendar. Avoid double subtraction: a blocked period already excluded from gross capacity is not another deduction.

The reserve is a management choice, not a universal percentage. It leaves room for ordinary demand and uncertainty. A larger reserve reduces campaign reach but makes the plan less dependent on every assumption being correct.

Finally, separate meaningful constraints. Someone available only after work cannot use a morning opening. Use date-and-time pools where needed, and verify service and staff suitability before treating appointments as interchangeable.

2. Map the delay between sending and requesting

The send date is not the demand date. Recipients may read later, check their schedules, and request an appointment after the earliest advertised time has passed.

Where records exist, estimate the interval from sending to receiving a booking request. Keep that separate from the notice customers need between requesting and attending. Without reliable history, use explicit planning assumptions and a smaller initial wave.

This fictional example uses the following assumptions:

  • Every request could consume one appointment; no allowance is made for requests that do not convert.
  • Requests arrive one to three days after sending: 25% on day one, 50% on day two, and 25% on day three.
  • Customers need at least one calendar day between requesting and attending.
  • Early-date recipients can attend the suitable time bands on June 13; some can also attend June 12.
  • Later-date recipients have supplied availability covering the suitable time bands on both June 15 and June 16.

A June 9 send therefore has a planning request window of June 10–12. Requests arriving on June 12 cannot use June 12 appointments under the notice assumption.

This delay distribution is a planning scenario, not an upper bound. Requests can arrive later, and demand can exceed the high scenario. Neither the worksheet nor a smaller wave protects against every possible response pattern.

3. Build the initial capacity worksheet

The fictional business has 12 standard appointments per day from June 12 through June 16. Most are already committed. Its campaign owner records the following snapshot before selecting a schedule.

APPOINTMENT-CAPACITY WORKSHEET — HYPOTHETICAL

Offer: one standard appointment per booking
Snapshot: June 9, 09:00
Minimum request-to-appointment notice: one calendar day

Date     Gross   Confirmed   Other holds   Reserve   Campaign capacity
Jun 12      12           7             1         1                   3
Jun 13      12           6             1         1                   4
Jun 14      12           5             1         1                   5
Jun 15      12           4             1         1                   6
Jun 16      12           3             1         1                   7
TOTAL       60          25             5         5                  25

Requests per recipient — planning scenarios:
Low: 5%     Planning: 8%     High: 12%

Selected waves, with request totals rounded upward:
Wave   Recipients   Low   Planning   High
A              33     2          3      4
B             100     5          8     12

Initial schedule:
A: June 9, 10:00 — 33 eligible recipients
B: June 11, 10:00 — up to 100 eligible recipients,
   conditional on a fresh capacity and suitability review

Accountable roles:
Campaign owner prepares the worksheet.
Booking lead verifies capacity and unresolved requests.
Operations manager authorises each wave.

The calendar contains 60 gross appointments, but only 25 are allocated to campaign demand. That distinction prevents a large-looking calendar from justifying an oversized send.

Calculate and round each wave separately. For example, Wave A's high scenario is 33 × 12% = 3.96 requests, rounded to four. These scenarios are planning inputs, not statistical confidence limits.

Deduplicate the audience and check existing bookings and opt-outs before each wave. A recipient should not enter Wave B simply because another appointment pool remains open.

4. Size Wave A against its tightest date constraint

A starting calculation is:

Wave ceiling = floor(usable capacity ÷ high-scenario request rate)

The critical choice is which capacity belongs in that formula. The early pool has seven appointments across June 12–13, but only four on June 13. Earlier respondents could take those four before later requests arrive.

A 40-recipient wave would produce five requests after rounding its high scenario upward. Availability across both dates would not establish that June 13 remains available for the last requests. Monitoring would reveal the shortage, not prevent it.

The selected decision is therefore 33 recipients: floor(4 ÷ 0.12) = 33. Its rounded high-scenario demand fits entirely on June 13, without depending on anyone accepting June 12.

WAVE A DATE-LEVEL CHECK — HYPOTHETICAL

Date     Suitable capacity   Treatment in decision
Jun 12                   3   Extra flexibility; not needed to justify wave
Jun 13                   4   Controlling capacity

Audience suitability:
All 33 recipients have supplied availability covering
these four June 13 appointments.

High-scenario demand: ceil(33 × 12%) = 4
Controlling-date capacity: 4
Decision: authorise 33, not 40

This resolves the allocation problem within the selected scenario: whether earlier respondents use June 12 or June 13, four total requests can fit. It does not establish spare capacity beyond that scenario. Later ordinary bookings, more requests, or requests arriving too late can still invalidate the plan.

5. Make Wave B conditional on demonstrated suitability

The second wave needs a fresh snapshot, not permission inherited from the original worksheet. In the hypothetical June 11 review, Wave A has produced three confirmed bookings: two on June 12 and one on June 13. One unresolved request is provisionally assigned to June 13.

Meanwhile, ordinary bookings have consumed two appointments on June 14 and one on June 15. The review records both remaining capacity and the audience's ability to use it.

PRE-SEND REFRESH — HYPOTHETICAL
Snapshot: June 11, 09:00

Early pool:
Date     Original   A bookings   Pending A holds   Remaining
Jun 12          3            2                 0           1
Jun 13          4            1                 1           2
TOTAL           7            3                 1           3

Later pool:
Date     Original   New ordinary bookings   Remaining
Jun 14          5                       2           3
Jun 15          6                       1           5
Jun 16          7                       0           7
TOTAL          18                       3          15

Wave B suitability check:
All 100 recipients have supplied availability for the
standard service during 13:00–17:00 on BOTH Jun 15 and Jun 16.
All 5 remaining Jun 15 slots fall within that band.
All 7 remaining Jun 16 slots fall within that band.
Suitable controlling capacity: 5 + 7 = 12.
Jun 14's 3 slots are extra flexibility, not relied upon.

Wave B high scenario: ceil(100 × 12%) = 12 requests
Suitable controlling capacity: 12
Headroom within controlling pool: 0
Additional Jun 14 capacity: 3, not counted as late-request headroom

Decision: operations manager authorises 100 recipients
for June 11, 10:00, based on this refreshed snapshot.
No automatic top-up wave.
Next reviews: June 12 and June 13.

Wave B's scenario request window is June 12–14. Even requests arriving on June 14 can use June 15 or 16. Because the audience supports both dates and their available time bands, all 12 high-scenario requests could fit there regardless of earlier requests consuming some of that capacity.

There is no headroom within this controlling pool. An owner wanting additional protection should choose a smaller wave. If the availability check were incomplete, authorisation would remain conditional, however many empty appointments appeared in the calendar.

Unresolved requests remain provisional commitments until resolved. An unanswered request is not free capacity merely because it has not become a confirmed booking.

6. Separate preparation, authorisation, and delivery

Record campaign preparation, template review where required, send authorisation, and actual delivery as separate states. A campaign intended for June 11 may no longer fit if delivery occurs on June 13. Review the timing of affected recipients rather than assuming the whole wave followed its planned schedule.

For WhatsApp campaigns, 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. That window opens or resets with a user message. Template approval does not guarantee delivery; consult the current WhatsApp Business Messaging Policy for precise requirements.

If template preparation or review remains incomplete at the capacity checkpoint, do not treat the campaign as ready. If automation assists with responses, provide a clear route to a human.

When using Alactic, check the workspace and current plan for relevant availability. This worksheet is a recommended operating practice, not evidence that capacity checks, reservations, or sending decisions execute automatically. Keep a named human authoriser for each wave.

7. Define pause conditions before sending

Phasing should preserve a decision, not merely divide a large list. Record what would stop or reduce the next wave:

  • Suitable capacity declines: recalculate using the controlling dates and time bands, not the original total.
  • Demand concentrates on a narrower window: replace the combined pool with that window's capacity.
  • Requests arrive later: remove appointments that no longer meet the notice requirement.
  • Delivery shifts: rebuild the request-window scenario using observed timing.
  • Unresolved requests accumulate: pause expansion until their likely capacity requirements are established.

For example, if Wave B's suitable June 15–16 pool falls to eight appointments, the hypothetical 12% high rate supports at most 66 recipients before additional headroom: floor(8 ÷ 0.12) = 66. Three June 14 openings would not solve a shortage for requests arriving on June 14.

If demand exceeds the scenario after sending, stop unsent waves first. Give respondents accurate remaining availability and offer only genuine alternatives. Individual rescheduling is a separate process; the campaign decision is whether more invitations should go out.

8. Improve the next worksheet with observable outcomes

Retain the filled worksheet alongside actual results. Compare requests per recipient sent, request delays, unresolved requests, and confirmed bookings. Keep delivery counts separate so delivery changes are not mistaken for changes in customer interest.

Record why each unmatched request could not use the advertised capacity: unavailable date, unsuitable time band, insufficient notice, or another specific constraint. Also record ordinary bookings that consumed capacity between preparation and sending.

Use those observations to change one planning input: send earlier when requests arrive too late, narrow the availability pool when time bands fail, or reduce wave size when demand exceeds suitable capacity. The useful outcome is a better scheduling decision, not simply a fuller calendar total.

Campaign schedulingAppointment 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