Table & ReturnEMAIL TOOLS FOR RESTAURANTSCreate an email

WORKED EXAMPLE · GUIDE

A restaurant email worked example: from brief to final draft

Follow a fictional new-menu email from business facts through an illustrative first draft, human edits, preview, and downloadable HTML or text.

By Table & Return · October 24, 2026 · Practical guidance for restaurant teams

This walkthrough shows the decisions behind one restaurant email. It uses a fictional restaurant, Olive & Oak, and a mushroom ravioli menu launch. The draft pair is an editorial illustration of an AI-assisted writing workflow, not a recorded AI session, real customer campaign, or performance case study. You can inspect and download the revised example without spending credits.

The complete example: brief, review, and export.

Olive & Oak and this menu launch are fictional. The initial and final drafts below were prepared editorially to demonstrate an AI-assisted workflow; they are not a recorded live AI response, customer campaign, or evidence of marketing results. Viewing or downloading this example uses no credits.

1. The business brief

Olive & Oak is a fictional neighborhood Italian restaurant. Introduce mushroom ravioli joining the dinner menu from November 6. Invite existing subscribers to view the updated dinner menu. Use a warm tone. No discount, limited-availability claim, or unverified ingredient description.

2. An illustrative first draft

3. The human review

  • Replace the vague subject with the actual dish and service.
  • Keep November 6 as a launch date without adding a year or deadline not supplied in the brief; replace it with your confirmed date.
  • Remove repeated invitations and keep the main news easy to scan.
  • Change “Explore what’s new” to “View the dinner menu” so the button states its destination.
  • Add a practical route for dietary questions without claiming the dish meets any dietary requirement.

4. The revised email

The writing is ready for review, but the email is not send-ready. These exports deliberately leave destination, postal address, and unsubscribe placeholders. Supply your restaurant’s verified details and your sending platform’s unsubscribe mechanism before testing or sending.

Review the draft, fill in the footer, then send through your email platform.

Define the task before choosing the words

The task is to introduce one dish joining the dinner menu from November 6 and invite existing subscribers to view that menu. The brief supplies the restaurant type, launch date, dish, tone, and desired action. It excludes discounts and unsupported scarcity. There is no guest list or personal customer information in the brief. In a real restaurant, check the dish and date with the kitchen first and confirm that the destination page will be updated before the send. Do not interpret an example date as a promise about your own service.

Use the generator for a draft, not operational facts

To try the workflow, open the generator, choose New menu and a warm tone, and enter your own confirmed version of the brief. Sign in and check the balance before generating. A successful live generation uses one credit and may produce different wording each time. The fixed example on this page is available free for comparison; it does not call the AI service when you open this page. The AI cannot confirm the dish’s ingredients, your opening hours, reservations, or dietary suitability. Missing facts must come from the restaurant, not an attractive sentence.

Review the first draft against the brief

The initial example includes the dish and launch date, but its subject is vague and its invitation repeats itself. Those are editing decisions rather than reasons to pay for another generation. Ask whether the subject explains the news, whether the preheader adds useful context, and whether a guest knows what the button will open. Keep one main action. The review in this example changes the subject to name the dish, reduces repetition, and makes the button point explicitly to the dinner menu. None of these changes implies a measured improvement in opens or bookings.

Keep the revision faithful to the facts

The final version retains mushroom ravioli, dinner, Olive & Oak, and November 6. It adds no offer, invented deadline, ingredient story, or claim that a table is available. The dietary question sentence directs guests to staff rather than certifying the dish. Read the finished message aloud to check whether the tone suits the team. In a real launch, verify the date and any year or seasonal reference before sending. Choose your actual menu URL and confirm that the page works on a phone. A clearer draft still needs factual and operational review.

Preview and save the result

Compare the initial and revised versions in this guide, then copy or download the final draft. The HTML and text use the same export functions as the templates and generator. They intentionally leave the menu destination, postal address, and unsubscribe details unfinished because the restaurant is fictional. Do not send the sample unchanged. Replace the restaurant identity and content, supply a valid destination, and use your sending platform’s sender and unsubscribe setup. Save the file somewhere your team can find it; an account credit balance does not create a saved draft library.

Complete the sending workflow in your own tools

Check your email provider’s current import options. Use supported HTML import or place the copy into its native editor. Set the subject and preview in the corresponding fields, review any formatting changes, and test the actual outgoing email before scheduling. Use subscribers whose marketing preferences support the message and follow the rules applicable to your audience. Table & Return does not schedule delivery, manage contacts, or process opt-outs. The linked export tutorial covers the general workflow without claiming a tested integration with a particular provider or plan.

Record learning after the send

For a real campaign, record the approved brief, final copy, audience, destination, and send time. Review useful menu visits, bookings, or orders where your tools can associate them with the email. Note cancellations and any service changes that affect the result. An open or click is not a restaurant visit, and this illustrative walkthrough supplies no revenue or conversion evidence. If you later publish a real case study, obtain permission and explain the measurement period, attribution method, and limitations. The goal here is a repeatable review process, not a claim that one wording will outperform another.

Continue with a practical next step.

Read the HTML and text export tutorial, inspect the complete worked menu example, or choose a new-menu email template. For live AI writing, follow the generator walkthrough.

For commercial email requirements, start with the FTC's guidance for US businesses and the official rules relevant to your own audience. Our guides are general information, not legal advice or a promise of results.

A LITTLE NOTE. A FULL TABLE.

Have a good reason to write?

Choose the moment, add the facts, and create a draft you can review before it reaches your guests.

Let's write an email