Call volume distribution:
├── Lunch rush (11:30-13:30): 25% of daily calls
├── Dinner rush (18:00-21:00): 45% of daily calls
├── Off-peak hours: 20% of daily calls
├── Closed hours: 10% of daily calls

Staff availability reality:
├── During service: Host handling arrivals, can't answer
├── Between services: Often only kitchen staff present
├── Closed: No one available
├── Staff multitasking: Phone often lowest priority

Average missed calls:
├── Daily missed: 15-30 calls
├── Weekend missed: 25-50 calls
├── Monthly missed: 400-800 calls
├── Peak event days: Up to 100 missed

Monthly missed calls: 500
├── Reservation intent: 70% (350)
├── Would have booked: 60% (210)
├── Average party size: 3 people
├── Average spend: €40/person
├── Potential revenue: €25,200/month

Lost revenue from missed calls: €25,200
Annual loss: €302,400

Additional losses:
├── No-show rate higher without confirmation calls
├── Inefficient table management
├── Staff frustration
└── Poor customer experience

Reservations (65%):
├── "I'd like to book a table for Saturday"
├── "Do you have availability tonight?"
├── "Can I change my reservation?"
├── "I need to cancel my booking"
└── "Do you take large group reservations?"

Information (25%):
├── "What time do you close?"
├── "Do you have vegetarian options?"
├── "Is there parking nearby?"
├── "What's your address?"
├── "Do you have outdoor seating?"
└── "What's on the menu?"

Special requests (10%):
├── "Do you accommodate allergies?"
├── "Can I bring a birthday cake?"
├── "Is there a private dining room?"
├── "Do you have highchairs?"
└── "Can I speak to the manager?"

Reservation management:
├── New bookings
├── Modifications
├── Cancellations
├── Confirmations
├── Waitlist management
└── Party size handling

Information queries:
├── Hours of operation
├── Location and directions
├── Menu highlights
├── Dietary accommodations
├── Special features
└── Parking information

Operational support:
├── No-show prevention calls
├── Confirmation reminders
├── Capacity management
├── Special event handling
└── Overflow call routing

Caller: [Dials restaurant]

Voicebot: "Thank you for calling Bella Italia. 
I can help you with reservations, hours, 
and menu information. How can I help you?"

Caller: "I'd like to book a table for 
        Saturday night."

Voicebot: "I'd be happy to help with a Saturday 
reservation. How many people will be dining?"

Caller: "Four people"

Voicebot: "Perfect, a table for 4 on Saturday.
What time would you prefer?

We have availability at:
• 18:00
• 18:30
• 20:30
• 21:00

Note: Our 19:00-20:00 slots are currently 
full, but I can add you to the waitlist."

Caller: "20:30 works great"

Voicebot: "Excellent! I have a table for 4 at 
20:30 on Saturday, January 18th.

May I have your name for the reservation?"

Caller: "Maria Johnson"

Voicebot: "Thank you, Maria. And a phone number 
in case we need to reach you?"

Caller: "555-123-4567"

Voicebot: "Perfect! Let me confirm:

📅 Saturday, January 18th at 20:30
👥 Table for 4
👤 Name: Maria Johnson
📱 Contact: 555-123-4567

Any special requests-highchair, 
dietary restrictions, special occasion?"

Caller: "Actually, it's my husband's birthday"

Voicebot: "How wonderful! I've noted that it's 
a birthday celebration. We'll make sure 
the evening is special.

Would you like us to bring a complimentary 
dessert with a candle?"

Caller: "That would be great, thank you!"

Voicebot: "My pleasure! You'll receive a 
confirmation text shortly. We ask that you 
arrive 10 minutes before your reservation 
time. If your plans change, please call 
us at least 4 hours in advance.

Is there anything else I can help with?"

Caller: "No, that's all. Thanks!"

Voicebot: "Thank you for choosing Bella Italia. 
We look forward to celebrating with you 
on Saturday. Goodbye!"

Caller: "Table for 6 tonight at 7 PM?"

Voicebot: "Let me check availability for 6 guests 
at 19:00 tonight...

I'm sorry, we're fully booked at 19:00. 
However, I do have some alternatives:

Option 1: Tonight at 17:30 (early dinner)
Option 2: Tonight at 21:15 (late seating)
Option 3: Tomorrow at 19:00 (same time)

I can also add you to tonight's waitlist at 
19:00-if a cancellation comes in, we'll 
call you immediately.

Which would you prefer?"

Caller: "Put us on the waitlist, 
        and book 21:15 as backup"

Voicebot: "Smart choice! I've done both:

✅ Waitlist: Tonight 19:00 for 6 guests
   (We'll call 555-123-4567 if a spot opens)

✅ Confirmed: Tonight 21:15 for 6 guests

If we can seat you at 19:00, I'll automatically 
cancel the 21:15 booking. Otherwise, we'll 
see you at 21:15.

May I have a name for the reservations?"

Caller: "Hi, I have some questions before booking"

Voicebot: "Of course! I'm happy to help with any 
questions about our restaurant."

Caller: "Do you have gluten-free options? 
        My wife has celiac disease."

Voicebot: "Absolutely! We take allergies very 
seriously. For celiac disease:

Gluten-free options available:
├── Dedicated gluten-free pasta
├── Risotto dishes (naturally GF)
├── Grilled fish and meat entrées
├── Most appetizers can be modified
└── Gluten-free dessert options

Our kitchen has separate prep areas for 
allergen-sensitive dishes, and our staff 
is trained in cross-contamination prevention.

I'd recommend mentioning the celiac requirement 
when you book, so the kitchen is prepared.

Would you like to make a reservation now?"

Caller: "Yes, what's available Friday night?"

Reservation platforms:
├── OpenTable integration
├── Resy connection
├── TheFork/TripAdvisor
├── In-house booking system
└── Google Reserve

POS integration:
├── Table management
├── Cover tracking
├── Revenue data
└── Guest history

Communication:
├── SMS confirmations
├── Email receipts
├── Reminder calls
├── Waitlist notifications
└── Review requests

Basic information:
├── Hours of operation (regular + special)
├── Address and directions
├── Parking information
├── Contact details
└── Reservation policies

Reservation rules:
├── Maximum party size
├── Minimum booking notice
├── Cancellation policy
├── Deposit requirements
├── Peak time restrictions
└── Event/holiday handling

Capacity settings:
├── Total covers available
├── Table configurations (2-top, 4-top, etc.)
├── Turn times by meal period
├── Buffer between seatings
└── Overflow handling

Time slot rules:
├── Available booking windows
├── Blocked times (private events)
├── Last seating times
├── Early bird incentives
└── Peak pricing (if applicable)

Required:
├── Phone system (SIP/VoIP)
├── Reservation system API
├── SMS gateway
└── Calendar sync

Optional:
├── POS integration
├── CRM system
├── Marketing platform
└── Review management

Reservation tests:
□ Standard booking flow
□ Fully booked handling
□ Modification requests
□ Cancellation processing
□ Large party handling
□ Special requests

Edge cases:
□ Invalid date/time requests
□ Past date attempts
□ Capacity exceeded
□ System unavailable
□ Caller wants human

Monthly benefit = (automated calls x minutes saved x cost/minute)
                + (recovered calls x conversion rate x avg order value)
                - monthly fee
Payback = setup fee / monthly benefit

Good restaurant voice:
├── Warm and welcoming
├── Efficient but not rushed
├── Knowledgeable about menu
├── Appropriately formal/casual (match brand)
└── Helpful with suggestions

Avoid:
├── Overly robotic responses
├── Too many menu options at once
├── Complicated booking process
├── Ignoring special requests
└── No human escalation option

During busy periods:
├── Faster conversation flow
├── Priority to new bookings
├── Quick modifications/cancellations
├── Efficient party size handling
└── Clear availability communication

Waitlist management:
├── Automatic position updates
├── ETA communication
├── Quick callback when available
├── Fair queue management
└── No-show replacement

Good fit if:
□ Missing 10+ calls daily
□ Phone interrupts service
□ High reservation volume
□ Staff stressed with calls
□ Want 24/7 booking capability

Calculate opportunity:
(Daily missed calls) × (reservation rate) × 
(avg party size) × (avg spend) × 30 days
= Monthly revenue opportunity