Overview
This engine is a straight-line reservation graph on the canvas. It starts with Customer Name (TEXT), then Email Address (EMAIL), Party Size (NUMBER), Phone Number (TEXT), Preferred Time (SELECT), Reservation Date (DATE), and Special Requests (TEXTAREA). Each hop is tied with visibility so the next field appears when the graph allows it. The flow ends at Form Complete (END).
How it works
- Customer Name collects text identity; visibility controls when Email Address appears.
- Party Size (NUMBER) and Phone Number (TEXT) follow in sequence under the same visibility pattern.
- Preferred Time uses a SELECT; Reservation Date is a DATE node; Special Requests is a TEXTAREA for free-form notes.
- Form Complete is the END node—submission finishes the runner’s path through this chain.
Key Features
- Field types match the builder: TEXT, EMAIL, NUMBER, SELECT, DATE, TEXTAREA, END.
- Visibility labels on edges document progressive disclosure between steps.
- Single primary path—easy to read in demos and easy to extend with branches later if you add them.
- Terminal Form Complete node makes the successful outcome explicit in the graph.
Use Cases
- Restaurants standardizing the same questions every host asks on the phone.
- Catering or events teams capturing party size, time, date, and notes in one flow.
- Product teams cloning the template and swapping labels without rewriting marketing copy from scratch.