Restaurant Reservation Deposit Refund Support Workflow Builder

Build a support workflow for restaurant reservation deposit refund requests with policy checks, evidence review, empathy macros, escalation paths, and chargeback prevention.

Prompt Template

You are a hospitality support operations lead creating a workflow for restaurant reservation deposit, cancellation fee, or no-show fee disputes. Build the workflow for:

Restaurant type: [fine dining, tasting menu, event space, casual group dining, holiday brunch, private room]
Booking model: [deposit, prepaid menu, cancellation fee, no-show fee, card hold, third-party booking platform]
Policy details: [cancellation window, refund rules, reschedule rules, weather policy, illness exception, group minimum]
Customer issue: [cancelled late, duplicate booking, platform error, illness, travel delay, weather, wrong date, no-show dispute]
Systems available: [reservation platform, POS, email, SMS, phone logs, payment processor, CRM, helpdesk]
Evidence sources: [booking confirmation, policy acceptance, cancellation timestamp, customer messages, staff notes, payment record]
Customer segment: [regular guest, first-time guest, private dining client, VIP, tourist, corporate organizer]
Escalation risks: [chargeback, social complaint, legal threat, discrimination concern, food safety illness claim, staff error]
Communication channels: [email, phone, SMS, reservation platform, social DM]
Tone: [warm, accountable, concise, premium, neighborhood-friendly, firm but kind]

Create:
1. Intake checklist for booking, policy, timestamps, payment, guest story, and desired resolution.
2. Decision tree for refund, partial refund, reschedule credit, policy explanation, manager review, or escalation.
3. Customer macros for late cancellation, duplicate booking, platform error, illness, weather, and no-show dispute.
4. Evidence checklist that avoids collecting unnecessary sensitive information.
5. Manager escalation template with facts, risk, recommendation, and deadline.
6. Chargeback prevention steps including clear receipts, policy references, and respectful follow-up.
7. Policy-safe language for refunds and credits using only supplied restaurant rules.
8. Exception log structure for fairness and future policy review.
9. QA checklist for empathy, accuracy, consistency, and tone.
10. Metrics dashboard for refund requests, exceptions, chargebacks, repeat issues, and guest recovery.

Do not invent consumer rights, payment timelines, medical exceptions, platform rules, or local laws. Flag uncertain cases for manager, legal, or payment processor review.

Example Output

Triage Path

Confirm the reservation ID, booking date, cancellation timestamp, deposit amount, policy shown at booking, and what the guest is requesting. If staff error or platform error is plausible, route to manager review before sending a firm policy response.

Macro: Late Cancellation

Hi [Name], I am sorry your plans changed. I reviewed reservation [ID] for [date] and see the cancellation came in [x] hours before the booking. Our policy shown at booking is [policy]. Based on that, I can offer [approved option]. If there is context we should review, I can send this to a manager with the booking details.

Exception Log

Track reason, amount, approver, guest segment, evidence, and whether the exception prevented a chargeback or rebooked the guest.

Tips for Best Results

  • 💡Use timestamps and policy acceptance before making a decision.
  • 💡Give managers a concise fact packet so emotional disputes do not become messy threads.
  • 💡Track exceptions for fairness; one-off generosity can turn into policy drift.
  • 💡Avoid asking for sensitive medical details when an illness exception can be handled with simpler information.