Reserve multiple spots PRD

Overview

This feature allows a single client to reserve multiple spots in a group booking using one email address. Currently, our system prevents the same email from booking the same meeting multiple times. This enhancement addresses use cases where parents want to book sessions for multiple children or teams need to reserve multiple spots under one contact.

Feature Summary

  • Host Configuration: A checkbox setting to enable multi-spot bookings per group meeting

  • Dynamic Form Question: System-generated dropdown asking "How many spots would you like to book?"

  • Spot Tracking: Display actual attendee count vs. client count in host dashboard

  • Payment Integration: Automatic price calculation based on spot quantity

  • Email Updates: Modified notification templates to reflect multi-spot bookings

User Flow (Brief)

  1. Host enables "Allow one client to book multiple spots" checkbox in group booking settings

  2. System automatically adds "How many spots would you like to book?" question to booking form

  3. Client selects desired number of spots from dropdown (1 to available spots)

  4. Payment amount updates dynamically (spots × price = total)

  5. Host sees booking with spot count: "user1 - 3 spots" instead of separate entries


Edge Cases & Error Scenarios

1. Concurrent Booking Race Conditions

Scenario: Two users booking simultaneously causing overselling

  • User A selects 5 spots while 8 are available

  • User B books 4 spots before User A submits

  • User A's submission would cause overbooking (5 spots + 4 spots = 9, but only 4 remain)

Required Handling: Server-side validation with real-time availability check on submission

2. Mid-Booking Availability Changes

Scenario: Available spots change while user is filling form

  • User opens form with 8 spots available

  • Another user books 6 spots

  • Original user's dropdown still shows 1-8 options

  • User selects 5 spots but only 2 are actually available

Required Handling: Real-time availability updates or validation on form submission

3. Recurring Meeting Complications (we are currently not doing this for regular group bookings)

Scenario: Multi-spot booking for recurring meetings

  • User books 3 spots for a recurring weekly meeting but on the 2nd week the number of spots are less than 3.

4. Cancellation & Rescheduling complications

Scenario: Partial cancellation of multi-spot booking

  • User books 5 spots, wants to cancel only 2

  • Current system doesn't handle partial cancellations

  • Refund calculation becomes complex

Required Handling: Define cancellation policy (recommend: all-or-nothing for MVP, partial cancellation for future iteration)


Settings & Feature Dependencies

  1. Payments

  2. Host email

  3. Analytics