An example prompt for a booking system

Build a booking system for a dog-grooming salon with three groomers. It needs: services, resources and staff, availability rules and exceptions, double-booking prevention, booking flow with slot holds, time-zone handling and reminders and notifications. Rule that must always hold: store each booking as a half-open tstzrange including buffers and enforce EXCLUDE USING gist (resource_id WITH =, during WITH &&) over held and confirmed rows; the app inserts and handles the violation. Leave out for now: no check-then-insert booking logic: the exclusion constraint is the only overlap guard and no two-way Google/Outlook calendar sync, waitlist automation or dynamic pricing in phase 1.

Replace the first sentence with your own idea. The list of needs stays useful whatever the niche, because it comes from what a booking system has to do.

• Build a class booking app for a climbing gym. Start with services, resources and staff and availability rules and exceptions, and add double-booking prevention once those work.
• Build a consultation scheduler for a physiotherapy clinic. People should be able to reserve a slot while the customer fills in details or pays, then confirm or release it.

Forge AI picks a reference architecture from how you describe the app. These phrases point to a booking system: booking system, appointment booking, appointment scheduling, scheduling app, calendly, acuity, book appointments and online booking.

• Database exclusion constraint on tstzrange to prevent double booking.
• UTC instants plus IANA zones, availability rules in local business time.
• Short slot holds that participate in the exclusion constraint.
• Reminders as time-indexed rows claimed by a worker.

This is a reference design for the category, not a promise that every item is generated today. Built-ins such as email, background jobs, file uploads and search are coming soon, so anything here that needs them is something you add yourself for now.

• Two-way Google/Outlook calendar sync: needs OAuth app review and per-provider rate-limit handling.
• SMS provider integration at scale: email reminders cover phase 1 and SMS adds per-message cost.
• Waitlist and auto-fill of cancelled slots: adds offer expiry and fairness rules.
• Read replicas for availability and calendar reads: primary handles phase-1 load.

How detailed should a prompt for a booking system be?

Name the users, the main objects, one rule that must always hold and one thing to leave out. The plan fills in the rest, and you can change it before generation.

Which words tell Forge64 this is a booking system?

Phrases such as booking system, appointment booking, appointment scheduling and scheduling app point to this category.

Can I change the app after the first build?

Yes. Describe the change in plain English and Forge AI edits the app; the quality gate checks the code again.

• How to build a booking system
• Booking system architecture
• Booking system security checklist
• Booking system scaling checklist
• Often combined: SaaS dashboard
• Often combined: marketplace
• All app types