Key takeaways
- Capture less, use more: collect only the guest data you will actually use for service or marketing.
- Loyalty matters to many guests: 52% take part in a restaurant rewards program[1].
- Marketing texts and calls carry real legal risk: the TCPA allows $500 per violation, trebled if willful[2].
- Write guest notes as if the guest will read them, and never store card data or health details beyond allergies.
What a restaurant CRM actually is
A restaurant CRM, or guest data platform, is a single record per guest that combines what you know from reservations, the POS, online ordering, loyalty, Wi-Fi sign-ups and email. At its simplest, it answers three questions for the host and the manager: who is this guest, what do they like, and when did they last visit. At its most useful, it lets you send the right message to the right guests and leave everyone else alone.
Many restaurants already have most of a CRM spread across tools. The reservation system has visit history and notes, the POS has spend and items, online ordering has addresses and order frequency, and the loyalty program has opt-ins. The work is deciding which data to keep, how to connect it and how to use it without being creepy or breaking consent rules.
Why guest data is worth the effort
Repeat guests carry most independents, and guests respond to being recognized and rewarded. Fifty-two percent of consumers participate in a restaurant loyalty or rewards program, and 96 percent of them appreciate these programs[1]. Membership affects where people order: 65 percent of drive-thru users and over 60 percent of takeout and delivery users say it does[3].
Source: National Restaurant Association, 2025[3]
Show the data
| Item | Value |
|---|---|
| Drive-thru users | 65% |
| Takeout and delivery users | 60% |
For full-service restaurants, the value is often less about points and more about memory: the host who knows a guest prefers the corner booth, the server who sees a shellfish allergy before the guest mentions it, the manager who sends a thank-you after a large party. A good CRM makes that memory survive staff turnover.
What to capture, from where
| Source | Data worth keeping | Use | Consent note |
|---|---|---|---|
| Reservations | Name, phone, email, party size, visit dates, occasions, seating preferences, allergy notes | Service at the table, occasion follow-ups | Ask before adding to marketing lists |
| POS | Spend per visit, items ordered, server, date and time | Spot regulars, favorite dishes, lapsed guests | Do not store full card numbers; link through the payment token only if your POS supports it |
| Online ordering | Name, phone, email, address, order history, pickup or delivery | Reorder prompts, delivery problem follow-ups | Marketing only with a clear opt-in at checkout |
| Loyalty program | Sign-up date, points, rewards redeemed, birthday month | Rewards and birthday offers | Terms and an easy way to leave |
| Phone calls | Booking requests, catering leads, call-back numbers | Follow-up on the request the guest made | Use for the request, not for marketing, unless they opt in |
| Wi-Fi and events | Email and event attended | Event invitations | Opt-in box, not pre-ticked |
Notice what is not in the table: full dates of birth, detailed health information beyond the allergy or dietary need relevant to the meal, payment card numbers, and free-text opinions about guests. You rarely need them, and each one raises the risk if data leaks.
Connecting the tools without a data project
You do not need a separate guest data platform to start. Most independents get most of the value by connecting two systems they already have and agreeing a few rules.
- Pick the home for guest profiles. For dine-in restaurants this is usually the reservation system; for counter-service it is usually the POS or online ordering tool.
- Connect the POS to that home, if your tools support it, so spend and items appear on the guest profile.
- Match on phone number or email, not on name. Names are spelled five ways; a phone number is usually unique.
- Send marketing opt-ins from every source to one email or text tool, with the source recorded.
- Leave sources that do not connect alone rather than copying lists by hand, which is how duplicates and consent errors creep in.
Consider a dedicated guest data platform only when you have several locations, several ordering channels and a person whose job includes using the data every week. Before that, it is usually an expensive way to keep a list nobody reads.
Who should see what
Not everyone needs every field. Hosts need names, party details, seating preferences, occasions and allergy notes for tonight. Servers need the table-level notes and allergies. Managers need visit history and spend for regulars and complaints. Only the owner or marketing lead needs export rights to the full list. Set permissions to match, remove access the day someone leaves, and never export the whole guest list to a personal laptop or a spreadsheet emailed around the team.
Consent: email, texts and calls
The channel decides the rules. Email marketing needs an honest sender, a working unsubscribe link and prompt removal of anyone who opts out. Texts and calls carry more legal risk. Under the Telephone Consumer Protection Act, consumers can sue for actual losses or $500 per violation, whichever is greater, and courts may treble damages for willful or knowing violations[2]. Federal rules also bar telephone solicitations to residential subscribers before 8 a.m. or after 9 p.m. local time at the called party's location[4].
- Get a clear opt-in for marketing texts, separate from the order or booking confirmation, with wording that says what they will receive.
- Keep transactional messages (booking confirmations, order-ready texts) separate from marketing messages.
- Honor "STOP" and any other reasonable request to opt out quickly, across every tool.
- Store the date, source and wording of each opt-in, so you can prove consent if challenged.
- Send marketing texts only during daytime hours in the guest's time zone.
A list of phone numbers from booking calls is not a marketing list. Those guests gave you a number to confirm a table, not to receive promotions.
State privacy laws
A growing number of states have consumer privacy laws that give residents rights to know, delete and opt out of the sale or sharing of their personal information. Most apply only above size thresholds, but large groups and some single brands with big online ordering lists can cross them. In California, for example, the annual gross revenue threshold in the definition of a covered business was adjusted to $26,625,000 from January 1, 2025[5].
- Publish a privacy notice that says what you collect, why, who you share it with and how guests can contact you.
- Know which vendors hold guest data on your behalf, and what their contracts say about using it.
- Have a way to find and delete a guest's data across tools if they ask.
- If you might be near a state threshold, have a lawyer confirm what applies.
Even below every threshold, treat these rights as good practice. A guest who asks what you hold about them, or asks to be removed, should get a quick, polite answer. Being able to do that in a few minutes is a sign your guest data is organized well enough to be useful.
Use the data sensibly
Start with service, not marketing
Show hosts and servers visit count, occasions, seating preferences and allergy notes for tonight's reservations.
Write notes guests could read
Keep notes factual and kind: "prefers quiet table, celebrates anniversary in June". No judgments, no gossip, no tip history.
Build three simple segments
New guests (first visit in the last 30 days), regulars (three or more visits in 90 days) and lapsed guests (no visit in 120 days).
Send one message per segment
Thank new guests, give regulars first notice of events, and invite lapsed guests back with a reason, not just a discount.
Measure return visits
Count how many guests in each segment visited again within 30 days of the message.
Clean up quarterly
Merge duplicates, remove bounced emails and unsubscribed numbers, and delete data you no longer need.
Example: a lapsed-guest campaign
Example: a fictional 70-seat restaurant finds 340 guests in its reservation system who visited at least twice last year, opted in to email and have not visited in four months. The manager sends one email announcing the new fall menu with a link to book, signed by the chef. No discount is included. Over the next month, 29 of those guests book, and the host stand sees their past notes when they arrive.
Example: the restaurant does not send a text, because most of those guests gave their numbers only for booking confirmations. The manager adds an opt-in for text updates to the booking form for the future, worded plainly and unticked by default. The Example shows the usual pattern: the best campaigns use data guests expected you to have, for something they are glad to hear about.
Frequently asked questions
What is a restaurant CRM?
A single record per guest combining reservations, POS spend, online orders, loyalty and opt-ins, used to recognize guests and send relevant messages.
Can I text guests who booked by phone?
You can send messages about their booking. For marketing texts, get a separate, clear opt-in first; TCPA damages can reach $500 per violation, trebled if willful[2].
What guest data should a restaurant not keep?
Full card numbers, health details beyond allergy and dietary needs for the meal, and opinions about guests. Delete data you no longer use.
Do privacy laws apply to my restaurant?
Many state laws apply above size thresholds; California's revenue threshold is $26,625,000 from 2025[5]. Publish a privacy notice either way and check with a lawyer if you are close.
References
National Restaurant Association (2024). Where operators plan to invest in tech (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), US Code (2026). 47 U.S. Code § 227 - Restrictions on use of telephone equipment (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), eCFR text of FCC rule (2026). 47 CFR § 64.1200 - Delivery restrictions (opens in a new tab) ↑
California Privacy Protection Agency (2024). Updated Monetary Thresholds in CCPA (opens in a new tab) ↑