TL;DR
To build a booking app with Claude, describe what is booked, how long it takes, and your hours. Claude builds a public page to pick a slot and a team schedule behind sign-in. Postgres guarantees no double bookings, and a scheduled job sends reminders. On floo, two routes in floo.app.toml make one page public and the other invite-only.
- Public booking at
/, team schedule at/adminbehind sign-in. - The database, not the page, prevents double bookings.
- Reminder emails run as a cron job with your email provider's key.
Booking tools are a common first app because the rules are clear and the cost of the off-the-shelf version adds up: equipment, rooms, consultations, classes, site visits. The part to get right is the one customers never see: two people must never get the same slot.
1. Describe the booking
Build a booking app. Customers book a 45-minute site visit. We have two inspectors; a customer picks a time and we assign whoever is free. We work 8am to 5pm New York time, Monday to Friday. The public page shows open slots for the next 14 days and asks for name, email, address, and notes. After booking, the customer gets a confirmation email. The team page at /admin shows the week by inspector and lets us move or cancel a visit. Put every team API route under /admin/api, never under /api. Send a reminder email 24 hours before each visit. Use a Postgres constraint so the same inspector can never be booked twice for overlapping times.
2. Host it
[app]
name = "site-visits"
access_mode = "public"
[services.web]
type = "web"
path = "."
port = 3000
ingress = "public"
[[routes]]
path = "/"
service = "web"
access = "public"
[[routes]]
path = "/admin"
service = "web"
access = "accounts"
[managed.default]
type = "postgres"
[cron.reminders]
schedule = "*/15 * * * *"
command = "node scripts/send-reminders.js"
service = "web"
- Two routes, two rules. Anyone can open
/. Only people you invite can open/admin, and those requests carryX-Floo-User-Email. Everything outside/adminis public, so the team's move and cancel endpoints must live under/admintoo, such as/admin/api/visits. - The reminder job runs every 15 minutes and sends reminders for visits starting 24 hours from now that haven't had one. Recording "reminder sent" on the visit keeps it from sending twice.
- Email key:
floo env set EMAIL_API_KEY --stdin --app site-visits.
3. Test the hard cases
Ask Claude to write tests for the cases that break booking apps:
- Two bookings for the same inspector and time at once: one succeeds, one fails cleanly.
- A booking across the switch to or from daylight saving time shows the right local time.
- A cancelled visit frees its slot.
Store times in UTC in Postgres and convert to New York time only for display.
Before you share the link
- Spam protection on the public form. A rate limit or a simple challenge.
- A custom domain.
book.yourcompany.comreads better in an email. See custom domains. - A calendar file in the confirmation. An
.icsattachment lets customers add the visit in one click.
For the scheduled part in more detail, see how to run a daily job in an app Claude built.
Frequently asked questions
Can Claude build a booking or appointment app?
Yes. Describe what people book, how long it takes, when you are open, and what happens after someone books. Claude builds the public booking page, the team schedule, and the reminders. On floo the public page and the team page live in one app, each with its own access rule.
How do I stop two people booking the same slot?
Enforce it in the database, not only in the page. Ask Claude for a unique constraint on the resource and start time, or an exclusion constraint on the time range in Postgres. A second booking for the same slot then fails even if two people click at the same second.
How do I make the booking page public but the schedule private?
Declare two routes in floo.app.toml: "/" with access = "public" for the booking page and "/admin" with access = "accounts" for the team. floo's gateway asks for sign-in only on /admin.