Custom domain
Players book on your domain, not ours.
The booking site, the emails, and the payment receipt carry the club’s name. Lobby stays behind the counter, so the player relationship is yours to keep.
White-label setup
book.club.example
Member booking preview
club.example/book
Illustrative domain setup: DNS check, certificate, and brand preview for a club site.
The problem
When players book through a vendor’s app or subdomain, the vendor owns the habit. The club gets the court fee, and the vendor gets the relationship, the email list, and the next booking.
- 01
Players search the vendor’s app first, where competitors are one tap away.
- 02
Confirmation emails arrive from a brand the player never chose.
- 03
Leaving the vendor means leaving the URL players have saved.
How it works
In the order it happens.
What the club decides
Your rules, written once.
Questions
The plain answers.
Do we need a developer to set this up?
No. You add one DNS record at your domain provider. Lobby checks it, issues the certificate, and shows the status until the domain is live.
Is Lobby visible to players anywhere?
Not in the booking path. The site, emails, and receipts carry the club brand. Stripe appears on the card statement as the payment processor.
What if we already have a website?
Keep it. Most clubs put the booking site on a subdomain such as book.yourclub.com and link to it from the existing site.
Works with
Connected to the rest of the club.
Custom domain in your club
Bring the real workflow.
Test the real week.
Set it up in a free preview workspace with your own courts, prices, and rules. Nothing is published until you say so.