Suppression List

Every sending platform keeps a suppression list, because the law makes one mandatory. What differs in hospitality is what else belongs on it. A restaurant CRM builds its exclusions from the same guest records it builds its segments from, so a suppression rule can reference a complaint filed last week or a reservation on tonight’s book, neither of which an email tool knows about.

Who belongs on a suppression list?

Suppression lists hold two kinds of entry, and mixing them up causes trouble later.

The first kind is compulsory. A guest who unsubscribed from email, a guest who replied STOP to a text, a bounced address, a guest who asked to be deleted. Honoring these is a legal obligation rather than a courtesy, and the obligation follows the guest across systems. An unsubscribe recorded in one tool and not the other is a live compliance problem, not a data hygiene issue.

The second kind is discretionary and specific to hospitality. A guest with an unresolved complaint should not receive a cheerful event invitation. A guest messaged three days ago should sit out this week’s send. A guest currently seated in the dining room should not get a marketing text between courses, and a guest who is a member of staff or a supplier does not belong on a guest campaign at all. Each of these is a judgment a restaurant would make instinctively for one guest and cannot make manually for four thousand.

What is the difference between a suppression list and an unsubscribe list?

An unsubscribe list is one input to a suppression list. The unsubscribe is chosen by the guest, applies until the guest reverses it, and cannot be overridden by the restaurant. Suppression is the wider mechanism the platform applies at send time, and much of it is temporary. Recently messaged, currently dining, mid-complaint: all three expire on their own.

Channel scope is the other difference operators run into. A guest can reasonably want no promotional email and still want a text confirming a reservation, so consent and opt-out are tracked per channel and often per message type. Loyalist tracks consent per channel and holds unsubscribe groups, so a guest can decline one type of message without falling out of everything. Without that separation, an unsubscribe from a wine dinner invitation also silences the booking confirmation.

Where should a suppression list live?

A suppression list should live above the individual campaign and be applied automatically to every send. Suppression maintained inside one campaign protects that campaign only, and the failure mode is predictable: the third person to build a segment forgets one exclusion, and the guest who unsubscribed in March gets a message in June from a list somebody exported to a spreadsheet.

Exported lists are where most of these mistakes originate. A CSV pulled from the guestbook is a snapshot with no memory of opt-outs recorded after it, and sending from that file bypasses every guardrail the platform has.