A phone number or email collected for a reservation gives you a way to contact a guest about that booking. It does not, by itself, tell you whether the guest wants promotional messages. Keep the booking contact, the reason for each message, and the guest’s marketing preference as separate pieces of information.
Start with a simple operating rule: use contact details for the reservation workflow you have established, and hold a guest out of promotional audiences unless you have an appropriate, recorded basis to include them. Ask qualified counsel to help set that basis for each channel and jurisdiction. Your staff should not have to guess from a completed booking form.
This audit is about the quality and movement of booking data, not how often to send campaigns. Even a carefully timed campaign can reach the wrong person if the audience was built from a list of everyone who ever booked.
Map contact details, service messages and preferences
List every way a guest can book: your website, phone, walk-in, a discovery platform and, where available, a Google booking path. For each source, note where staff enter the contact details and where the record ends up. A single guest may appear in more than one tool, so a form review alone is not enough.
Separate the fields into three groups:
- Booking information: guest name, contact details, local date and time, party size, booking status and relevant requests.
- Service communication: the channel used for booking-related messages and the status of messages such as confirmations or changes.
- Marketing preference: the guest’s choice for each promotional channel, when and where that choice was recorded, and any later change.
A confirmation that states the reservation time serves a different purpose from an email advertising next month’s tasting menu. A reminder can also become harder to classify if it includes a substantial promotional offer. Have counsel review mixed-purpose templates rather than assuming the booking context settles the question.
Make the owner’s choice explicit: should a guest with no recorded marketing preference enter a campaign list? A cautious audit setting is no. Mark that record as unknown, not as a yes or a no invented by staff. A recorded decline is different from an unknown choice; preserve that difference so a later import does not turn either into permission.
Record the source and time of a preference where your tools allow it. Also save the wording or form version associated with the choice, or keep a reference to it. If a guest later asks why they received a promotion, a bare checkbox with no context is difficult to explain. Ask vendors how these details are stored and whether they travel with an export.
Use the following worksheet to make decisions before building an audience. Its entries are hypothetical operating assumptions, not legal conclusions. The last column gives the action staff would take under those assumptions.
| Record or message | Hypothetical input | Audit decision |
|---|---|---|
| Booking contact | Email entered for a dinner reservation | Keep with the booking; do not treat the address alone as a marketing choice. |
| Service confirmation | Time, party size and restaurant address only | Use the established booking workflow; keep the template separate from promotions. |
| Email promotion | Guest declined promotional email | Exclude from the email campaign audience and preserve the decline. |
| Text promotion | No text marketing choice recorded | Mark unknown and hold out of the text audience pending an appropriate basis. |
| Preference change | Guest later updates a choice | Record the change and check that connected campaign tools receive it. |
The worksheet makes two distinctions that matter at the counter: contact information is not a preference, and a choice for one channel should not automatically be copied to another. Your actual settings and templates need review against the rules that apply to your restaurant.
Work through a guest who declines promotions
In this hypothetical example, Maya books a table for dinner through a restaurant’s website. She provides an email address for the booking, declines promotional email, and makes no text marketing choice. The restaurant uses an email confirmation that contains only booking details. Assume counsel has approved this service-message workflow for the restaurant’s circumstances.
The correct operating result under those assumptions is specific:
- Keep Maya’s email with her reservation so the restaurant can use the approved booking workflow.
- Send the booking-only confirmation through that workflow.
- Record her promotional email choice as declined, including its source and time if the system supports those fields.
- Keep her out of promotional email audiences. Mark text marketing as unknown rather than copying the email decline or creating a text opt-in.
- If Maya changes her choice later, update the authoritative record and check downstream audiences before the next campaign.
Now suppose the dining room changes Maya’s reservation time. Staff need a way to communicate the change without interpreting her promotional decline as a request to cancel the booking or erase all contact details. The service workflow and marketing preference must remain distinguishable on the staff screen and in any export.
Also consider the reverse mistake. A staff member sees Maya’s email in the reservation list and adds every address from that list to a promotion for a holiday menu. The booking record may be accurate, but the audience decision is not. The fix is not merely to remove Maya from one campaign; identify the list-building step that ignored the decline and check whether the same process affected other records.
For a safe practice run, use a fictional guest and a sandbox or other non-sending environment. Configure the exercise so it cannot send a guest message, charge a real card or dispatch a courier. Review the intended confirmation and campaign audience on screen. A simulation checks the logic and fields; it does not prove that a live integration will behave the same way.
If you later run a live service pilot, use an authorized test account and a deliberately approved process. Review actual delivery and suppression results with the relevant vendors before expanding the audience. Do not mistake a simulated screen result for a live delivery check.
Trace exports, suppression and corrections
A preference can be correct in the booking tool and wrong in the marketing tool. Draw a short map showing where records originate, which tool holds the preference your team relies on, and every destination that receives contact data. Include manual spreadsheet downloads as well as connected software. For each arrow, name the person responsible for checking it.
Ask what happens when a guest declines or changes a preference after an export. Does a connected audience receive an update, and how quickly? If a staff member downloads a new list, can an older file still be used? A suppression list is useful only if the campaign process checks it against the audience that will actually be sent.
Decide which record wins when two systems disagree. For example, if the booking system shows a later decline but an older spreadsheet shows an opt-in, pause the promotional send while the conflict is resolved. Keep the date, source and correction together. Do not let a newly imported blank field overwrite a known decline without a deliberate rule.
Run these checks with fictional records in a non-sending environment:
- Export or otherwise inspect the permitted test data and confirm that contact details, channel, preference status, source and change time are represented as expected.
- Check that a declined guest is absent from the promotional audience while the reservation record remains available for the approved service workflow.
- Change the fictional preference and inspect each destination that should receive the correction.
- Test a duplicate record and an older import. Confirm that neither creates an unsupported permission or removes a newer decline.
- Document who resolves exceptions, how the correction is confirmed, and where staff should report a mismatch.
If a vendor cannot show you a field or workflow, ask how its customers handle that gap. Do not assume that an integration transfers preference history just because it transfers names and email addresses. Similarly, ask whether you can inspect and correct a preference without deleting the reservation itself.
Booking source matters here. OpenTable offers reservations, restaurant operations and a diner discovery network. A direct booking through a restaurant website is a different path. For either source, ask what preference information you can access, what you can export, how booking-channel attribution is retained, and which fees apply. Do not assume the same data or permissions follow every booking.
If you are changing systems, reconcile booking counts and preserve booking identity, local date and time, party size, status and appropriate special requests using an authorized, supported method. Assign one cutover owner and separately verify how preferences and suppressions move. A rehearsal reduces uncertainty; it does not guarantee uninterrupted service or that every order or booking will survive a change.
Set rules with counsel and train the team
Service-message and marketing rules can depend on the guest’s location, the channel, the wording used, and the relationship with the guest. Ask qualified counsel to review your actual forms, message templates, data flows and retention practices. This is an operational audit, not a substitute for legal advice.
Bring counsel concrete materials rather than a broad question about whether your system is compliant:
- Screenshots or copies of booking forms for each booking source, including the wording and default state of any marketing choice.
- Examples of confirmations, reminders, change notices and mixed-purpose messages that include an offer.
- A map of where contact information and preferences travel, including spreadsheets and outside vendors.
- Your proposed treatment of unknown, declined and changed preferences for each channel.
- The process for correcting records and handling guest requests across connected tools.
Ask counsel which approach is appropriate for each jurisdiction and channel, what evidence of a choice you should retain, and how to handle older records with incomplete histories. If contract or tax treatment affects a vendor quote, ask the appropriate qualified adviser rather than treating an operational comparison as advice.
Give staff a one-page procedure after the decisions are made. It should identify who can change a preference, where to record a guest’s request, when to pause a campaign and whom to contact when systems disagree. Review the procedure when you add a booking source, change a form or connect a new marketing tool.
For related operating questions, review the reservations FAQ and the guide to measuring reservation no-show costs. When evaluating broader restaurant management software, include preference handling in the demonstration rather than treating it as an afterthought.
Next step: Take the worksheet and one of your actual booking forms to a vendor demonstration. Compare your requirements with Fleksa’s restaurant reservation system and ask to see the relevant booking, preference and correction workflow.
Frequently asked questions
Can I send a booking confirmation when a guest declines marketing?
A promotional decline and a booking-related message are different operational questions. Set a separate service-message workflow and ask counsel to review when and how it may be used.
What should I do when a marketing preference is missing?
Keep it marked as unknown rather than treating it as permission. Hold the guest out of the promotional audience until you have an appropriate basis for the relevant channel.
Does an unsubscribe in one tool update every connected list?
Do not assume it does. Ask each vendor how updates and suppressions move, then check the relevant destinations using a safe test process and an approved live pilot where appropriate.
