Product tour
One operating system
for the booking desk.
A dense look at what Lobby actually does: schedule, members, classes, Stripe payments, reporting, white-label booking, and migration/import.
Court 01
Padel · indoor
Court 02
Padel · indoor
Court 03
Padel · outdoor
Court 04
Padel · outdoor
Court 05
Singles
Open play
Beginner social
17:00 — 18:30 · 4/4
Reservation
F. Langworth +3
Lesson
Coach Madison
20:00 — 21:00
Block
Maintenance
League match
Marchand vs Veiga
17:30 — 20:00 · Ladder R3
Free · €30/h
Reservation
A. Iliescu +1
17:00 — 19:00
Holding · 90s
New booking
Reservation
Open play
Intermediate
18:30 — 20:00 · 3/4
Free
Clinic
Net positioning
17:30 — 20:00 · 6/8
Reservation
N. Hein
01 · Schedule
A calendar that rejects conflicts.
Court holds, recurring bookings, blocks, classes, and payment state live in the same grid. The booking is not confirmed until the write path and payment path agree.
Class roster
Net positioning · Coach Madison
Upcoming cohort · weekly
02 · Memberships and classes
Access rules beside attendance.
Membership status, class capacity, waitlists, recurring cohorts, and member notes stay close to the booking desk. Staff do not need a spreadsheet to decide who can book.
Recent payments
Next payout
€2 184.00
Mon 19 May
Processor fees
Stripe
Set by Stripe · Lobby never touches them
Lobby cut
€0.00
No booking percentage. Ever.
03 · Stripe payments
Card state where the booking lives.
Members pay the club through Stripe in Stripe-supported markets. Lobby shows payment links, paid state, refunds, and reconciliation without taking a booking percentage.
Illustrative occupancy
Sample
Example report cell
Illustrative revenue
Sample
Example report cell
Illustrative attendance
Sample
Example report cell
04 · Reporting
Operational reports, not vanity charts.
Reports focus on occupancy, revenue by surface, payment status, member activity, and CSV export. The page is designed for operators and accountants.
Import preview
Demo Club · dry run
| Source field | Target field | Rows | Status |
|---|---|---|---|
| Playtomic.members | lobby.users | 1 842 | ✓ ok |
| Playtomic.bookings | lobby.bookings | 18 204 / 24 mo | ✓ ok |
| Playtomic.memberships | lobby.clients | 412 | ✓ ok |
| Playtomic.coupons | lobby.coupons | 38 | ✓ ok |
| Stripe.customer_ids | preserved | 1 842 | ✓ ok |
| Stripe.past_payouts | reference-only | — | read-only |
05 · Migration and import
Dry-run imports before cutover.
Lobby imports members, courts, bookings, classes, and reference payment data from CSV. Every import gets a staging preview before a public launch.
Sport configurations
Same product,
different rules.
The product surfaces above are configured differently for courts, lanes, studios, packages, waitlists, and open-play sessions.
Implementation notes
Read the
operator playbooks.
The first content pieces explain the product surfaces that matter before a pilot has publishable customer outcomes: migration/import and Stripe reconciliation.
06 · White-label
The booking flow
looks like the club.
Lobby is not a player marketplace. The member-facing surface can sit on the club URL and carry the club brand, while the operator surface stays consistent for staff.
- OKClub-owned URL for member booking
- OKTenant colors and logo in the booking flow
- OKTransactional emails routed through the club workflow
- OKNo marketplace listing or player acquisition claim
White-label setup
book.club.example
Member booking preview
club.example/book
book.club.example
Choose a court
Court 01
18:00 to 19:30
Court 02
18:00 to 19:30
Class pass
Membership required
See it with your workflow