30 ChatGPT Prompts Every Restaurant Owner Should Try

The quickest AI win for a restaurant owner is a good prompt

You opened ChatGPT, typed "write me a marketing email for our Father's Day set menu," got back something that used the word "culinary" three times and compared your steak to a journey, and closed the tab. Fair.

The problem isn't ChatGPT. It's the prompt. Most restaurant owners are giving it bad briefs because nobody ever showed them what a good one looks like. A structured prompt, fed the right context, gets you output you can actually send.

Below: 30 ChatGPT prompts for restaurant owners, organised by the jobs you actually do. Marketing emails, menu copy, review replies, staff comms, supplier emails, PR pitches, special occasions, and a few power-user prompts at the end. Every one is ready to copy-paste. Every one produces restaurant-specific output on the first try if you fill in the bracketed placeholders.

One thing to name upfront. Every new ChatGPT chat needs you to re-brief it on your restaurant. Cuisine, voice, guest profile, dietary focus. That's the tax you pay for using a general tool. We'll come back to it at the end. For now, the prompts.

If you want the broader frame for where AI fits in a modern restaurant, start with How restaurants use AI.

How to use these prompts (read this once, skip it next time)

Every prompt below follows the same shape:

• Role: who you're asking ChatGPT to be (a restaurant marketing lead, a food writer, a senior manager)
• Context: your restaurant's specifics, in [brackets] for you to fill in
• Task: the actual thing to produce
• Constraints: word count, tone, CTA, boundaries
• Format: what the output should look like (email, table, bullet list)
• Avoid: clichés and phrases to keep out

The bits in [brackets] are the ones you edit. Default values are placeholders. Swap them for your restaurant.

One time-saver: paste your restaurant brief once at the top of a ChatGPT chat and reuse it for every prompt in that session. Or set it in ChatGPT's "custom instructions" so it's baked in across chats. Saves about five minutes per task.

And treat every output as a first draft. These prompts get you 80% of the way; the last 20% is your eye on it before it ships.

1. Marketing emails that don't sound like a brochure (3 prompts)

Marketing emails are the highest-frequency writing job for most operators. They're also where ChatGPT output gets shipped without enough editing. Which is how "embark on a journey" ends up in your subscriber's inbox.

Prompt 1: New menu launch announcement

When to use it: You're launching a seasonal menu, a new chef's special, or a refreshed dinner list and need an announcement email in under 10 minutes.

Act as a restaurant marketing lead for an independent [cuisine type — e.g., modern Thai] restaurant in [city, e.g., Singapore].

Context:
- Restaurant name: [name]
- Positioning: [one-line positioning, e.g., "weekday neighbourhood spot, weekend date venue"]
- Voice: [warm / cheeky / refined / casual — pick one]
- New menu theme: [e.g., "autumn harvest", "Nyonya heritage"]
- Signature dishes on the new menu: [3 dishes with one sensory detail each]

Task: Write a 150-word marketing email announcing the new menu.

Constraints:
- One clear CTA: book a table for [launch date]
- Warm, specific, not formal
- Mention at least two of the three dishes
- British English spelling
- No em dashes

Format: Subject line + preheader + body with one CTA button label

Avoid: the words "culinary", "journey", "nestled", "embark", "delve", "curated", "elevate". Avoid phrases like "come join us" and "don't miss out".

Sample output (abbreviated):

Subject: Autumn's on the menu at Huat Seafood House

Preheader: Three new dishes. One long lunch. Book the first table.

Body: Our new autumn menu lands next Friday, and we think it's our best one yet. The clay-pot short rib has been a year in the making. The miso butterfish... [cont.]

CTA: Book your table

Prompt 2: "We miss you" re-engagement email

When to use it: A guest hasn't been in for 60+ days. You want a warm nudge, not a discount desperation play.

Act as a restaurant marketing lead for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Guest segment: lapsed — last visit was [X weeks / months] ago
- Voice: warm, personal, not salesy
- What makes people come back to us: [one-line reason, e.g., "our pandan kaya toast at weekend brunch"]

Task: Write a 90-word re-engagement email that feels like a note from the owner, not a campaign.

Constraints:
- Reference their last visit in a natural way
- No discount by default. Optional incentive placeholder: [free dessert on next visit — use only if the operator wants]
- One CTA: book your next visit
- British English

Format: Subject line + preheader + short body + CTA

Avoid: "We've missed you!", "It's been a while", "culinary", "special offer just for you".

Sample output (abbreviated):

Subject: Your table's still here

Preheader: It's been a few months. We'd love to have you back.

Body: Noticed it's been a while since we saw you at Kopi & Co. The weekend brunch menu has shifted a little since — the pandan kaya toast is back on Sundays. If you fancy it, we'd love to hold a table for you... [cont.]

Prompt 3: Occasion set-menu email (bilingual option)

When to use it: Mother's Day, Father's Day, Lunar New Year, Ramadan, Eid, Diwali, Christmas — any occasion you run a set menu for.

Act as a restaurant marketing lead for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Occasion: [e.g., Mother's Day / Lunar New Year reunion dinner / Eid set menu]
- Set menu price and what's included: [price, number of courses, signature dish highlight]
- Dates available: [range]
- Voice: [warm / celebratory / refined]
- Languages: [English only / English + Mandarin / English + Bahasa Melayu]

Task: Write a 130-word occasion email in the specified language(s). If bilingual, write the English version first, then the translation underneath.

Constraints:
- Lead with the emotional hook of the occasion, not the price
- Mention one signature dish by name
- One clear CTA: book your table
- Price mentioned once, near the end

Format: Subject line + preheader + body + CTA (repeat in second language if bilingual)

Avoid: "honour your mother", "embark", "unforgettable", "culinary", "treat your loved ones".

Sample output (abbreviated):

Subject: A reunion dinner, without the kitchen cleanup

Preheader: Eight courses. One long table. We'll handle the rest.

Body: Lunar New Year reunion dinner at Huat Seafood House, 27–29 January. Eight courses built around our prosperity yusheng and slow-braised abalone... [cont.]

If you're sending these weekly and tired of pasting your restaurant brief into ChatGPT every time, Oddle's Generate Campaign does this inside the email tool. It holds your brand context and guest data, so you're not re-briefing from scratch. More on that at the end.

2. Menu copy that makes a dish sell (3 prompts)

Menu descriptions are the most skimmable copy in your entire restaurant. Most are forgettable. These prompts get you specific, sensory language. Without the clichés.

Prompt 4: Menu descriptions for a full section

When to use it: Writing or refreshing descriptions for an entire menu section (mains, sharing plates, desserts) in one pass.

Act as a food writer for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Voice: [refined / conversational / playful]
- Menu section: [e.g., Mains]
- Dishes with their core ingredients (one per line):
  1. [Dish name] — [3–5 key ingredients]
  2. [Dish name] — [3–5 key ingredients]
  3. [Dish name] — [3–5 key ingredients]

Task: Write a 20–25 word description for each dish.

Constraints:
- Each description names at least one cooking method (braised, charred, cured) and one origin or sourcing detail
- No adjective pile-ups ("rich, buttery, indulgent")
- Lead with the hero ingredient, not the adjective
- British English

Format: Markdown table with columns: Dish | Description

Avoid: "decadent", "mouthwatering", "perfectly cooked", "house-made" (unless genuinely distinctive), "culinary", "elevated", "journey".

Sample output (abbreviated):

| Dish | Description |

|------|-------------|

| Clay-pot short rib | Short rib braised overnight in Shaoxing and rock sugar, finished over charcoal, served with spring onion pancakes. |

| Miso butterfish | Butterfish cured three days in white miso, grilled, with pickled daikon and shiso... |

Prompt 5: Server upsell script for a high-margin dish

When to use it: You have a signature dish you want servers to recommend without sounding like they're upselling.

Act as a front-of-house training lead for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Dish to recommend: [dish name + one-line what makes it special]
- Typical guest: [e.g., couples on first date, regulars on weekday lunch]

Task: Write two 40-word server lines for recommending this dish. One confident ("this is the one I'd order"), one subtle ("if you haven't had it before…").

Constraints:
- Sounds like a real person speaking, not a script
- Names one specific detail about the dish (technique, ingredient, time)
- Doesn't use the word "recommend" or "popular"

Format: Two options, labelled A (confident) and B (subtle)

Avoid: "signature", "must-try", "best seller", "customers love it", "you'll love it".

Sample output (abbreviated):

A: "If it's your first time, get the clay-pot short rib. We braise it overnight — you won't find it done like this anywhere else on this street."

B: "Just so you know, the short rib is back on tonight. It goes quickly. Happy to hold one if you want to decide later."

Prompt 6: Dietary-alternative suggestions using existing mise en place

When to use it: A guest needs vegetarian, vegan, or gluten-free options and you want suggestions your kitchen can execute without new prep.

Act as a head chef at an independent [cuisine] restaurant in [city].

Context:
- Existing menu section: [paste 6–10 dishes with key ingredients]
- Kitchen mise en place already on hand: [list ingredients and preps you already prep daily]

Task: Suggest three dietary-alternative dishes — one vegetarian, one vegan, one gluten-free — that use only the existing mise en place.

Constraints:
- Each dish must use at least 3 ingredients already in daily prep
- Each dish has a 20-word menu description
- Flag any ingredient cost considerations (e.g., "uses off-cut, lower margin-neutral")

Format: Three dish suggestions with: name, description, mise en place used, margin note.

Avoid: suggestions that require new sourcing, special orders, or fresh daily prep.

Sample output (abbreviated):

1. Charred aubergine, miso glaze (vegan) — Uses: aubergine, miso from butterfish cure, spring onion, sesame. Margin note: uses off-cuts of miso mix — margin-positive.

2. Glass noodle salad, pickled daikon (GF, vegan on request)... [cont.]

3. Google and social review responses at scale (3 prompts)

Review responses protect reputation. They also take 15 minutes each when you're writing them off the cuff at 11pm after service. These prompts get you to 90% quality in under a minute, so you can spend the other fourteen minutes sitting down.

If reviews are a weekly fire-drill for you, there's a longer playbook here: AI for responding to Google reviews.

Prompt 7: 5-star review reply

When to use it: Responding to a positive review without sounding like you copied the same line on all 50 of them.

Act as the owner of an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Voice: warm, specific, not corporate
- The review: [paste the full review text]

Task: Write a reply under 60 words.

Constraints:
- Mention at least one specific thing the reviewer said (dish name, staff member, moment)
- Sign off with the owner's first name if provided — otherwise "the [name] team"
- Invite them back naturally, not as a sales line
- British English

Format: A single short reply, no subject line.

Avoid: "We appreciate your kind words", "Thank you so much for the 5-star review", "Your feedback means the world to us".

Sample output (abbreviated):

Thanks Sarah — really glad you enjoyed the short rib, and good to hear Marcus looked after you. He'll be chuffed you mentioned him by name. We'll save the corner booth for next time. — Jon

Prompt 8: 1–2 star review reply

When to use it: De-escalating a negative review without admitting liability or arguing publicly.

Act as the owner of an independent [cuisine] restaurant in [city]. This is a public reply on Google — it will be read by other prospective guests, not just the reviewer.

Context:
- Restaurant name: [name]
- The review: [paste the full review text]
- What actually happened, in one line: [your internal version, e.g., "kitchen was short-staffed that night, we know food was slow"]

Task: Write a reply under 80 words.

Constraints:
- Acknowledge their experience without admitting liability
- Don't argue or correct them publicly
- Offer an off-platform channel: email [owner@restaurant.com] or phone
- Don't offer compensation publicly
- Warm, accountable, not defensive
- British English

Format: A single short reply.

Avoid: "We're sorry you feel that way", "We dispute", "Unfortunately", "As per our policy", "we'll review our procedures".

Sample output (abbreviated):

Hi Marcus — thanks for taking the time to write this, and I'm sorry your evening didn't land the way we'd want. I'd like to hear the full story directly. Can you drop me a line at jon@kopiandco.com? I read every one. — Jon

Prompt 9: Multi-language review reply (EN + Mandarin or EN + Bahasa)

When to use it: The review is in Chinese or Bahasa and you want a reply in both languages — native version first, English underneath.

Act as the owner of an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- The review (original language): [paste review]
- Review language: [Mandarin / Bahasa Melayu / Cantonese]
- Voice: warm, specific, not formal

Task: Write a reply in the original language (first), then an English translation underneath.

Constraints:
- Under 60 words per language
- Reference at least one specific thing they mentioned
- Natural in the original language — not a direct translation from English
- If Mandarin: use Traditional characters if the reviewer used Traditional, Simplified if Simplified
- British English for the English version

Format: Reply in [original language], then blank line, then English translation.

Avoid: formal language that doesn't match a small independent restaurant's voice. Avoid "尊敬的顾客" / "Dear valued customer".

Sample output (abbreviated):

謝謝您特地提到阿華的服務，我會轉告他。下次再來，記得試試我們新上的冬瓜湯。— 阿明

Thanks for mentioning Ah Hua's service — I'll pass it on. Next time, try our new winter melon soup. — Ming

4. Social captions and content that don't all sound the same (3 prompts)

Social is where voice gets lost fastest. A content calendar makes consistency easier. Prompt variety makes each post readable.

Prompt 10: 30-day Instagram content calendar

When to use it: You need a month of post ideas mapped to a consistent weekly rhythm.

Act as a social media lead for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Positioning: [one line]
- Voice: [warm / playful / refined]
- Signature dishes: [3]
- Team members worth featuring: [names + roles]
- Special dates in the next 30 days: [e.g., "anniversary on the 15th"]

Task: Build a 30-day Instagram content calendar.

Constraints:
- Weekly rhythm: Menu Monday (dish feature), Team Tuesday (staff profile), Behind-the-Scenes Wednesday, Guest Story Thursday, Reel Friday, Weekend Vibes Saturday, Quiet Sunday (educational/slow post)
- Each post: type, caption angle (one line), suggested photo brief (one line)
- Include any special dates naturally in the calendar
- Don't repeat dish features within the same week

Format: Markdown table with columns: Day | Date | Post Type | Caption Angle | Photo Brief

Avoid: generic "foodie" language, "come and try", "the best in town".

Sample output (abbreviated):

| Day | Date | Post Type | Caption Angle | Photo Brief |

|-----|------|-----------|----------|-------|

| Mon | 1 Apr | Menu Monday | Why we braise the short rib overnight | Steam rising off the clay pot, close-up |

| Tue | 2 Apr | Team Tuesday | Marcus on his three favourite wines this month | Marcus at the pass, half-smile |

| Wed | 3 Apr | BTS | Morning prep: pandan leaves being tied... [cont.] |

Prompt 11: Single Instagram caption, three tone variations

When to use it: You have one photo and want three caption options so you can pick the one that fits your mood and the post's moment.

Act as a social media lead for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Photo is of: [describe what's in the photo in one line]
- Voice: flexible — we want three options

Task: Write three Instagram captions for this photo.

Constraints:
- Option A: warm and personal (under 80 words)
- Option B: witty and short (under 30 words)
- Option C: concise, almost terse (under 15 words)
- Each ends with a different call-to-action style: A = invitation, B = question, C = none
- No hashtags in the body. List 5–7 relevant hashtags at the bottom once.

Format: Three options labelled A/B/C, then hashtag block.

Avoid: emojis unless the voice calls for it. Avoid "foodie", "delicious", "must-try".

Sample output (abbreviated):

A (warm): "Marcus has been tying pandan leaves by hand since he started with us two years ago. He's faster at it than anyone in the kitchen. This is the kaya that goes into Sunday brunch — the one you queue for..." [cont.]

B (witty): "Marcus can tie a pandan leaf in 0.8 seconds. We've timed it."

C (terse): "Sunday's kaya. In progress."

Prompt 12: Short-form video hook ideas

When to use it: You're filming TikTok or Reels content and need hook lines that stop the scroll.

Act as a short-form video strategist for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Subject of the video: [dish / technique / behind-the-scenes moment]
- Target audience: [e.g., 25–40-year-olds in your city, food-curious]

Task: Write 10 hook lines for the first 2 seconds of a short-form video.

Constraints:
- Each under 10 words
- Mix formats: statement, question, bold claim, contrarian take, number/stat, sensory detail, curiosity gap, recognisable trope, behind-the-scenes tease, insider knowledge
- Specific to the subject, not generic

Format: Numbered list of 10 hooks, each labelled with its format type.

Avoid: "You won't believe", "We tried", "The best _ in _", "Things you didn't know".

Sample output (abbreviated):

1. (Bold claim) "We braise this short rib for 14 hours. Nobody does that."

2. (Curiosity gap) "The one spice in this dish that nobody gets right."

3. (Number) "Three hours, one pot, zero shortcuts..." [cont.]

5. Staff communication without the awkwardness (3 prompts)

Internal comms are the quiet killer of an operator's evening. These prompts draft the message. Your judgement decides if it ships.

A note up front. For anything touching HR or disciplinary topics, these are drafts only. Run them past your HR lead or legal advisor before sending.

Prompt 13: Shift change / schedule update message

When to use it: You're sending a WhatsApp update to the team about a roster change and want it short, clear, and not corporate-stiff.

Act as a senior manager at an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Team size: [e.g., 12 front-of-house, 8 kitchen]
- Voice: friendly, direct, respectful — like a note from a colleague, not HR

Task: Write a WhatsApp-style message to the team about: [describe the change — e.g., "moving Friday brunch start time from 10am to 9:30am from next week due to increased bookings"]

Constraints:
- Under 80 words
- Explain why in one short line
- Acknowledge the impact on people
- Ask for confirmation if needed
- No corporate filler

Format: Single message, ready to paste into WhatsApp.

Avoid: "kindly note", "effective immediately", "please be advised", "as per".

Sample output (abbreviated):

Hey team — heads up, Friday brunch is moving to a 9:30am start from next week. Bookings have picked up and we need the extra half-hour. I know that's a bit earlier for those of you on the 8am in. Let me know if anyone needs a hand swapping shifts. — Jon

Prompt 14: De-escalation message after a guest complaint

When to use it: A senior server handled a difficult guest and you need to check in with them without it feeling like a telling-off.

Act as the owner of an independent [cuisine] restaurant in [city]. You are drafting a private message to a senior server. This is a human-in-the-loop draft only — review before sending.

Context:
- Server's name: [name]
- What happened: [one-line account, e.g., "guest complained about wait time, server responded tersely, guest left angry"]
- Relationship context: [e.g., "she's been with us 4 years, this is very out of character"]

Task: Write a 100-word private message acknowledging what happened, without accusing, and offering to talk.

Constraints:
- Lead with curiosity, not judgement ("I want to hear your side first")
- Name the specific incident without editorialising
- Offer a time to talk in person, not over message
- Don't use disciplinary language

Format: Single private message, ready to send.

Avoid: "I was disappointed", "we expect better", "this is a serious matter", "in future please".

Sample output (abbreviated):

Hey Sarah — quick one. Want to check in about last night's table 14. The guest mentioned the exchange got tense around the wait time. Before I form any view on it, I'd rather hear what happened from you directly. You've been rock-solid with us for four years, so I'm reading this as an off night, not a pattern. Free for a coffee before service tomorrow? — Jon

Prompt 15: New-hire first-day welcome

When to use it: You're onboarding a new server or kitchen hire and want a warm welcome message that sets expectations without being a corporate induction deck.

Act as the owner of an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- New hire's name: [name]
- Role: [e.g., server, line cook, reservations lead]
- Three things that matter most on day one: [list]

Task: Write a 150-word welcome message for their first morning.

Constraints:
- Warm, personal, direct
- Names the three things that matter on day one
- Mentions one specific person they'll work closely with
- Ends with a practical note (e.g., "lunch is on us today")
- British English

Format: Message ready to paste into WhatsApp or print.

Avoid: "welcome to the family", "we're thrilled", "looking forward to your contribution", "hit the ground running".

Sample output (abbreviated):

Hey Marcus — welcome to Kopi & Co. Quick note before you start today. Three things I'll be watching for on your first week: how you greet a table, how you handle the menu questions (it's fine to say "let me check"), and whether you're cleaning as you go. Everyone here does. Maya will be on the floor with you all of this week — she knows the menu better than me. Lunch today is on us — pick anything you like. See you at 11. — Jon

6. Supplier and landlord negotiations you'd rather not write (3 prompts)

These are the emails every operator dreads writing. The tone has to be firm but relationship-preserving. Suppliers and landlords in Singapore, Malaysia, and across Southeast Asia tend to remember how you handled the conversation long after they've forgotten the price point.

One note. For lease renegotiations, always review with your lawyer before sending. ChatGPT writes the draft. Legal signs off.

Prompt 16: Supplier price-increase pushback

When to use it: Your protein or produce supplier has announced a price rise and you want to push back without souring the relationship.

Act as an operations lead at an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Supplier: [supplier name + what you buy from them]
- Your monthly order volume: [approx. SGD/MYR amount]
- Proposed increase: [e.g., "8% on all seafood"]
- Your relationship: [e.g., "been buying from them for 3 years, always paid on time"]

Task: Write a 150-word email asking them to hold prices or offer an alternative.

Constraints:
- Acknowledge the market context without conceding
- Reference your order volume and payment history
- Offer one counter: (a) extend the contract by 12 months for a price hold, or (b) commit to higher volume in exchange
- Warm close, leaves the door open

Format: Email with subject line, body, sign-off.

Avoid: threatening language, "we'll have to consider alternatives" (unless you will), "as a valued supplier".

Sample output (abbreviated):

Subject: Re: April price update

Hi Ahmad — thanks for the heads-up. Before we process it at the new rate, I wanted to check if there's room to hold. We're at roughly SGD 12K/month with you across seafood and would be open to extending our arrangement by 12 months if we can stay at current pricing... [cont.]

Prompt 17: Landlord rent-review response

When to use it: Your landlord has proposed a rent increase and you need a polite, fact-based response. Review with your lawyer before sending.

Act as the owner of an independent [cuisine] restaurant in [city]. This is a draft for the owner to review with legal counsel before sending.

Context:
- Restaurant name and location: [name + address]
- Current rent: [amount + lease remaining]
- Proposed increase: [percentage or new amount]
- Market comparables you know of: [if any — otherwise leave blank]
- Your track record as a tenant: [e.g., "always paid on time, invested in fit-out, no complaints from other tenants"]

Task: Write a 180-word email acknowledging receipt and proposing a conversation before agreeing to terms.

Constraints:
- Respectful, fact-based, not emotional
- Reference your track record concretely
- Mention market comparables if supplied
- Propose a meeting rather than countering in writing
- British English

Format: Email with subject, body, sign-off. Mark draft as "REVIEW WITH LEGAL BEFORE SENDING" at the top.

Avoid: threats, emotional appeals, references to closing the restaurant, passive-aggressive language.

Sample output (abbreviated):

[REVIEW WITH LEGAL BEFORE SENDING]

Subject: Lease renewal — request for a conversation

Dear Mr Lim — thank you for sending through the renewal terms. Before we respond formally, I'd like to request a meeting to talk through a few points... [cont.]

Prompt 18: Request for extended payment terms

When to use it: Cash flow is tight and you want to ask a supplier for 30 or 60-day terms without sounding like you're in trouble.

Act as an operations lead at an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Supplier: [supplier name]
- Current terms: [e.g., "payment on delivery"]
- Proposed terms: [e.g., "net 30"]
- Reason (one line, honest but not desperate): [e.g., "smoothing cash flow for end-of-quarter"]

Task: Write a 120-word email proposing new payment terms.

Constraints:
- Short, direct, confident
- Acknowledge this is a change request
- Offer one concession in return (e.g., guaranteed minimum order volume)
- Don't apologise excessively

Format: Email with subject, body, sign-off.

Avoid: "I hate to ask", over-apologising, "we're going through a difficult period".

Sample output (abbreviated):

Subject: Proposed shift to net-30 terms

Hi Ahmad — quick proposal. Would you consider moving our account from payment-on-delivery to net-30? It'd help us smooth cash flow across the quarter. In exchange, we're happy to commit to a minimum monthly order of SGD 10K, up from our current average... [cont.]

7. Turning guest feedback into action (3 prompts)

Feedback is a pile of text on a page until someone synthesises it. ChatGPT is good at this job. Cheap, fast, and willing to read 50 reviews without complaint.

Prompt 19: Summarise 30 recent reviews into themes

When to use it: You've got a stack of recent Google, Facebook, or in-house survey reviews and want to know what guests are actually telling you.

Act as a guest experience analyst for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Reviews source: [Google / in-house survey / mixed]
- Review text: [paste 30 recent reviews]

Task: Identify the top three themes across these reviews and the action implied by each.

Constraints:
- Themes must be specific, not generic ("service was slow on weekend dinner" not "service issues")
- Each theme supported by at least 3 review quotes
- Each theme paired with one clear, actionable recommendation
- Distinguish between occasional complaints and consistent patterns

Format: Three themes, each with: theme, supporting quotes (3), recommended action.

Avoid: vague recommendations like "improve service". Be specific.

Sample output (abbreviated):

Theme 1: Weekend dinner wait times exceed 15 minutes at the door

Supporting quotes: "waited 25 minutes past our reservation"... "table wasn't ready"... "felt rushed once seated to make up time".

Action: Review reservation slot density on Friday and Saturday dinner. Add a 15-minute buffer between slots at the peak 7:30–8:30 window.

Prompt 20: Analyse a year of survey or check-in responses

When to use it: You have a year's worth of guest survey data (or check-in programme responses) and want top-level insights segmented by guest type.

Act as a guest insights analyst for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Data: [paste up to 200 responses — text only, with one-line descriptor per response, e.g., "first visit | 2024-03-02 | 'food was great, service felt slow on a Tuesday'"]

Task: Return the top 5 insights, each segmented by guest type (first-timer / returning regular / lapsed).

Constraints:
- Each insight names the guest segment it applies to
- Each insight includes at least one supporting quote
- Each insight ends with one recommended action
- Flag any insight that contradicts another (e.g., "regulars love X, first-timers find X confusing")

Format: Five insights, each with: segment, insight, quote, action.

Avoid: generic insights that apply to all segments equally. Be specific to each segment.

Sample output (abbreviated):

Insight 1 (first-timers): Menu feels overwhelming on first visit. Quote: "didn't know what to order, staff were busy". Action: brief servers to offer a "three-dish recommendation" to tables with no reservation history.

Prompt 21: Apology-and-recovery letter for a serious service failure

When to use it: Something went genuinely wrong — a lost reservation for a birthday, a dietary mistake, a rude exchange — and you need to write directly to the guest. Review before sending.

Act as the owner of an independent [cuisine] restaurant in [city]. This is a private letter to a guest after a serious service failure. Review before sending.

Context:
- Guest name: [name]
- What happened, in your own words: [honest account, 2–3 lines]
- Context that matters: [e.g., "it was her mother's 70th, they had come specifically for the anniversary"]

Task: Write a 180-word private email.

Constraints:
- Take responsibility clearly, without qualifying
- Don't explain operational reasons in the first half — lead with accountability
- Offer one tangible remedy (meal on the house, dedicated reservation for a future visit)
- Warm, personal sign-off from the owner

Format: Email with subject line, body, sign-off.

Avoid: "we apologise for the inconvenience", "unfortunately", "we dispute", shifting blame to staff, over-explaining.

Sample output (abbreviated):

Subject: About Saturday

Hi Priya — I want to write directly about what happened at your mother's birthday on Saturday. We lost your reservation. You came from across town for a 70th, and we didn't have a table for you. I'm sorry. Not the kitchen, not the server on the floor — me... [cont.]

8. Press, partnerships, and PR (3 prompts)

Most independent restaurants are bad at outreach. Not because the restaurant isn't good. Because the email is. These prompts give you a first draft that doesn't sound like a press release from 2011.

Prompt 22: New restaurant opening press pitch

When to use it: You're opening a new outlet or concept and want a pitch to send to local F&B journalists.

Act as a press liaison for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Concept in one sentence: [e.g., "a 30-seat neighbourhood bistro focused on wood-fired seafood"]
- Opening date: [date]
- Chef/founder background: [one line]
- What's new or distinctive about it: [one line — what makes it worth writing about]
- Target journalist: [name + publication, or "local F&B journalist"]

Task: Write a 150-word pitch email.

Constraints:
- Subject line leads with the hook, not the restaurant name
- Body: hook → what's new → why now → invitation to a pre-opening visit
- No press-release formality
- Include a line about what would make it visual/photographable
- Warm, human close

Format: Subject + body + sign-off.

Avoid: "We are pleased to announce", "proud to unveil", "the first of its kind", "unique dining experience".

Sample output (abbreviated):

Subject: A 30-seat bistro built around one wood-fired oven opens in Tiong Bahru next month

Hi Rachel — I wanted to tell you about a new place opening on Seng Poh Road on 12 May. It's built around a single wood-fired oven — the one Marcus Tan used to run at [prior restaurant]. The room seats 30, the menu is 12 dishes, and everything touches fire... [cont.]

Prompt 23: Collaboration pitch to a complementary F&B brand

When to use it: You want to propose a collab with a coffee roaster, bakery, wine shop, or cocktail bar.

Act as a partnerships lead for an independent [cuisine] restaurant in [city].

Context:
- Your restaurant name: [name] — [one-line positioning]
- Target partner: [name + what they do]
- Why it makes sense: [2-line reasoning]
- Collaboration idea: [e.g., "four-week menu feature with their beans as the house pour-over"]
- What you're offering them: [e.g., "menu placement, staff training included, co-marketed launch"]

Task: Write a 130-word email proposing the collaboration.

Constraints:
- Mutual value clear in the first paragraph
- Specific about what you're offering and what you're asking for
- Warm, concise, not fluffy
- Ends with a specific next step (coffee this week, visit to our space, etc.)

Format: Subject + body.

Avoid: "synergy", "mutually beneficial partnership", "touch base", "circle back".

Sample output (abbreviated):

Subject: A four-week coffee feature with Kopi & Co

Hi Lena — I've been drinking your single-origin Timor-Leste at home for six months and wanted to propose something. Would you be open to us running it as our house pour-over for four weeks in June? Full menu placement, credit on signage, and I'd put one of our team through training on your kit... [cont.]

Prompt 24: Influencer / content creator outreach DM

When to use it: You want to invite a local food creator for a hosted meal without it feeling transactional.

Act as a social media lead at an independent [cuisine] restaurant in [city].

Context:
- Your restaurant name: [name]
- Creator: [name] — [platform + one-line on their content]
- Why this creator specifically: [one detail from their recent content]
- Hosted meal terms: [e.g., "full menu for two, no posting required"]

Task: Write an Instagram DM under 100 words inviting them for a hosted meal.

Constraints:
- First sentence references their actual content, specifically
- Doesn't demand posting as a condition
- Warm, peer-to-peer, not transactional
- Ends with a specific next step (a date range for them to pick from)

Format: Single DM, ready to paste.

Avoid: "We'd love to collaborate", "exchange for a post", "influencer package", mass-template vibes.

Sample output (abbreviated):

Hey Zara — your short on the three-day laksa at that spot in Bangsar was the best food video I've watched in months. If you're ever in Singapore, I'd love to host you and a plus-one at Kopi & Co — full menu, on us, no posting required. Any time in May? — Jon

9. Special occasions and seasonal campaigns (3 prompts)

Occasion campaigns drive outsized booking volume. The prompts below are built for the full calendar your guests actually celebrate. Lunar New Year, Ramadan, Eid, Diwali, alongside Mother's Day and Christmas. Not just the Western holidays.

Prompt 25: Full occasion campaign brief

When to use it: You need a campaign hook, email subject, Instagram post idea, and menu angle for an upcoming occasion — all in one go.

Act as a campaign strategist for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Occasion: [Mother's Day / Father's Day / Valentine's / Christmas / anniversary / New Year's Eve]
- Date range: [when it runs]
- Signature dish you'd build the campaign around: [dish]
- Voice: [warm / playful / refined]

Task: Produce a full campaign brief with four outputs: (1) campaign hook line, (2) email subject line, (3) Instagram caption, (4) menu angle.

Constraints:
- Hook must be specific to the occasion — not "celebrate with us"
- All four outputs should share a through-line
- Email subject under 50 characters
- Instagram caption under 80 words
- Menu angle should name the signature dish

Format: Labelled sections for each output.

Avoid: "celebrate with your loved ones", "make it special", "unforgettable experience".

Sample output (abbreviated):

Hook: "The dinner where Mum doesn't cook."

Subject: "This year, you're off kitchen duty."

Instagram: "Mother's Day. Eight courses. One long table. She does nothing. You book. We handle everything else. Sunday 12 May — two seatings, 12pm and 6pm."... [cont.]

Prompt 26: Lunar New Year / Ramadan / Eid / Diwali campaign

When to use it: You're running a regional occasion campaign and want messaging that respects the occasion without tokenism.

Act as a campaign strategist for an independent [cuisine] restaurant in [city] serving a multicultural guest base.

Context:
- Restaurant name: [name]
- Occasion: [Lunar New Year / Ramadan / Eid / Diwali]
- Your restaurant's relationship to the occasion: [e.g., "our chef is Malay, Ramadan is personal for us" / "most of our regulars celebrate LNY, we run a reunion dinner every year"]
- Set menu or offer: [details]
- Languages: [EN / EN + Mandarin / EN + Bahasa]

Task: Write a campaign email and one Instagram post for the occasion.

Constraints:
- Respect the occasion — don't reduce it to a discount or a novelty
- Lead with a specific moment of the occasion (iftar, reunion dinner, rangoli lighting)
- Reference the restaurant's genuine connection to the occasion, if relevant
- Bilingual output where specified — native second language, not a direct translation
- Include booking CTA

Format: Email (subject + body + CTA) + Instagram post. If bilingual, both languages.

Avoid: "Happy Lunar New Year from all of us at [name]", generic well-wishing, emoji pile-ups, tokenistic references.

Sample output (abbreviated):

Subject: Iftar at Kopi & Co, 10–30 March

Body: For the month of Ramadan, we're opening early for iftar. Our chef Azman has built a four-course menu around the dishes he grew up breaking fast with — kurma, bubur lambuk, and his mother's rendang... [cont.]

Prompt 27: Guest birthday or anniversary message

When to use it: You're sending a personalised message to a guest whose birthday or anniversary is coming up, pulled from your guest data.

Act as a guest relations lead for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Guest first name: [name]
- Occasion: [birthday / wedding anniversary]
- Guest history: [e.g., "regular, comes monthly, usually books the corner booth"]
- Voice: warm, personal, not salesy

Task: Write two variations of a message: one warm, one playful.

Constraints:
- Under 80 words each
- References something specific about their history if provided
- Optional incentive placeholder: [free glass of wine on the day — include only if the operator wants]
- One clear CTA: book your table

Format: Two labelled versions: Warm / Playful.

Avoid: "on behalf of everyone at [name]", generic birthday clip-art language, over-formality.

Sample output (abbreviated):

Warm: "Hi Priya — saw your birthday's next Thursday. The corner booth's yours if you want it. Bring whoever you like. Let me know and I'll hold it. — Jon"

Playful: "Priya — another year, another excuse to sit in the corner booth. It's free Thursday. Shall we pencil you in? — Jon"

10. Three power-user prompts most operators don't know about (3 prompts)

These three prompts go beyond writing. They use ChatGPT as an analyst, not a copywriter. The shape of the output is different, and the payoff is bigger.

Prompt 28: The menu engineering prompt

When to use it: You have menu item sales data from the last 90 days and want to know which dishes to push, cut, reprice, or keep. Credit where it's due: the classic menu-engineering framework comes from Smith and Kasavana (1982). It isn't new. It's just fast now.

Act as a menu engineering consultant for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Time period: [e.g., last 90 days]
- Menu section: [e.g., mains]
- Data (one line per dish):
  [Dish name] | [units sold] | [food cost %] | [menu price, SGD/MYR/AUD]

Task: Classify each dish using the classic menu-engineering matrix:
- STARS (high margin, high sales) — keep and feature
- PUZZLES (high margin, low sales) — push
- WORKHORSES (low margin, high sales) — reprice or rework
- DOGS (low margin, low sales) — cut or replace

Constraints:
- Margin threshold: above 70% gross margin = "high margin"
- Sales threshold: above the section average = "high sales"
- Each dish gets one specific, actionable recommendation (not just the category)
- Flag any dish where the data looks unusual (e.g., low sales and low margin but a signature dish)

Format: Markdown table: Dish | Classification | Recommended Action | Note.

Avoid: generic recommendations. Be specific to each dish.

Sample output (abbreviated):

| Dish | Classification | Action | Note |

|------|----------------|--------|------|

| Clay-pot short rib | STAR | Keep as lead hero dish. Feature in all email opens. | Margin 76%, sales 2x section avg. |

| Miso butterfish | PUZZLE | Feature in server upsell script. Menu position from #7 to #2. | Margin 81%, sales 0.4x avg. |

| Pandan chicken rice | WORKHORSE | Price up SGD 2 (SGD 18 → SGD 20). | Margin 58%, sales 3x avg. Resilient to price bump. |

| Caesar salad | DOG | Cut next menu cycle. | Margin 52%, sales 0.2x avg. |

Prompt 29: The ideal guest profile prompt

When to use it: You want to know, from evidence rather than guessing, who your most valuable guest actually is.

Act as a guest insights analyst for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Data: [paste 20 reviews, enrolment survey responses, or feedback forms]

Task: Build a detailed ideal guest profile from this data.

Constraints:
- Profile must include: demographics (age range, group composition), common occasions, what they specifically value (pull at least 3 phrases from the data), what makes them return
- Distinguish between what they say they love and what the data suggests they actually come back for
- Name any false positives (e.g., "they say they love the wine list but only 12% of tables order from it")

Format: Structured profile with five sections: Demographics, Occasions, Stated Values (with quotes), Observed Behaviour, Return Drivers.

Avoid: vague demographic profiles. Be specific.

Sample output (abbreviated):

Demographics: 28–42, mostly pairs and groups of four, Singapore-resident, professional background.

Occasions: 60% date nights and first-time meets, 30% work dinners, 10% birthdays.

Stated values: "not pretentious" (8 mentions), "feels like the owner cares" (6), "kitchen's visible" (4)...

Observed behaviour: Book 7–10 days ahead, average spend SGD 95/head, 40% rebook within 60 days...

Prompt 30: Lapsed-guest winback variations by spend tier

When to use it: You have a list of lapsed guests and want tailored winback copy. Warm for your best guests, more direct for transactional ones.

Act as a CRM lead for an independent [cuisine] restaurant in [city].

Context:
- Restaurant name: [name]
- Voice: [warm / casual / refined]
- Lapsed guest segments:
  - Tier A: lifetime spend above SGD 1,000, last visit 60–120 days ago
  - Tier B: lifetime spend SGD 300–1,000, last visit 60–120 days ago
  - Tier C: lifetime spend under SGD 300, last visit 60–120 days ago

Task: Write one 90-word winback email per tier. Each tier gets its own tone, incentive level, and CTA.

Constraints:
- Tier A: no discount. Personal tone. CTA is "book with us directly, I'll make sure we save your usual table"
- Tier B: one soft incentive (e.g., complimentary starter on next visit). Warm but general tone
- Tier C: clearer value-led incentive (e.g., 15% off set menu). Direct tone, no over-familiarity
- Each email has its own subject line, preheader, body, CTA
- British English

Format: Three labelled sections (Tier A / B / C), each with subject + preheader + body + CTA.

Avoid: same email with different incentive — each needs a different voice. Avoid "we noticed you haven't visited".

Sample output (abbreviated):

Tier A: Subject: "Your corner booth's been quiet." Preheader: A note from Jon.

Body: "Priya — noticed you haven't been in since January. No campaign, just checking in. Your usual booth is free next Thursday if you want it. Nothing fancy needed on your end — just reply yes. — Jon"

Tier B: Subject: "A table, and a starter on us."

Body: "Hi Marcus — it's been about ten weeks. If you've been meaning to come back, we've got a free pandan kaya starter with your name on it for your next visit..." [cont.]

That third prompt points at the larger problem.

The real win isn't a better prompt. It's stopping the re-briefing.

You've probably noticed by now: every prompt above needed you to paste in your restaurant's context. Cuisine, voice, guest profile, signature dishes, spend tiers, occasion calendar. Every. Single. Prompt.

That's useful the first time. It's exhausting by the tenth. And it's why most operators who try ChatGPT seriously stop within a month. Not because the output is bad. Because re-briefing it on your restaurant for every task is its own part-time job.

The real gain for most restaurants isn't writing better prompts. It's building the context once and having it auto-feed every AI task from then on.

That's the gap Oddle's Generate Campaign was built to close. A Brand Knowledge Base holds your restaurant's context in one place. Cuisine, voice, signature dishes, guest profiles, tone rules, things to avoid. Campaigns get drafted against that context instead of against a blank chat window. And because the tool sits next to your guest data via Customer Intelligence, it knows which guests to send to, not just what to say.

You still own the final word. You just stop re-briefing from scratch.

The bigger point from the AI hub: AI is a force-multiplier when it's fed your data. Until then, it's a well-spoken generalist.

Want the broader frame on where AI fits in a modern restaurant? Read How restaurants use AI.

Try these this week

Three to start with, if you're picking: the new-menu announcement email (Prompt 1), the 5-star review reply (Prompt 7), and the menu description prompt (Prompt 4). Low risk, instant output, repeatable every week.

Save this page. Bookmark it. Send it to whoever runs your marketing.

And if you'd rather not type these prompts from scratch every time, book an Oddle demo. We'll show you what Generate Campaign does when it's fed your guests and your brand.

FAQ

What's the best ChatGPT prompt for a restaurant?

The best prompt is the one that matches the job you're doing and gives ChatGPT enough structure to work with. A well-structured prompt has six parts: role (who ChatGPT is acting as), context (your restaurant's specifics), task (the concrete thing to produce), constraints (word count, tone, CTA), format (how the output should look), and avoid (clichés to keep out). Any of the 30 prompts above will produce first-try usable output if you fill in the bracketed placeholders properly. The marketing email prompt (Prompt 1) is the most-used starting point for most operators.

Can ChatGPT replace a marketing agency for restaurants?

Not entirely, but it can replace the parts of agency work that are brief-to-draft conversion, which is a lot of it. What ChatGPT is good at: first drafts, variations, multi-language output, rapid iteration. What it still can't do on its own: strategy, genuine brand judgement, knowing your guests, photography. For most independent restaurants running 1–3 outlets, ChatGPT plus someone in-house who knows the brand is a better setup than a retainer agency. For multi-outlet groups, agencies still play a role in campaign strategy and creative direction.

Is it safe to put guest data into ChatGPT?

Be careful. Don't paste personally identifiable information (names, email addresses, phone numbers, payment details) into a public ChatGPT chat. If you're analysing reviews or survey responses, strip or anonymise any PII first. For richer guest analysis where you need the data intact, use tools built for restaurants that keep guest data in a closed environment rather than a general chat interface. Check your country's data protection rules. Singapore's PDPA, Australia's Privacy Act, Malaysia's PDPA, and the UAE's PDPL all have requirements around third-party processing of personal data.

What version of ChatGPT should I use?

For most restaurant tasks, ChatGPT's free tier is enough. It handles the prompts above without issue. The paid tier (Plus) adds file upload (useful for pasting in a PDF menu and asking for descriptions), image input (useful for analysing a dish photo), and faster responses during peak hours. If you're a larger group processing a lot of guest data regularly, ChatGPT Team or Enterprise adds data-privacy controls that matter. Outputs aren't used for model training, and there's stricter access control.

How do I stop ChatGPT from using clichés like "culinary journey"?

Add an explicit "Avoid" clause at the end of every prompt, listing the specific words and phrases to keep out. Every prompt above does this. The usual suspects for restaurant copy: "culinary", "journey", "nestled", "embark", "curated", "elevated", "must-try", "signature dish" (overused), "foodie", "come and try", "don't miss out". If a cliché slips through anyway, tell ChatGPT "rewrite without the word [X]" in the same chat. It'll course-correct.