Who this guide is for
If you run a tea room, tea house, or afternoon-tea venue and you're still managing bookings through a paper diary, a shared spreadsheet, or Instagram DMs, this guide is for you. It's also for owners who already use a generic restaurant reservation platform and wonder why it feels like it was designed for someone else's business.
We wrote it specifically for operators who serve set tea seatings, need to capture dietary information before guests arrive, and want to run ticketed or seasonal events without switching to a second tool.
Tea rooms vs restaurants: what's different operationally
A busy restaurant optimizes for table turns—seat a party, clear, reset, repeat. A tea room optimizes for timed seatings. Guests book the 11:00 AM, 1:30 PM, or 4:00 PM service. Food is prepped in bulk by seating, not à la carte. Dietary needs must be collected at booking time, not when the server arrives at the table.
This fundamental difference means a reservation system built for restaurants will force workarounds: blocking “fake tables” to simulate seatings, manually emailing guests about allergies, or keeping a side spreadsheet for add-ons like champagne upgrades. A tea-room-specific system handles all of this natively.
What a tea-room reservation system must do
Timed seatings and capacity rules
Your system should let you define discrete seating windows (for example, three seatings per day with a 90-minute duration each) and set a hard capacity cap per seating. When the 1:30 PM seating fills to 24 covers, the system should close that slot automatically and— ideally—offer the guest a waitlist or alternative time.
Look for a system where seatings and capacity are first-class concepts, not a workaround layered on top of rolling availability.
Floor plans and “no double booking” logic
Tea rooms often have multiple rooms (a main parlor, a garden room, a private dining space) with different table configurations. An interactive floor plan lets you assign parties to specific tables, merge tables for larger groups, and block rooms for private events— all while the system prevents the same table from being booked twice in the same seating window.
Guest profiles (dietary needs, allergies, special occasions)
A strong reservation system captures per-guest information at the booking step: allergies, dietary restrictions (gluten-free, vegan, halal), celebrations (birthdays, anniversaries), and any notes. This data should persist across visits so repeat guests don't have to re-enter it, and it should flow directly into a kitchen prep list the morning of each seating.
Add-ons and upgrades in the booking flow
Champagne, prosecco, birthday cake tiers, souvenir teacups—these add-ons are a meaningful revenue stream for tea rooms. The booking flow should present them as optional extras that guests can select and pay for before they arrive. This replaces the awkward “would you like to upgrade?” email chain.
Events: ticketed and seasonal teas
Mother's Day, Christmas, Valentine's Day, themed collaborations with local florists or chocolatiers—events are where many tea rooms earn their best margins. Your system should support creating event-specific ticket tiers with prepayment, separate capacities, and their own confirmation and reminder flows. See our full event workflow guide.
Decision framework
Not every tea room operates the same way. Use this framework to prioritize features based on your model.
If you run set seatings (e.g., 11:00 / 1:30 / 4:00)
Prioritize: timed-seating capacity management, automated reminders keyed to seating time, dietary data capture, and kitchen prep list exports. Add-ons in the booking flow are a bonus if you offer upgrade options.
If you run mixed walk-ins + reservations
Prioritize: real-time floor plan with live table status, a waitlist that works alongside booked tables, and SMS notifications so walk-in guests can browse nearby shops while they wait.
If you run frequent themed/ticketed teas
Prioritize: event creation with ticket tiers, full prepayment capture, refund/transfer policy enforcement, and day-of check-in tools. You essentially need event management layered on top of your daily reservation system.
Feature comparison table
Required vs nice-to-have vs enterprise
| Feature | Required | Nice-to-have | Enterprise |
|---|---|---|---|
| Timed seatings with capacity caps | ✓ | ||
| Interactive floor plan | ✓ | ||
| Dietary/allergy capture at booking | ✓ | ||
| Automated email + SMS reminders | ✓ | ||
| Deposits and card holds | ✓ | ||
| Website embed widget | ✓ | ||
| Add-ons and upgrades in booking | ✓ | ||
| Ticketed event management | ✓ | ||
| Guest profiles with visit history | ✓ | ||
| Waitlist with SMS callback | ✓ | ||
| Multi-location management | ✓ | ||
| POS integration | ✓ | ||
| API access | ✓ |
Pricing models to understand
Flat subscription vs per-cover vs payment fees
Reservation platforms typically charge in one of three ways:
- Flat monthly subscription: a predictable cost regardless of how many covers you book. Best for tea rooms with consistent volume.
- Per-cover fee: you pay a small amount per seated guest (often $0.50–$2.00). This scales with your business but can become expensive during peak seasons.
- Payment processing fees: if the system handles deposits or prepayment, expect a 2.5–3.5% + $0.30 charge per transaction. Some platforms bundle this; others pass it through.
For most small-to-medium tea rooms, a flat subscription with pass-through payment processing offers the most predictable economics.
Why “SMS as a separate fee” feels bad
Some platforms charge SMS reminders as an add-on (per message). This creates a perverse incentive: the feature that reduces your no-shows costs extra every time you use it. Look for a system that bundles reminders into the subscription, or at minimum offers email reminders at no extra cost with SMS as an optional upgrade.
Implementation checklist
Go live in a weekend: the minimum viable setup
You don't need weeks of configuration. Here's a realistic weekend plan:
- Saturday morning: Create your account, add your venue details (name, address, phone, hours), and configure your seating times and capacity.
- Saturday afternoon: Upload or build your floor plan. Add tables to each room and set party-size ranges.
- Saturday evening: Set up your booking policies (deposit amount, cancellation window, reminder schedule) and customize your confirmation email template.
- Sunday morning: Embed the booking widget on your website. Follow the step-by-step embed guide.
- Sunday afternoon: Make a test booking from your phone. Check the confirmation email, the reminder timing, and the floor plan assignment. Adjust anything that feels off.
- Monday: Go live. Share the booking link on your social channels and update your Google Business Profile.
Ready to see how it works?
Table Mouse was built specifically for tea rooms. Timed seatings, floor plans, deposits, guest profiles, and ticketed events—all in one system.