When an unexpected closure affects a scheduled campaign, first stop any affected messages that have not yet gone out. Then check what has already been sent, decide how guests can use or replace the offer, and assign one person to approve the restart. Do not assume that closing online ordering or reservation availability also stops marketing messages.
The right control depends on the campaign tool and how far the send has progressed. A pause may hold a message for later; cancellation may remove it from the queue; an edit may change its content or timing. Ask your vendor exactly what each action does, including whether messages already being processed can still go out.
List the messages and offers affected by the closure
Start with the service period, not just the campaign name. A lunch promotion may be obvious, but an automated welcome message, loyalty reminder or scheduled SMS could also invite guests to visit while the doors are closed. Check each location if your restaurant has more than one.
Make a quick list of scheduled sends, recurring campaigns and offers guests may already have received. For each one, record the channel, audience, send time, location, offer terms and the person who can change it. Include messages in any separate tool or agency account; one dashboard may not show the entire queue.
Hypothetical example: A restaurant normally opens for dinner at 5 p.m. A water outage forces the manager to close for that evening. An email promoting a $4 appetizer discount is scheduled for 3 p.m., an SMS reminder is scheduled for 4 p.m., and a lunch email containing the same offer was sent earlier. The discount is valid only that evening. No other service is affected.
The expected result is straightforward: neither scheduled message should invite guests to the closed dinner service. The earlier email cannot be unsent, so the manager also needs a way to handle guests who saw it. The table turns those expectations into a practical check.
| Item | Action to check | Pass | Fail |
|---|---|---|---|
| 3 p.m. email, not yet sent | Pause or cancel the affected send | Status shows it will not send at 3 p.m. | It remains scheduled or its status is unclear |
| 4 p.m. SMS, not yet sent | Stop it separately or confirm it is included in a campaign-level stop | Status shows no send at 4 p.m. | The reminder remains queued |
| Earlier lunch email | Prepare a response for guests who have the offer | Staff have an approved response and know its limits | Staff do not know what to tell a guest |
| Dinner-only discount | Choose a replacement or exception and verify how staff will apply it | A simulated redemption follows the approved decision | The test produces a different outcome or no clear answer |
Record the time and the person who made each change. If a status is ambiguous, contact the vendor or agency and use another available control to prevent the send. A screen that still says “scheduled” is not proof that the message has stopped.
Choose between pausing, canceling and editing
Use a pause when the message may still be suitable after reopening and the tool clearly holds it until an authorized person releases it. Before choosing that option, ask whether the original send time stays attached and what happens if that time passes. A paused dinner promotion should not automatically go out at an unsuitable hour when someone resumes the campaign.
Cancel when the message is no longer useful or when you cannot safely confirm how a pause works. For the hypothetical dinner-only SMS, cancellation is a sensible choice if the restaurant will miss the entire service. The manager can create a new message later if there is a reason to contact guests. Ask whether cancellation affects only this occurrence or also removes a recurring series.
Edit when the audience should still hear from you but the details need to change. A closure notice may be more useful than a promotion, provided the manager has accurate information and permission to use the channel for that message. Change the offer terms and call to action as well as the headline. A corrected opening time beside an old “visit tonight” button can still confuse guests.
Editing is not necessarily a substitute for stopping a send. Ask whether changes apply to messages already queued or being processed, whether an approval step is required, and whether the revised version can be previewed before release. If the send is too close to verify, stop it first where possible and prepare the correction separately.
Also check dependencies. A promotional email may point to an ordering page, a code or a landing page that still describes the closed service. Coordinate the campaign decision with whoever controls those pages and the POS. Your restaurant management software may be part of the operational workflow, but confirm which changes must be made in each system.
Handle messages already sent and test redemption
A sent message is a different problem from a queued one. You cannot rely on guests seeing a correction before they travel or attempt to use the offer. Decide what staff should say if a guest calls, arrives or asks to redeem it after the closure.
For the example, the manager could approve honoring the $4 appetizer discount during the next dinner service, subject to the restaurant being open and the guest presenting the original offer. That is a business decision for this hypothetical restaurant, not an automatic property of the code. The manager should also decide whether the offer can be applied manually if the original code expires, who can authorize it and how staff should record the exception.
Before announcing an extension, ask the vendor how an existing code's dates and conditions can be changed, whether the change affects other locations, and what staff will see at checkout. If the system cannot support the chosen terms, select a process staff can actually carry out. A promise to extend an offer is not useful if the team has no approved way to recognize it.
Run a simulation using a test record or a written walk-through. Do not send a real guest message, take a real card payment or dispatch a courier. Have one staff member play the guest and another follow the approved response. Use a test environment if available; otherwise, walk through the screens and decision steps without completing a live transaction.
The simulation passes if staff can identify the original offer, explain the new terms, find the authorized way to apply the discount and identify who handles an exception. It fails if they offer different terms, cannot determine whether the code is usable, or need an unapproved workaround. Record the failure and resolve it before telling guests what they can expect.
Keep the economics separate from the service decision. A $4 discount is the face value of this hypothetical offer, not the full cost of the promotion. Product costs, other variable costs and any fixed campaign costs are excluded; the example assumes no exception-handling cost. If you are deciding whether to substitute loyalty value instead, distinguish points displayed to a guest from a reward they can actually redeem. The loyalty reward cost guide offers a framework for that separate calculation.
Assign the correction and set a restart gate
One person should own the closure response, even if others perform individual tasks. That owner confirms which campaigns stopped, approves the guest-facing message and keeps a short record of unresolved items. Assign a backup in case the closure continues into the next shift.
Give the owner a simple contact list: the person with campaign access, the person responsible for website and ordering information, the shift lead and any outside agency. Access matters during an emergency. A manager who can see a campaign but cannot stop it needs a named escalation contact, not a shared login that nobody can reach.
For the hypothetical closure, the shift lead can brief staff on the $4 offer, while the campaign owner confirms the two scheduled sends are stopped. A correction should state the affected service, what is known about reopening and how the offer will be handled. Avoid promising a reopening time until the person responsible for the restaurant has confirmed it. Use channels appropriate to the audience and the permissions you have; access to a contact list alone does not establish permission to market to it.
Set a restart gate before anyone resumes a paused campaign. The owner should confirm that the restaurant can serve the promoted offer, opening information is current, links and codes lead to the intended experience, and the revised audience and send time are appropriate. Preview the final message and obtain the required approval. If any item is unresolved, keep the campaign stopped or cancel it rather than guessing.
After the simulation, a live service pilot is a separate decision. If you use one after reopening, agree on its scope, staff coverage and stopping point beforehand. It involves actual operations, unlike the practice check, so do not treat a simulated result as proof that every live guest interaction will work.
Next, take one upcoming promotion and complete the four-row worksheet with your own channels, offer terms and responsible staff. Then compare your requirements with Fleksa's restaurant marketing automation and confirm current availability and the pause, edit and cancellation workflow before choosing it.
Frequently asked questions
Does closing reservations stop scheduled marketing?
Do not assume it does. Check each campaign queue and any separate marketing account. Ask the vendor whether a closure setting affects scheduled messages, recurring sends or neither.
Can I change a promotion after it has been sent?
You cannot change the copy already delivered to a guest. You may be able to change the underlying offer or issue a correction, depending on the tool and your approved process. Verify the terms staff can actually honor.
When should a paused campaign resume?
Resume only after the promoted service is available, the message and offer are accurate, and an authorized person has reviewed the audience and send time. If the original promotion no longer makes sense, cancel it and consider a new one.
