Before approving a guest campaign, a manager should check four things: the audience, the offer, every link, and the sender identity. Then preview the message as a guest would see it and decide who can authorize the send. If any essential detail is wrong or uncertain, stop the campaign until it is corrected and checked again.
A good preview is more than a spelling check. A message can look polished and still reach the wrong guests, advertise an offer staff cannot honor, or send customers to an expired page. The manager’s job is to connect the message to what will happen at the restaurant when guests respond.
Decide who owns the final send
Name one approver for each campaign. For a single restaurant, that may be the general manager. For a group, it might be a marketing lead who checks the message with each participating location. The person writing the campaign can prepare the sheet, but someone accountable for the offer should make the final decision.
Agree on what approval covers. The approver should see the actual audience rules and final message, not just a summary such as “send the lunch offer to regulars.” They should also know when the message is scheduled and whether it can still be stopped after approval. Ask the vendor how scheduled sends are paused or canceled and what happens if a send has already started.
Separate access to a guest’s contact details from permission to market to that guest. Before sending, have the responsible person confirm that the intended audience meets your restaurant’s applicable permission and opt-out rules. Ask a qualified adviser when you need help interpreting those obligations.
If the audience, offer, or timing changes after approval, treat the changed version as a new approval. A small edit can have a large effect: changing an expiration date may alter what the dining room has to honor all weekend.
Use a pre-send approval sheet
Record the campaign name, planned send time, preparer, and approver above the sheet. The table below gives the manager a practical minimum check. Add a location or channel check when the campaign covers more than one restaurant or uses both email and SMS.
| Check | What to inspect | Pass condition | Stop if |
|---|---|---|---|
| Audience | Selection rules, locations, estimated count, and excluded contacts | The count and rules fit the intended guests; exclusions are applied | The count is unexpected or permission status is uncertain |
| Offer | Benefit, dates, eligible items, locations, and restrictions | The message matches the offer staff can honor | Terms conflict or the restaurant cannot fulfill them |
| Links | Each button, text link, and opt-out link | Each opens the intended destination and the opt-out path works | A link fails, points to the wrong page, or requires an unintended action |
| Sender | From name, reply address, subject, and guest-facing identity | Guests can recognize the restaurant and replies have an owner | The identity is misleading or replies go unattended |
The estimated audience count is a sense check, not proof that every contact belongs. If a neighborhood campaign unexpectedly includes guests from another location, inspect the selection rules before approving. Ask whether the tool shows exclusions and duplicate contacts, and whether the estimate can change between approval and sending.
For the offer, check the guest’s full path. Can the host explain it? Can the cashier identify eligible items? If a code is involved, who will confirm that it is active for the stated dates and locations? Avoid vague terms such as “selected items” unless the message tells guests where to find the selection.
For links, inspect the destination as well as the button label. An “Order now” button should lead to the intended ordering destination, not merely a home page where a guest must hunt for it. Check the mobile view, since a layout that reads well on a wide screen may hide the important terms on a phone.
Finally, give the sender identity an operational check. If guests can reply, designate someone to monitor the inbox during and after the campaign. A familiar restaurant name is not much help if questions and complaints disappear into an unattended address.
Work through a hypothetical preview
Suppose a neighborhood restaurant plans an email offering a free iced tea with an eligible lunch entrée, Monday through Thursday next week. The offer is for dine-in at one location, while supplies last. The marketing coordinator prepares the message; the general manager is the approver.
The intended audience is guests associated with that location who are eligible to receive marketing emails. The coordinator expects about 600 recipients and sees an estimated 580 after the selected exclusions. That difference is not automatically a problem. The coordinator checks the rules and finds that the estimate excludes contacts who opted out. The manager still needs to confirm the audience selection before signing off.
The draft subject says “Lunch comes with iced tea next week.” In the body, the coordinator includes the eligible days, dine-in restriction, participating location, and supply limit. A button labeled “View lunch menu” points to the current menu. The sender name is the restaurant’s name, and the reply address goes to an inbox monitored by the front desk.
For the preview, use the vendor’s preview or a simulation that does not send a guest message, charge a card, or dispatch a courier. The coordinator opens the rendered message on a phone-sized and desktop view and checks the menu destination without placing an order. The expected result is that the terms are readable, the menu is current, and each link leads where its label says it will. The coordinator also checks the opt-out path without submitting an actual guest request.
Now suppose the preview shows Friday in the offer text, while the manager intended the offer to end Thursday. That is a stop condition. The coordinator corrects the text and prepares a new preview; the manager checks the revised message and confirms that staff can honor the final terms. The next action is recorded as “manager to approve revised version,” not “ready to send.”
Once the message passes, record the approved audience rules and estimate, final subject and offer terms, link destinations, sender and reply details, scheduled time, approver, and approval time. Store the record where the team can find it if a guest later asks what was advertised. This example is a workflow, not a claim that any particular product provides these controls.
Test the approval workflow before buying
Ask vendors to demonstrate the actual steps with a sample campaign. Use a fictional audience and a simulated preview. Do not use real guest contact details or trigger a real send during the practice. Your goal is to learn what the software shows the approver and what the team must check outside it.
- Build the audience. Ask to see the selection rules, estimated count, exclusions, and available permission information. Pass if the manager can understand who is included and identify uncertainty before approval. If the tool cannot show a needed detail, decide whether a dependable manual check is practical.
- Preview the final message. Ask how to inspect the subject, sender, offer terms, and destinations on different screen sizes. Pass if the approver can review the version intended for release and identify each destination without sending to guests.
- Change an approved detail. Simulate changing the offer after approval. Pass if your team can identify the change and apply its rule for renewed approval, whether that control is built in or documented manually. Ask whether the product records version changes and who approved them.
- Handle an exception. Simulate a broken menu link or an unexpectedly large audience. The expected result is a stopped campaign, a named person fixing the issue, and a fresh check before approval. Ask how to pause a scheduled send and what recovery options exist once sending begins.
- Get help. Ask support how quickly your team can reach someone during a scheduled campaign and what information support needs to investigate a problem. Compare that answer with the hours when your restaurant actually sends messages.
A manual approval sheet can work for a small team with occasional campaigns, provided someone owns it and saves the final version. It becomes harder to manage when several locations change offers at once. A tool with visible approval history may reduce that coordination burden, but ask to see the history and change controls rather than assuming they exist.
For a live service pilot after the simulation, use your normal approved guest-marketing process and a clearly defined small audience. Confirm the real offer, staffing, and stop procedure first. A live pilot has real consequences; it is not the same as a no-send preview.
Consider how the campaign fits the rest of your operation. A restaurant management system may be part of the workflow, but ask how staff will verify an offer at the point of service. If a campaign includes a loyalty benefit, use the loyalty reward cost guide to examine the economics separately from the message approval.
Next step: Take the approval sheet and one sample campaign to your vendor demonstration. Compare your requirements with Fleksa’s restaurant marketing tools, and confirm which preview, approval, and send controls are available for your setup.
Frequently asked questions
Who should approve a restaurant email campaign?
Choose one person accountable for the final send, usually a manager or marketing lead. They should confirm the audience and message with the location responsible for honoring the offer.
Is a preview enough to approve a campaign?
No. A preview helps catch layout and wording errors, but the approver also needs to check audience rules, permission status, link destinations, sender identity, and whether staff can deliver the offer.
What should happen if an offer changes after approval?
Stop the scheduled campaign if necessary, update the message, and have the approver check the changed version. Ask the vendor how cancellation works if sending has already begun.
