How to Run Ticketed Afternoon Tea Events (No Spreadsheets Needed)

What counts as a “ticketed tea event”

Themed teas, seasonal teas, collaborations, charity teas

Any afternoon tea with a fixed date, a distinct menu, a capacity limit, and upfront payment is a ticketed event. Common examples:

• Seasonal teas: Mother's Day, Valentine's Day, Christmas, Easter, Halloween.
• Themed teas: Bridgerton tea, garden-party tea, children's fairy tea.
• Collaboration teas: joint events with local florists, chocolatiers, authors, or jewelers.
• Charity teas: fundraiser seatings where a portion of ticket revenue goes to a cause.

The common thread: guests commit and pay before they arrive, so you know exactly how many covers to prep, what revenue to expect, and who has dietary restrictions.

The spreadsheet failure modes

Overselling seats, payment mismatches, dietary notes getting lost

If you're managing ticketed events through a shared spreadsheet, Instagram DMs, or a Google Form linked to manual bank transfers, you've probably encountered these failure modes:

• Oversold seatings: two staff members accept bookings at the same time and the spreadsheet isn't updated fast enough.
• Payment reconciliation: bank transfers arrive without reference numbers, and matching payments to bookings takes hours.
• Lost dietary notes: a guest mentions a nut allergy in a DM that gets buried under 40 other messages.
• No automated reminders: you manually email or text every guest the day before, or worse, you don't.
• No waitlist: when someone cancels, there's no automated way to offer the seat to the next person.

A dedicated ticketing workflow eliminates every one of these problems.

The modern workflow (end to end)

Build an event landing page with time slots and capacity

Create a landing page for each event with: the event name, date(s), a description, photos or mood boards, and the available seating times with remaining capacity displayed in real time. When a seating fills, it closes automatically and guests are offered a waitlist spot.

Configure ticket types (standard / premium / kids)

Offer two to three tiers that reflect real differences in the experience:

• Standard: the core afternoon tea service.
• Premium: adds champagne, a specialty tea flight, or a take-home gift.
• Kids: a smaller portion at a lower price, often with a themed activity.

Each tier has its own price and count toward the same seating capacity. The system should show remaining availability per seating, not per tier.

Add-ons (champagne, souvenir cup, birthday cake)

Present optional add-ons during checkout: a glass of prosecco, a birthday cake slice, a souvenir teacup, a bouquet from your collaboration partner. Add-ons increase average order value and let guests customize the experience.

Payment capture and refund rules

Capture full payment at the point of purchase. Set clear refund rules in your system:

• Full refund if cancelled 72+ hours before the event.
• 50% refund if cancelled 24–72 hours before.
• No refund within 24 hours (transfers still allowed).

Display these terms on the event page and in the confirmation email so there are no surprises.

Confirmations + reminder schedule

Even though guests have paid, reminders are still valuable. Send a confirmation immediately after purchase, a reminder 48 hours before with parking/directions, and a short “See you tomorrow!” text the evening before. This reduces confusion, especially for guests who booked weeks ago.

Day-of check-in (QR / list)

The simplest approach: a digital guest list on a tablet, sorted by seating time. As guests arrive, staff check them off. For larger events (50+ guests), add a QR code to the confirmation email that staff scan at the door for faster processing.

Ticket structure templates for tea rooms

2-seating vs 3-seating models

Choose your seating model based on your kitchen capacity and the event's expected demand:

Per-seat vs per-table ticketing

Per-seat is the default for afternoon tea: each guest purchases their own ticket and selects their own tier and add-ons.

Per-table works for private-room buyouts or small-group experiences where one person books and pays for the whole table. Use this for VIP packages or corporate team teas.

Policies you can copy

Refund window, transfer policy, dietary cutoff dates

Refund policy: Full refund for cancellations made 72+ hours before the event. 50% refund for cancellations 24–72 hours before. No refund within 24 hours. Bookings may be transferred to another person or date at no charge.

Dietary cutoff: Please submit dietary requirements at least 48 hours before your event. Changes made after this deadline may not be accommodated as our kitchen begins preparation in advance.

Transfer policy: Can't make it? You may transfer your ticket to another person at any time by updating the guest name in your booking confirmation, or contact us and we'll handle it.

Post-event ops

Export guest list, tag VIPs, follow-up offer

After the event, your system should let you:

1. Export the guest list with dietary notes, ticket tier, and add-on purchases for your records and future planning.
2. Tag high-value guests (multi-ticket purchasers, premium-tier buyers, repeat attendees) as VIPs for early access to future events.
3. Send a follow-up 24–48 hours after: thank guests, share photos, and offer early-bird access or a discount to your next event.

This turns a one-time event into a recurring revenue engine.