You Have Thousands of Customer Phone Numbers. Here's What to Do With Them Legally
Before texting an old customer list, confirm why each number was collected, remove opt-outs, choose one eligible group, and run one useful campaign.
Do not upload the whole list and send a promotion. First find out why each number was collected, remove anyone who opted out, and have qualified counsel confirm which people may receive the message you want to send. Then start with one eligible group and one useful reason to contact them.
That is how an old database becomes usable without pretending that possession of a phone number equals permission.
“Scared of spamming. Scared of getting fined.”A restaurant-agency prospect
The fear is reasonable. The answer is not to let the list sit untouched forever. It is to separate the records you can defend from the records you cannot. The broader restaurant SMS marketing guide explains what happens after the eligible audience is ready.
Start by finding out where every number came from
Export the raw records without deleting or overwriting anything. For each number, keep the source, collection date, restaurant or location, disclosure shown, action used to opt in, and any later opt-out.
A number from a loyalty signup is not automatically the same as a number entered for a reservation, delivery update, Wi-Fi login, giveaway, or online order. The reason the guest supplied it matters. If the source or permission is missing, put that record in an unknown group instead of guessing.
Deduplicate the list by phone number, but keep conflicting source records visible. A person may have opted in through one system and opted out through another. The safest version is the one that preserves both facts for review.
Have counsel clear the audience and the sending method
Promotional texting can involve federal consent rules, federal and state Do Not Call rules, state-specific requirements, and the messaging provider's own registration and content policies. The actual sending technology matters, and provider approval does not prove legal consent.
Give qualified counsel the real materials, not a summary: the collection screens and disclosures, source dates, states involved, sending technology, proposed message, and opt-out process. Ask for a written decision on which records may receive that specific campaign.
Remove every known opt-out before any send. Your system should recognize STOP, QUIT, END, REVOKE, OPT OUT, CANCEL, and UNSUBSCRIBE, along with ordinary requests such as “please don't text me again.” Under the applicable FCC rule, a covered request must be honored as soon as reasonably possible and no later than ten business days.
This is a practical sequence, not legal advice. A lawful answer can change with the collection method, state, provider, and technology.
Choose one group with one honest reason to hear from you
Do not start with “everyone who has a phone number.” Start with the narrowest approved group that shares the same relationship and reason for contact.
That might be guests who explicitly joined a weekday-lunch text list, members who earned a benefit, or guests whose approved signup covered updates about a specific event. It should not be a mixture of old reservations, delivery contacts, giveaway entries, and unknown imports simply because they live in the same spreadsheet.
If the list is mostly email addresses, do not silently treat email permission as texting permission. Audit the permitted channel before contacting anyone.
Write the message so the guest understands why they received it
State the restaurant, the relevant relationship, one timely reason to care, one next step, and the approved opt-out instruction.
For a fictional restaurant with an approved weekday-lunch text audience, that could look like this:
Hi Maya, it's Alex from Harbor Street Pizza on Main. You joined our weekday-lunch text list at the counter. We're serving tomato pie at lunch this Tuesday. Want the menu? Reply YES. Reply STOP to stop texts.
The useful detail is not the pizza. It is that the message can truthfully explain why this guest is hearing from this restaurant. Replace every detail with facts from your own approved campaign.
For more structures, use these restaurant promotional message examples. Keep the first send simple enough that your team can answer every expected reply.
Start small enough to handle the response
Send the first campaign to an approved group your team can actually manage. Before it goes out, decide who answers normal replies, who handles questions or complaints, and who records opt-outs.
Watch what happens in the order it happens:
- attempted messages, delivered messages, and failed messages;
- replies and opt-outs;
- reservations, claims, or other requested actions;
- completed visits;
- settled checks connected to identified guests.
Keep pending records separate until the guest has had enough time to act. Do not call every reply a visit or every reservation revenue. A directly matched check shows sales connected to that guest under your rules; it does not prove the campaign caused every dollar or that the campaign was profitable.
The first campaign should answer a useful question: did an approved message to this specific group create enough real interest and completed visits to deserve another send? The restaurant SMS cost guide can help compare the expense with the visits and checks that followed.
Keep what you learn attached to the customer record
Update the guest record with replies, preferences, opt-outs, visits, and the next appropriate follow-up. That is how the list becomes more valuable over time. A blast treats thousands of numbers as inventory. A useful restaurant program remembers that the list represents thousands of different relationships.
Feast becomes relevant when keeping permission, messages, guest responses, and available POS sales connected is the recurring problem. It supports restaurant follow-up and POS-linked campaign reporting while the restaurant and its counsel remain responsible for deciding who may receive each message.