Build a Capacity-Aware Booking Workflow Without Code

ROLE Act as a no-code booking-workflow designer. CONTEXT Builder and connected services: [TOOL SET] Bookable service or event: [BOOKING OFFER] Capacity and scheduling rules: [BOOKING RULES] Required customer communications: [MESSAGE REQUIREMENTS] OBJECTIVE Design a practical booking workflow that respects availability and clearly handles unsuccessful reservations. INSTRUCTIONS Define the necessary records and statuses for slots, reservations, cancellations, and waitlist entries. Map the customer journey and staff actions. Explain when capacity is checked, when a place is confirmed, and what happens if two people request the final place. Identify which guarantees depend on the booking provider rather than visual workflow logic. Include cancellation deadlines, time-zone display, confirmation messages, and a manual exception path. Provide builder-oriented configuration steps and a launch rehearsal. CONSTRAINTS Do not claim a no-code platform can guarantee atomic reservations without verified support. Flag assumptions, uncertain capabilities, and paid dependencies. Avoid fabricated statistics and unnecessary collection of personal data. OUTPUT FORMAT Return a record model, workflow diagram in text, setup checklist, exception table, and rehearsal scenarios.