To prevent a restaurant campaign from reaching guests who opted out or already redeemed an offer, start with the intended audience and remove anyone who fails either check. Check permission for the specific marketing channel, then check redemption against the specific offer. Run those exclusions as close to sending as your software allows.
A guest appearing in your customer list does not automatically mean you can send them a promotion. And a guest who qualified when you built a list may have opted out or redeemed the offer by the time you send it. Ask your vendor when those changes take effect and what happens if they arrive after a message has entered the send queue.
Define the audience before adding exclusions
Start with a campaign that has a clear purpose. For example, you might want to email a limited-use dessert offer to guests who joined your email marketing list. Write down the channel, the offer identifier, the intended send time, and the redemption rule before selecting an audience.
A segment identifies who you want to reach. A suppression rule removes people who should not receive that message, even if they otherwise fit the segment. For this campaign, the basic decision is:
- Include a guest only if the restaurant has permission to send that person marketing through the chosen channel.
- Exclude a guest who has already redeemed the specific offer, if the offer is intended for one use.
- Hold a guest out when the relevant permission or redemption status cannot be determined reliably.
Keep email and SMS permission separate. An email address or phone number collected for an order, reservation, or service update is contact information; it is not, by itself, a reason to send a marketing offer. Likewise, opting out of one channel should not be silently treated as a change to another channel without a defined rule and an applicable basis for doing so.
Service messages have a different purpose from promotions. A reservation confirmation or order update should follow its own communication rules, rather than being bundled into the marketing audience. Ask your software provider how it distinguishes message types and routes opt-outs. Ask a qualified adviser about the requirements that apply to your restaurant and channels.
Frequency limits answer a different question: how often an otherwise eligible guest should hear from you. They do not replace a suppression rule for an opt-out or a redeemed offer. Set those exclusions first, then decide whether an eligible guest should receive this particular campaign now.
Apply the rules to a sample guest list
The following example is hypothetical. A restaurant plans an email campaign for a dessert offer called DESSERT-A. The offer is intended for one use per guest. For this exercise, an affirmative email marketing permission and a reliable record showing no DESSERT-A redemption are both required. An unknown status means hold, not send.
| Guest | Email marketing permission | DESSERT-A status | Decision |
|---|---|---|---|
| Alex | Yes | Not redeemed | Eligible for the campaign |
| Blair | Opted out | Not redeemed | Suppress: email opt-out |
| Casey | Yes | Redeemed | Suppress: offer already used |
| Devon | Unknown | Not redeemed | Hold: permission needs review |
| Emery | Yes | Unknown | Hold: redemption needs review |
The table shows eligibility for this email and this offer only. Alex still needs to meet any other audience conditions the restaurant sets. Blair stays out even though the offer is unused; Casey stays out even though email permission is present. Devon and Emery are not counted as eligible until the missing information is resolved.
The usefulness of the table depends on the underlying records. Ask where opt-outs are stored, which redemption events are included, and whether the campaign tool can match those events to the right guest. An offer redeemed at the counter may need a different recording path from one redeemed in an online order. If the records do not meet, an apparently unused offer may have been used elsewhere.
Also decide what one use per guest means in your operation. A guest might have two email addresses, share an address with a household member, or use a different identifier at checkout. Ask the vendor how duplicate records are identified and whether staff can review a match before changing it. Do not merge records merely because names look similar.
If your offer can be used more than once, replace the one-use rule with the actual limit and ask how the system counts uses. A loyalty balance is not the same thing as an offer redemption: a guest may have points without having redeemed DESSERT-A. Review your loyalty workflow alongside the offer rules so staff know which event should trigger suppression.
Check changes immediately before sending
A list can be correct when it is prepared and wrong later. A guest might opt out after you schedule a campaign, or redeem the offer during the interval before the send. The key buying question is whether the system evaluates eligibility when the audience is selected, when the campaign is queued, or again before each message is sent.
Ask the vendor to walk through both changes: an email opt-out arriving after scheduling, and a DESSERT-A redemption recorded shortly before sending. For each, ask when the change becomes visible to the campaign, whether it removes a queued recipient, and what staff can see in the send report. Also ask what happens if the event arrives after a message has already been handed off for delivery. A restaurant should not assume it can recall a message at that point.
Before a live campaign, practice with fictional records in a simulation or a test environment configured so it cannot send guest messages, take payments, or dispatch couriers. Do not use actual guest contact details. Ask a staff member to record a simulated opt-out for one eligible test record and a simulated redemption for another, then recalculate the audience. Both records should be excluded under the example rules.
Check the result against the intended audience, not just a total count. If two records disappear, confirm that they are the two changed records and that the reason for each exclusion is visible. Try an unknown redemption status as well; it should remain on hold under the example policy. If the tool cannot show these decisions in a safe simulation, ask the vendor how it can demonstrate the workflow without sending messages or triggering real transactions.
A simulation checks the configured logic; it is not proof of how every live event will arrive. If you later run a live service pilot, keep it separate: use an approved campaign and audience, assign a staff owner, and monitor actual results and exceptions. A real campaign can send real messages, so do not call it a practice simulation. If the software cannot recheck a queued audience, consider building the list closer to send time and having the owner review late changes. That reduces the gap but does not guarantee every late event is caught.
When comparing campaign workflows, ask for a clear explanation of scheduling, suppression timing, reporting, and export options. Confirm whether staff can pause or cancel a scheduled send and what happens to messages already in the queue.
Give exceptions an owner
Assign one person to approve the audience and another available contact to handle a problem if the owner is away. In a small restaurant, those roles may sit with a manager and the owner. Record who can pause a send, who can correct a guest record, and where staff should report a disputed redemption or opt-out.
Use a short pre-send checklist:
- Confirm the offer, channel, audience, and intended send time.
- Review opt-outs and the redemption source used for this offer.
- Check the count and reasons for exclusions and holds; investigate an unexpected change.
- Confirm when the last eligibility check occurs and who can pause the campaign.
- Save an appropriate record of the decision and review exceptions after the send.
For an exception, record the issue and its resolution without putting unnecessary guest details into a shared staff note. If a guest says they opted out but still received a promotion, stop any affected upcoming send while the owner checks the record, timing, and channel. Correct the underlying issue before restarting. Do not assume that removing the guest from one exported list fixes every future campaign.
Review local requirements with a qualified adviser, including how permission, opt-outs, records, and service messages should be handled for your operation. Then turn that advice into a staff procedure and vendor questions. Ask how consent changes are recorded, who can access or export them, and how corrections move between systems. A written process is useful only if the people sending campaigns can follow it during a busy shift.
Next, take one upcoming offer and map its permission source, redemption source, and exclusion timing. Then compare the workflow and current availability with Fleksa, using the same questions you would ask any provider.
Frequently asked questions
Is a suppression list the same as an audience segment?
No. A segment selects guests who fit the campaign; a suppression rule removes guests who should not receive it. A guest can fit the segment and still be excluded because they opted out or redeemed the offer.
Should a redeemed offer suppress every future campaign?
Not necessarily. Tie the exclusion to the offer and its rules. A guest who used one dessert offer may still be eligible for a different promotion if they have the required channel permission and meet its conditions.
What if an opt-out arrives after a campaign is scheduled?
Ask whether the software rechecks permission before sending and can remove a queued recipient. If it cannot, identify the available pause and review steps, and avoid assuming that an already delivered message can be recalled.
