25 ChatGPT Prompts for Restaurants (Copy & Paste)

RESTAURANT FACT PACK

Restaurant name: [name]
Concept and cuisine: [one sentence]
Location or neighborhood: [location]
Audience: [who the message is for]
Brand voice: [three adjectives]
Words or styles to avoid: [list]

Verified menu facts:
- [dish, ingredients, price, availability]
- [dish, ingredients, price, availability]

Verified offer or event facts:
- [dates and times]
- [price or discount]
- [eligibility and exclusions]
- [capacity or availability, if confirmed]
- [booking or ordering URL]

Instruction: Use only the facts supplied here. Do not invent
ingredients, allergens, prices, dates, availability, awards, sourcing,
discounts, or policies. Mark missing information as [NEEDS INPUT].

You are editing menu copy for [restaurant name], a [concept] in
[location]. Rewrite the verified information below as one appetizing
menu description of 18–28 words.

Dish name: [name]
Verified ingredients and preparation: [details]
Price: [price or "do not include"]
Brand voice: [three adjectives]

Lead with the most distinctive flavor, ingredient, or preparation.
Avoid clichés such as "mouthwatering," "cooked to perfection," and
"a culinary journey." Do not add ingredients, dietary labels,
sourcing claims, or preparation methods. If an essential detail is
missing, write [NEEDS INPUT] instead of guessing.

Edit the menu descriptions pasted below so they feel as if one person
wrote them. Keep every dish name and factual detail unchanged.

House style:
- 15–25 words per description
- [casual / polished / playful] tone
- sentence fragments are [allowed / not allowed]
- mention preparation before accompaniment
- no unsupported superlatives or health claims

Return a two-column table: Dish | Revised description. After the table,
list any conflicting, vague, or apparently missing source information.

MENU COPY:
[paste current descriptions]

Convert these approved dine-in menu descriptions into clear online
ordering copy for [restaurant name]. A guest should be able to understand
what the item is without asking a server.

For each item:
1. write a description of no more than 30 words;
2. preserve all verified ingredients and preparation details;
3. state included sides only when they appear in the source;
4. do not promise customization or availability;
5. do not infer allergens or dietary suitability.

Return: Item name | Ordering description | Missing information to check.

SOURCE MENU:
[paste approved item data]

Help our chef brainstorm a limited special. This is an internal ideation
task, not a finished recipe or public menu claim.

Restaurant concept: [concept]
Service period: [lunch / dinner / brunch]
Ingredients we want to feature: [list]
Equipment or station constraints: [details]
Target food-cost or price constraint: [details, if available]
Items that must not be suggested: [list]

Propose five concepts. For each, give a working name, a one-sentence
idea, the operational complication most likely to slow service, and
questions the chef must resolve before testing. Do not label any concept
allergen-free, vegan, gluten-free, or compliant with a dietary need.

Write three caption options for a real photo from [restaurant name].

What the photo shows: [specific description]
Verified dish details: [ingredients and preparation]
Reason for posting now: [new item / seasonal return / staff favorite]
Audience: [local regulars / lunch crowd / visitors]
Brand voice: [three adjectives]
Call to action: [book / order / visit / none]
Link or location detail: [verified information]

Create:
- one Instagram caption, 40–70 words;
- one Facebook caption, 25–50 words;
- one caption under 20 words.

Use at most two relevant hashtags. Do not invent scarcity, customer
reactions, awards, ingredients, or sourcing claims.

Create a realistic five-post plan for [restaurant name] using only the
assets and events listed below. Do not create a post for every day unless
the available material supports it.

Business goal this week: [goal]
Audience: [audience]
Platforms: [platforms]
Available photos or video: [asset list]
Confirmed menu or event facts: [fact pack]
Brand voice: [voice]

Return a table with: Day | Platform | Post purpose | Asset to use |
Caption draft | Call to action. Vary the purpose and structure of the
posts. Mark any post that needs a new photo or missing fact.

Turn the notes below into a behind-the-scenes social post for
[restaurant name]. Explain the process in language a guest can understand
without oversimplifying it.

Process: [for example, shaping pasta or smoking brisket]
Staff member to credit: [approved name and role, or omit]
Verified operational details: [time, technique, ingredients]
Why guests might care: [texture, flavor, tradition, less waste]
Photo or video: [what viewers will see]
Platform: [Instagram / Facebook / TikTok]

Write a hook and caption. Do not invent quotations, personal history,
proprietary details, or claims such as "made fresh daily" unless supplied.

Adapt the approved announcement below for three social placements:
1. an Instagram feed caption under 80 words;
2. a three-frame Story, with no more than 12 words per frame;
3. a Google Business Profile update under 100 words.

Preserve the offer terms, dates, times, price, and URL exactly. Keep the
brand voice [voice]. Give each version a clear next step. Do not add
urgency or availability claims that are not in the source.

APPROVED ANNOUNCEMENT:
[paste text]

Draft a promotional email announcing the seasonal menu at
[restaurant name].

Audience segment: [segment]
Main reason to visit: [specific angle]
Featured items and verified descriptions: [details]
Launch date and availability: [details]
Booking or ordering link: [URL]
Brand voice: [voice]

Return:
- two accurate subject lines under 45 characters;
- one preheader under 80 characters;
- a body of 120–170 words;
- one call-to-action button label.

Use only supplied facts. Do not claim that an item is "back by popular
demand," limited, exclusive, local, or house-made unless stated above.

Write an email for guests who have opted in to restaurant promotions.
The goal is to encourage visits during [day and service period].

Restaurant: [name and concept]
Audience: [segment]
Verified offer: [complete terms]
Valid dates and times: [details]
Exclusions: [details]
Redemption steps: [details]
URL: [link]
Tone: [tone]

Keep the body under 140 words. State the essential terms in plain
language near the call to action. Do not invent a deadline, savings
amount, availability limit, or reason for the offer.

Draft a re-engagement email for an opted-in segment that has not visited
in [time period]. Do not imply that the owner personally noticed an
individual guest's absence.

Restaurant: [name]
What has genuinely changed or is worth revisiting: [details]
Offer, if any: [full approved terms or "none"]
Audience: [segment description]
Brand voice: [voice]
URL: [link]

Write three subject lines and a body under 130 words. Sound welcoming,
not intrusive. Do not refer to personal order history or past visits in
the copy unless that use has been approved for this campaign.

Edit the restaurant email below so it sounds specific to our business.
Do not change any factual detail or offer term.

Brand examples:
[paste two short examples of approved copy]

Words and habits to remove:
[for example: foodie, mouthwatering, culinary journey, excessive emojis]

Return:
1. the revised email;
2. a short list of generic phrases you replaced;
3. every factual statement a manager should verify before sending.

DRAFT EMAIL:
[paste draft]

Draft a public response to the review below for [restaurant name].

Thank the guest, mention one specific detail they appreciated, and give
a natural invitation to return. Do not repeat the whole review, mention
the star rating, or add facts about the guest. Use 45–70 words and our
[warm / concise / playful] voice. Provide two versions.

REVIEW:
[paste public review]

Draft a calm public response to this restaurant review.

Public review: [paste text]
Verified incident facts approved for public use: [facts or "none"]
Resolution the manager is authorized to offer publicly: [details]
Private contact method: [email or phone]
Brand voice: [voice]

Acknowledge the specific concern without arguing or admitting facts that
have not been established. Do not blame the guest or an employee. Do not
promise a refund, discount, or outcome beyond the authorized resolution.
Keep the response under 100 words. If the issue meets an escalation rule,
return ESCALATE instead of a draft.

Analyze the public restaurant reviews pasted below. This is an internal
operations task.

Group comments into themes such as food quality, order accuracy, wait
time, hospitality, value, cleanliness, and atmosphere. Separate repeated
patterns from isolated comments. For each theme, provide:
- number of reviews mentioning it;
- positive, negative, or mixed direction;
- short supporting excerpts;
- one question a manager should investigate.

Do not guess causes, employee identities, or facts outside the reviews.
End with the three highest-priority issues based on frequency and likely
guest impact. Explain the ranking briefly.

REVIEWS:
[paste anonymized public review text]

Create a small campaign pack for this confirmed restaurant event.

Restaurant and location: [details]
Event: [name and description]
Date and time: [details]
Price and what it includes: [details]
Capacity or availability: [verified detail or omit]
Booking method: [URL or phone]
Cancellation terms: [approved wording]
Audience: [audience]
Brand voice: [voice]

Write:
1. a website description of 120–160 words;
2. an email announcement under 140 words;
3. an Instagram caption under 70 words;
4. a 20-word in-store sign.

Keep all operational facts identical across the four versions. Do not
invent performers, menu items, scarcity, or what guests will experience.

Help us compare three possible promotions for a quiet [daypart]. Do not
write public copy yet.

Restaurant concept: [concept]
Business goal: [for example, more Tuesday dine-in covers]
Audience: [audience]
Average check or margin constraints we can share: [details]
Operational limits: [kitchen capacity, staffing, excluded items]
Possible offers: [offer A], [offer B], [offer C]

Compare each offer on guest clarity, operational complexity, risk of
discounting existing demand, data needed to measure it, and likely abuse
or confusion. Do not predict revenue. Recommend which offer is simplest
to test and state the assumptions behind that recommendation.

Rewrite these approved restaurant offer terms in plain English without
changing their meaning.

OFFER TERMS:
[paste exact terms]

Create:
- a one-sentence headline;
- a short description;
- a scannable terms line;
- a staff explanation for guests who ask how it works.

Preserve every date, time, location, item, exclusion, redemption rule,
and limit. Flag contradictions or missing details instead of resolving
them yourself.

Draft a final reminder for the confirmed event below.

Event details: [fact pack]
Current availability: [verified number/status or "do not mention"]
Audience: [people who received the announcement but have not booked]
Channel: [email / social]
Brand voice: [voice]

Write a concise reminder that gives the date, main reason to attend, and
booking action. Use urgency only if a real deadline or verified capacity
fact is supplied. Do not use "selling fast," "almost gone," or similar
language without evidence.

Organize the verified notes below into a briefing a manager can read to
the team in 90 seconds.

Use these headings: Service | Menu | Reservations & events | Staffing |
Watch-outs. Put the most time-sensitive item first. Preserve names,
times, counts, 86'd items, and assigned responsibilities exactly. Do not
add advice or fill gaps. End with a checklist titled "Manager verifies."

SHIFT NOTES:
[paste notes without unnecessary personal information]

Draft a concise email from [restaurant name] to [supplier].

Purpose: [late delivery / quality issue / availability question / order
clarification]
Purchase order or invoice reference: [reference]
Verified dates, quantities, and products: [details]
Requested next step: [specific action]
Required response time: [deadline, if approved]
Tone: direct and professional

Do not add contract terms, blame, financial deductions, or threats. Use
[NEEDS INPUT] if the requested resolution or timeline is unclear.

Create a five-minute training role-play for a [server / host / shift
manager] handling [a cold entrée / a long wait / an incorrect takeout
order].

Our approved recovery steps: [paste policy]
Decisions this role may make without a manager: [details]
When to escalate: [rules]
Tone expected from staff: [details]

Provide the guest's opening complaint, the employee's response, one
follow-up complication, and a short debrief with three coaching points.
Do not offer compensation outside the policy.

Create a short staff knowledge check using only the approved procedure
below.

Audience: [role and experience level]
Format: five multiple-choice questions and two short scenarios
Passing standard: [standard]

Make wrong answers plausible enough to test understanding, but do not
introduce practices that are absent from the source. Give an answer key
with the exact section of the procedure supporting each answer. Flag any
part of the source that is ambiguous.

APPROVED PROCEDURE:
[paste text]

Turn the meeting notes below into a decision record.

Return four sections:
1. Decisions made
2. Actions: owner | task | deadline
3. Open questions
4. Risks or dependencies explicitly mentioned

Do not convert suggestions into decisions. Do not assign an owner or
deadline unless the notes name one. Mark missing fields as [UNASSIGNED]
or [NO DEADLINE].

MEETING NOTES:
[paste notes]

Translate the approved guest message below from [source language] into
[target language] for [restaurant location and audience].

Preserve dish names, prices, dates, URLs, offer terms, and proper nouns
exactly. Use natural, hospitable language rather than a word-for-word
translation. If a phrase could have more than one meaning, flag it instead
of choosing silently.

Return:
1. the translated message;
2. a literal back-translation into [source language];
3. a list of terms a fluent staff member should review.

APPROVED MESSAGE:
[paste text]

Audit the draft against the source facts below. Create a table with:
Draft claim | Supporting source fact | Status.

Use only these status labels:
- SUPPORTED
- CONTRADICTED
- NOT IN SOURCE
- NEEDS HUMAN JUDGMENT

Check every ingredient, preparation method, dietary label, price, date,
time, offer term, availability statement, location, URL, award, and
sourcing claim. Do not rewrite the draft yet.

SOURCE FACTS:
[paste fact pack]

DRAFT:
[paste output]