Bottom line
A restaurant check or receipt is issued, a split or fee requires correction, or a charge, tip, service charge, authorization, refund, duplicate, dispute, or chargeback exception arises.
Best for
Full-service, fast-casual, quick-service, fine-dining, café, bar-and-grill, and private-dining restaurant operators.
Use when
Only after the project, service, account, and exception records are current and match.
Watch for
Automated medical, allergen-safety, foodborne-illness, regulator, alcohol-safety, accessibility-rights, fraud, liability, chargeback, or legal decisions.
How to Use This Email
When to use this
A restaurant check or receipt is issued, a split or fee requires correction, or a charge, tip, service charge, authorization, refund, duplicate, dispute, or chargeback exception arises.
What’s on their mind
A guest may mistake a card authorization for a duplicate charge or confuse a required service charge with a discretionary tip.
What this email should do
After service, trust depends on explaining the check and separating restaurant actions from processor and bank-managed payment states.
Best sender
Host event manager or billing owner
Read the Finished Email
Review the message as a recipient would see it. The names and business details are fictional.
Subject
Review restaurant check REF-1042Hi the current details,
Check REF-1042 for visit or order REF-1042 is ready for review: https://example.com/next-step
- Itemized and check: the current details
- Fee, tax and total: $240
- Payment and reconciliation: the current details
- Dispute and closeout: the current details
Review the details and choose the next step: https://example.com/next-step
Do not email card numbers or security codes. Authorization, capture, restaurant refund, processor acceptance, issuer posting, and chargeback are separate states.
Alex Morgan · (555) 014-0182
Northstar Services
Template to copy
Subject
Review restaurant check [Check reference]Hi [Verified guest or payer],
Check [Check reference] for visit or order [Visit or order reference] is ready for review: [Check link]
- Itemized and check: [Itemized check summary]
- Fee, tax and total: [Fee tax total summary]
- Payment and reconciliation: [Payment reconciliation summary]
- Dispute and closeout: [Dispute closeout summary]
Review the details and choose the next step: [Check link]
Do not email card numbers or security codes. Authorization, capture, restaurant refund, processor acceptance, issuer posting, and chargeback are separate states.
[Billing owner] · [Phone number]
[Company name]
Subject Line Variations
- Review restaurant check [Check reference]
References the actual operating record or decision.
- Check, Charge, Service Fee, Tip, Refund, And Dispute: [Reference number]
Direct operational alternative.
- Update from [Company name] about [Reference number]
Use with a recognized business and valid reference.
Best for
- Full-service, fast-casual, quick-service, fine-dining, café, bar-and-grill, and private-dining restaurant operators.
- Restaurants able to synchronize reservations, tables, menus, recipes, suppliers, kitchen, fulfillment, incidents, checks, payment, and accounting records.
- Teams coordinating guests, hosts, servers, kitchen, managers, event contacts, couriers, and payers.
Don’t send this if
- Automated medical, allergen-safety, foodborne-illness, regulator, alcohol-safety, accessibility-rights, fraud, liability, chargeback, or legal decisions.
- Messages that expose full card data, private health details, customer addresses, access credentials, employee-sensitive records, or other guests' incident information.
- Marketing copy without live table, recipe, ingredient, kitchen, custody, safety, and payment records.
When to Send It
Trigger
A restaurant check or receipt is issued, a split or fee requires correction, or a charge, tip, service charge, authorization, refund, duplicate, dispute, or chargeback exception arises.
Timing
Only after the project, service, account, and exception records are current and match.
Frequency
Once for each valid event or confirmed update; reminders must retain the same verified obligation or decision.
Timing note
Use only a real operational deadline, safety escalation, weather window, or live allocation window.
Make This Email Yours
- Use current party, reservation, table, accessible feature, menu and recipe, ingredient and supplier, guest-stated food need, preparation control, order, kitchen, courier, custody, incident, check, fee, payment, and owner records.
- Use minimum necessary disability, medical, guest, employee, address, incident, and payment information; keep full card data, credentials, private health detail, and other guests' records out of ordinary email.
- Pause for active reaction, choking, illness emergency, fire, violence, imminent public-health risk, unsafe facility state, alcohol safety concern, regulator or responder control, compromise, chargeback, evidence or legal hold, or manager control.
Before You Use This Email
Why This Approach Works
Platform Setup Steps
Trigger
A restaurant check or receipt is issued, a split or fee requires correction, or a charge, tip, service charge, authorization, refund, duplicate, dispute, or chargeback exception arises.
Segment
Verified guest, reservation booker, diner, large-party or event contact, payer, pickup customer, courier, manager, supplier, or responsible restaurant stakeholder for one current reservation, order, visit, incident, or check.
Delay
Send after the record is reconciled and before the next dependent operational action.
Reply owner: Billing owner responsible for itemized source records, fee and tip treatment, tax and total, tender and payment-state reconciliation, disputed-line workflow, refund evidence, secure receipt delivery, and closeout.
- Verify restaurant, reservation, party or order, recipient authority, current table or recipe and ingredient version, food-need or incident state, channel, owner, and timing.
- Send minimum necessary facts with one clear confirmation, approval, table, substitution, custody, report, dispute, or manager action.
- Record the decision and supporting evidence; suppress superseded automation; reconcile CRM, reservation, waitlist, table, menu, recipe, supplier, POS, kitchen display, order, delivery platform, incident, payment, and accounting systems.
Stop conditions
- A valid decision, superseding reservation, party, seating, menu, recipe, allergen, order, kitchen, pickup, delivery, incident, check, payment, refund, or dispute record, cancellation, reply, or live handling.
- Guest, party, accessible feature, table, time, menu, ingredient, recipe, allergen, cross-contact control, item, quantity, substitution, price, kitchen state, courier, custody, safety, charge, fee, tip, refund, or deadline change.
- Active allergic reaction, choking, medical event, fire, violence, suspected foodborne illness cluster or imminent public-health risk, unsafe food or facility condition, abuse or harassment, alcohol or intoxication safety concern, suspected fraud or account compromise, regulator or responder control, chargeback, evidence or legal hold, or qualified manager control.
Mistakes To Avoid
- Treating a reservation note or menu label as an allergen guarantee
Recipes, suppliers, shared equipment, garnishes, and preparation can change.
Use instead: Reconcile the exact item with current sources and cross-contact controls under the person in charge.
- Combining service charge, tip, authorization, refund, and bank posting
Each can have a different legal, operational, and payment-system meaning.
Use instead: Itemize the check and name each payment state, reference, and responsible party.
Sequence Placement
Use only for the verified restaurant reservation, order, visit, incident, or check represented by current systems; suppress when stale, superseded, cancelled, unsafe, disputed, compromised, or controlled by emergency, person in charge, health authority, responder, accessibility, payment, insurer, legal, or qualified manager review.
Related Email Platform Guidance
teams running behavior-based nurture with branching, scoring, and segmentation
Not best for: teams whose requirements stop at newsletters and a short welcome series
View ActiveCampaignPaid linkagencies standardizing lead-response systems across multiple accounts
Not best for: teams expecting a native field-service or legal practice-management system
View GoHighLevelPaid linkB2B organizations aligning marketing, sales, and service around shared CRM data
Not best for: small teams needing only broadcasts and a simple welcome sequence
View HubSpot
Disclosure
Some platform links on this page are paid links. If you choose a platform through one of them, EmailCampaigns.io may earn a commission. That does not change our recommendations. We include best for and not best for notes so you can decide based on fit, not payout.