Communication & Enforcement

Clear communication and consistent enforcement are key to an effective cancellation policy that protects your business while maintaining customer relationships.

Customer Communication

Policy Display on Booking Page

Your policy must be clear and prominent during the booking process.

Display Requirements:

• Shown before payment information
• Clear, easy-to-read formatting
• Checkbox acknowledgment required
• Link to full terms and conditions
• Cancellation deadline calculator

Best Practices:

• Use simple, non-legal language
• Highlight key points (window, penalties)
• Show specific deadline for this booking
• Make checkbox statement clear
• Include "Why we have this policy" explanation (optional)

Confirmation Email

The booking confirmation email should include:

Policy Section:

• Full policy details clearly stated
• Specific cancellation deadline for this reservation
• How to cancel (link/phone/email)
• What happens if they cancel late or no-show
• Contact information for questions

Example Structure:

Your Reservation Details
[Date, time, party size, venue]

Cancellation Policy
You may cancel free of charge until [specific date/time].
Cancellations after this time may incur a [penalty details].
No-shows will be charged [no-show penalty].

To cancel: Click here [link] or call us at [phone]

Questions? Contact us at [email/phone]

Reminder Communications

Include policy information in reminder emails and SMS:

24-Hour Reminder:

• Upcoming reservation details
• Cancellation deadline clearly stated
• Easy cancellation link
• Encouragement to cancel if plans change

2-Hour Reminder:

• Final reminder
• "Past cancellation deadline" note (if applicable)
• See you soon message
• Directions/parking info

Policy Wording

Creating Effective Policy Text

Your policy text should be:

Clear ✓ "Cancel at least 24 hours before your reservation" ✗ "Cancellations must be received no less than one business day prior to scheduled dining experience"

Specific ✓ "Late cancellations incur a £15 per person fee" ✗ "Fees may apply to cancellations"

Friendly but Firm ✓ "We understand plans change, but to serve all our guests fairly, we need 24 hours notice" ✗ "Violations of cancellation policy will be prosecuted"

Honest ✓ "This helps us offer your table to other guests and reduce food waste" ✗ "This is legally required" (unless it actually is)

Policy Template

Customize this template for your venue:

Cancellation Policy

We understand that plans change. To help us serve all our guests 
fairly and reduce food waste, we ask for [WINDOW] notice for 
cancellations.

Cancellation Terms:
• Cancel [WINDOW] or more before your reservation: No charge
• Cancel with less notice: [PENALTY]
• No-shows: [NO-SHOW PENALTY]

[If deposits required:]
A [AMOUNT] deposit per person is required to secure your booking. 
This will be deducted from your final bill or refunded if you 
cancel with adequate notice.

We appreciate your understanding and look forward to serving you!

To cancel: [CANCELLATION METHOD]
Questions? Contact us at [CONTACT INFO]

Tone by Venue Type

Casual Dining:

• Friendly and approachable
• Brief and to the point
• Less formal language

Fine Dining:

• Professional and courteous
• More detailed explanation
• Slightly more formal

Family/Pub:

• Warm and understanding
• Emphasize flexibility
• Conversational tone

Example - Casual:

"Hey! Plans change, we get it. Just give us 2 hours heads up if you need to cancel, and we're all good. Less notice and we might need to charge a small £5 fee. Thanks for understanding!"

Example - Fine Dining:

"To ensure we can provide an exceptional experience for all our guests, we kindly request at least 48 hours notice for cancellations. Cancellations with less notice will incur a charge of 50% of your estimated dining cost. We appreciate your understanding."

Automatic Enforcement

The system handles most enforcement automatically.

How Automatic Enforcement Works

1. Booking Made

• Policy attached to reservation
• Customer acknowledges terms
• Deadline calculated and stored

2. Cancellation Requested

• System records exact cancellation time
• Compares to cancellation deadline
• Determines if penalty applies

3. Penalty Applied (if applicable)

• Calculates penalty amount
• Processes payment (if card on file)
• Updates reservation status to "Cancelled - Late"

4. Notifications Sent

• Customer receives cancellation confirmation
• Lists any charges applied
• Explains reasoning
• Provides contact for questions

5. Records Updated

• Booking marked as cancelled
• Table released back to availability
• Financial records updated
• Customer history noted

What Gets Automated

✓ Fully Automated:

• Deadline calculation
• Time compliance checking
• Penalty calculation
• Payment processing
• Email notifications
• Status updates
• Reporting

✓ Semi-Automated:

• No-show detection (with grace period)
• Dispute flagging
• Exception recommendations

Manual Overrides

Sometimes you need to override the policy.

When to Override

Appropriate Overrides:

• Genuine documented emergencies (medical, family)
• Severe weather or transport disruptions
• Venue error or mistake
• System technical issues
• First-time issue with loyal customer
• Good customer service opportunity

Questionable Overrides:

• "Just forgot" (enforce for consistency)
• Frequent offenders
• No valid reason provided
• During high-demand periods

How to Process Overrides

Steps:

1. Open the reservation
2. Click "Cancel Reservation"
3. Select cancellation reason from dropdown
4. Choose override option:
   • Waive penalty entirely - No charge at all
   • Apply partial penalty - Reduced amount
   • Apply full penalty - Enforce policy
   • Custom amount - Specific charge
5. Add detailed note explaining decision
6. Confirm cancellation

Documentation Requirements:

• Reason for override
• Staff member who approved
• Date/time of decision
• Customer communication
• Any supporting evidence

Override Authority Levels

Set who can override policies:

Manager Level:

• Waive up to £50 in penalties
• Apply partial penalties
• Grant exceptions

Owner Level:

• Waive any amount
• Create blanket exceptions
• Override for VIP customers

Staff Level:

• Process standard cancellations
• Flag issues for manager
• Cannot override without approval

No-Show Handling

No-Show Detection

The system identifies no-shows automatically:

Automatic Detection:

• Reservation time + grace period passes
• Guest hasn't arrived (no "Seated" status)
• No cancellation received
• Automatically marked as "No-Show"

Grace Period:

• Default: 15 minutes after reservation time
• Configurable: 10-30 minutes
• Accounts for traffic, parking
• Good faith accommodation

Manual Marking:

• Staff can mark as no-show earlier
• Required reason selection
• Timestamp recorded
• Override if guest arrives

No-Show Consequences

Define what happens after a no-show:

Financial:

• Charge penalty per policy (typically 50-100% of estimated bill)
• Forfeit any deposit held
• Process payment immediately
• Send invoice email

Account Status:

• Flag customer record
• Note incident in history
• May affect future booking privileges

Future Bookings:

• First no-show: Warning
• Second no-show: Require deposit
• Third no-show: Require full prepayment
• Fourth+ no-show: Restrict booking ability

No-Show Recovery Process

Turn negative situations into opportunities:

Immediate (Day of No-Show):

1. Mark as no-show in system
2. Process penalty payment
3. Send notification explaining charge
4. Provide contact information

Follow-Up (Next Day):

1. Send recovery email: "We missed you yesterday"
2. Ask what happened (reply mechanism)
3. Provide feedback opportunity
4. Offer to help rebook

Resolution:

• Address genuine emergencies with compassion
• Waive penalty if documented emergency
• Offer to rebook with appropriate policy
• Maintain relationship if possible

Exception Handling

Compassionate Exceptions

Some circumstances warrant automatic exceptions:

Automatic Exception Triggers:

• Documented medical emergency
• Death in family
• Natural disasters
• Official travel advisories
• Venue-initiated cancellation (your closure)

Process:

1. Customer contacts venue with situation
2. Explains circumstance
3. Provides documentation (if available/appropriate)
4. Staff reviews situation
5. Grants exception or applies standard policy
6. Documents decision and reasoning
7. Communicates outcome clearly

VIP & Regular Customer Treatment

Special handling for valued customers:

Recommended Approach:

• First incident: Automatic exception (everyone gets one)
• Loyal customers (20+ bookings): 1-2 exceptions per year
• High-value customers: Discretionary flexibility
• New customers: Standard policy

Configuration:

1. Navigate to customer record
2. Set "VIP Status" if applicable
3. Define exception allowance
4. Track exceptions used
5. Reset annually

Grace Period Settings

Configure grace periods for edge cases:

Booking Grace Period:

• Brief cushion for technical issues (5-10 minutes)
• Network problems don't penalize customer
• System downtime protection
• Good faith accommodation

Arrival Grace Period:

• 15 minutes after reservation time (default)
• Traffic, parking issues
• Before no-show triggered
• Configurable 10-30 minutes

Refund Grace Period:

• Brief window after penalty charged
• Allow customer to dispute quickly
• Easy reversal for errors
• Typically 24 hours

Staff Training

Ensure your team handles policies consistently:

Training Topics

Understanding the Policy:

• Policy details and reasoning
• How it protects the business
• Benefits to customers
• Common questions

System Operation:

• How to view policy on bookings
• Processing cancellations
• Applying overrides
• Handling disputes

Customer Communication:

• Explaining policy clearly
• Handling complaints
• When to escalate
• Maintaining professionalism

Edge Cases:

• Emergency situations
• System issues
• Payment problems
• Multiple violations

Training Resources

Provide staff with:

• Policy reference card
• FAQ document
• Override authority levels
• Escalation contacts
• Example responses to common situations

Dispute Resolution

Prepare for occasional disputes:

Common Disputes

"I cancelled and didn't get my refund"

• Check system logs for cancellation
• Verify timing against policy
• Explain refund timeline (5-7 days)
• Provide transaction confirmation

"The policy wasn't clear"

• Show booking confirmation
• Point to policy acknowledgment
• Explain where it was displayed
• Consider exception if genuinely unclear

"This is an emergency"

• Listen compassionately
• Request documentation if appropriate
• Apply emergency exception process
• Document situation

"I didn't receive reminders"

• Check email/SMS logs
• Verify contact information
• Resend if technical issue
• Consider exception for first occurrence

Escalation Path

Clear escalation process:

Level 1: Front Staff

• Receive complaint
• Gather information
• Apply standard resolution
• Document interaction

Level 2: Manager

• Review documentation
• Apply override authority if appropriate
• Make exception decisions
• Communicate resolution

Level 3: Owner

• Handle complex disputes
• Make final decisions
• Set precedents
• Update policy if needed

Related Documentation

• Cancellation Overview - Policy basics and setup
• Policy Configuration - Detailed settings and rules
• Deposits & Refunds - Managing payments
• Analytics & Best Practices - Measuring effectiveness

Need Help?

Questions about enforcement or customer communication?

• Email: [email protected]
• WhatsApp: https://wa.me/message/GPBDMIVKYIELE1