To prevent overlapping campaigns, put every promotional message for a guest through one shared decision: Is the guest eligible, has the guest reached the contact limit, and is a higher-priority message already scheduled? Keep essential service notices outside the promotional cap, but do not use those notices to carry extra offers.
A restaurant email frequency cap works best when it covers more than the newsletter. A birthday offer, a win-back email and a manager’s weekend promotion can all be reasonable on their own. Together, they can make one guest feel chased. The goal is to decide which message wins before the first one goes out.
1. Inventory every message that can reach a guest
Start with a list of messages, not a list of marketing tools. Include automated journeys, one-off campaigns, loyalty reminders and any messages a staff member can send from another system. For each, record the channel, trigger, audience, scheduled time, owner and reason for sending.
Look for these common points of overlap:
- A welcome series after a guest joins a marketing list.
- A birthday or loyalty offer triggered by a date or account activity.
- A win-back campaign for guests who have not ordered recently.
- A weekly special sent manually to a broad audience.
- An order confirmation, pickup update or reservation notice.
- A feedback request sent after an order or visit.
Ask the person responsible for each message to show where it is scheduled and how it can be paused. A manager may know about the Friday email but not the automated offer that runs on Thursday. If a delivery partner, reservation provider or separate email tool also contacts guests, include it in the inventory and ask who controls those messages.
Then decide how the systems identify the same guest. An email address in one tool and a phone number in another do not automatically form a single contact history. Ask vendors how they match records, handle duplicates and make recent sends visible across channels. If messages cannot be coordinated across tools, use a shared calendar and narrower audiences as an interim control; do not assume the software will enforce a restaurant-wide limit.
Having a guest’s contact details is not the same as having permission to send marketing. Record the guest’s marketing choices by channel and make those choices part of the eligibility check before applying a frequency cap.
2. Rank messages and choose the window
Separate operational notices from promotions. An order confirmation or a change to a reservation communicates information the guest needs for a transaction. A discount, event invitation or loyalty offer is promotional. A feedback request deserves an explicit decision: if its purpose and permission are unclear, do not quietly treat it as an essential notice to bypass the cap.
For promotions, choose both a channel limit and a total limit. For example, a restaurant could allow no more than one promotional email in a rolling seven-day window and no more than two promotional contacts across email and SMS in that same window. The total limit stops a guest from receiving the maximum on each channel independently.
A rolling window moves with the send. If a promotional email goes out on Tuesday at 10 a.m., another email becomes eligible after the following Tuesday at 10 a.m. A calendar-week rule is easier to explain, but it can permit a Sunday message followed by another on Monday. Ask which window the software actually supports and whether the clock uses the scheduled time or the actual send time.
Set a priority order for campaigns that compete. A time-sensitive birthday offer might rank above a general weekly special; a welcome message might rank above a broad win-back offer. There is no universal order. Write down the business reason and decide who can change it. Also decide whether a blocked message expires or waits. A Friday dinner offer should not be delivered the following Monday simply because a slot opened.
Useful service notices can continue when a promotional cap has been reached. Keep their content focused on the order or reservation. Adding a discount to an operational notice makes the distinction harder for staff and guests to understand; have a qualified adviser review any questions about consent or message treatment.
3. Use a shared-cap worksheet to resolve conflicts
The following example is hypothetical. Assume one guest has opted in to both promotional email and SMS. The restaurant’s rule is one promotional email and two promotional contacts total in any rolling seven-day window. Essential service notices do not count toward those limits. All times below fall within the same seven-day window.
| Planned message | Priority and channel | Decision under the rule |
|---|---|---|
| Tuesday: order confirmation | Service email | Send as an operational notice; promotional count stays at zero. |
| Wednesday: birthday offer | High-priority promotional email | Send; promotional count becomes one email and one contact. |
| Thursday: weekend special | General promotional email | Block because the email limit is already reached; expire it after the weekend. |
| Friday: loyalty reminder | Promotional SMS | Send if still eligible; promotional count becomes one email and two total contacts. |
| Saturday: win-back offer | Promotional SMS | Block because the two-contact total is reached. |
The table shows why a per-channel rule alone is not enough. After Wednesday’s email and Friday’s SMS, the guest has received two promotions. A separate SMS-only cap might still allow Saturday’s offer, even though the shared total says to stop.
Now change one input: suppose the restaurant wants a quieter schedule of one promotional contact total in seven days. Wednesday’s birthday email uses the only slot. Both SMS promotions are blocked, as is Thursday’s email. The order confirmation remains eligible because it is a service notice. That choice reduces overlap but also means the loyalty reminder needs to wait for a later eligible window or be dropped.
Write the rule in an order staff can follow:
- Check the guest’s channel-specific marketing choice and any suppression.
- Classify the message as operational or promotional.
- For a promotion, check the rolling channel and total limits against actual recent sends.
- If several eligible promotions compete, select the highest-priority one.
- Expire or reschedule the rest according to a deadline set for each campaign.
Specify what happens when two campaigns are scheduled at the same time. The safest rule is to select the winner before either is released, rather than rely on which system happens to send first. Ask whether the platform can make that decision atomically, how it handles retries, and whether a cancelled or failed send counts toward the limit. If it cannot coordinate simultaneous sends, stagger schedules and have one owner review the overlap.
4. Check the workflow before a live campaign
Turn the worksheet into a simulation with sample guest records and a non-sending test mode or equivalent safe setup. The simulation should not send a guest message, take a payment or dispatch a courier. If a tool cannot safely simulate the complete workflow, review its scheduling and suppression controls with the vendor instead of triggering a real transaction.
Walk through a guest who qualifies for two campaigns, a guest who has opted out of one channel, and a guest with an order notice due after reaching the promotional cap. Check the planned outcome against the rule. Also check a message that becomes stale while waiting and a duplicate guest record that could otherwise receive the same offer twice.
Before a live service pilot, agree on the audience, schedule, staff owner and stop condition. A live pilot is a real send to eligible guests, not a simulation. Keep it small enough that the team can review the results and pause future messages if the rules are not working as intended.
Ask what staff can see without exporting a full guest list: recent sends, scheduled campaigns, suppression reasons, opt-outs and failed messages. A useful record explains why a guest did or did not receive a campaign. Also ask how quickly an opt-out is reflected in pending campaigns and in any other tool used to send messages.
Fleksa’s restaurant marketing automation page describes email and SMS campaigns, segmentation, promo codes and loyalty tools. Ask for a demonstration of the shared cap, priority and suppression rules you need; do not assume that every rule in the worksheet is available. If your restaurant ordering system or a separate provider sends service notices, include those messages in the discussion so staff know which system owns each send.
5. Monitor the effect and adjust deliberately
Review opt-outs alongside campaign volume, not in isolation. A rise after a busy promotional week is a reason to inspect the schedule and audience, not proof that one particular message caused the change. Compare similar periods where practical, and note menu changes, holidays and changes to the guest list that could affect the result.
Track a short set of operational measures: promotions sent per guest, messages blocked by the cap, opt-outs by channel, expired campaigns and service notices that failed. Check whether valuable time-sensitive offers are routinely blocked by lower-priority campaigns. If they are, change the priority or schedule rather than simply raising the cap.
Review the rule with the people who create campaigns and manage guest records. Decide who can override it, how an override is recorded and when it expires. A manager may have a good reason to make an exception, but unrecorded exceptions quickly turn a shared limit into a suggestion.
For loyalty promotions, consider the offer as well as the send schedule. The guide to calculating loyalty reward cost can help you assess the reward separately from the contact rule.
Next step: List the next two weeks of planned and automated messages, apply the worksheet to one sample guest, and compare the resulting workflow with Fleksa. Bring your cap, priority order and suppression questions to the conversation.
Frequently asked questions
Should order confirmations count toward a promotional cap?
Generally, keep essential order and reservation notices separate from promotional limits so guests can receive information they need. Keep promotional content out of those notices and get qualified advice when message classification or consent is unclear.
Should email and SMS have separate limits?
They can have separate channel limits, but add a shared promotional limit if you want to control the total number of contacts. Check the guest’s marketing choice separately for each channel.
What happens to a campaign blocked by the cap?
Set an expiry or a rescheduling rule before launch. Drop an offer when it will no longer be relevant, and make sure any queued message is checked again for consent and eligibility before sending.
