Audience
Know who may receive this specific message.
Choose one useful message, check who can receive it, and use a platform that fits your list and timing. Adapt the email, test the links and settings, then record the actions you can observe.
Know who may receive this specific message.
Use one clear, truthful restaurant update.
Deliver the email and manage sending settings.
Link to the matching menu or reservation details.
Swipe the table horizontally to see every column.
| Your real situation | Start with | What must be true |
|---|---|---|
| New dishes are available | New Menu email | Dish facts and menu page are current. |
| You have a useful ongoing update | Restaurant Newsletter | Frequency and main news are genuine. |
| You have usable birthday data | Birthday email | Audience and invitation terms are accurate. |
Choose from the three complete email examples.
Compare contact capacity, monthly volume, daily limits and features already included in your restaurant system. The software comparison gives the source details. For this example, send one new-menu update to 100 eligible subscribers; this is a teaching scenario, not an optimal list size or a tested campaign.
A new-menu message to 100 recipients needs a platform and list status suitable for that send.
An 800-person same-day send cannot be judged by monthly allowance alone.
Replace fictional dishes, restaurant name, menu URL and sender details. For the 100-person example, use your actual two new dishes and direct menu URL in the New Menu sample. Keep one next step that the destination page can fulfill.
Use the software before-sending checklist.
Swipe the table horizontally to see every column.
| Campaign | Delivered | Unique clicks | Observable action |
|---|---|---|---|
| New menu example | Record platform count | Record menu clicks | Record confirmed reservations separately |
A template is writing help. Your platform handles delivery; clicks alone do not prove a restaurant visit.