Run your book without the paper book. Describe your covers, your services, and your table plan, and Taskade Genesis builds a reservation app that takes requests, shows the night at a glance, confirms each party, and keeps the notes that make a regular feel remembered.
The Seating Chart Planner is a live Taskade Genesis app on this page. Move a party around the plan, see how a real seating record behaves, then press "Use this app" to clone it in about ten seconds and turn it into the reservation book described here.
A restaurant book is a scheduling problem with a hard physical constraint: seats, turns, and a kitchen that can only send so many covers at once. This build stays honest about that. It does not pretend to compute optimal seating. It gives you a clear picture of the requests, the confirmed parties, and the load per service, and it leaves the seating judgement to the person who knows the room.
What the build gives you: a request per party with date, service, party size, contact, and notes such as allergies, high chairs, or an anniversary. Plus a confirm step, a running cover count per service so you can see when you are near capacity, deposit handling for large parties, and a guest history so a returning table arrives with its preferences attached.
The same reservations render across the layouts you need:
- Calendar view for tonight and the week ahead, service by service
- Table view for the run sheet with party size, time, table, and notes columns
- Board view to group parties by service or by seating area
- Plus List, Mind Map, Gantt, and Org Chart across the rest of the 7 project views
Automations handle the desk work. The Form Submitted trigger captures a request, a filter flags parties above your large-group threshold for a deposit via the Stripe Checkout Session action, and a scheduled trigger sends the day-before confirmation text to every party. Across 100+ bidirectional integrations, forms and Gmail pull requests in while SMS, email, and Slack push confirmations and the nightly run sheet out. Automations run on paid plans; the Free plan includes 10 flow runs in total.
The AI agents in the app carry 34 built-in tools including persistent memory and file analysis. The Reservations agent drafts replies to unusual requests, summarizes tonight's notes into a single pre-service briefing, and flags the parties that need a call rather than a text.
Two habits make this build pay for itself quickly. The first is capturing walk-ins as records alongside reservations, because a cover count that only knows about bookings is a cover count that lies to you every Friday. The second is writing one line of note after any table that went unusually well or unusually badly. Thirty of those lines is a better guide to your service than any survey, and it is already attached to the guest who will book again.
Clone the app, invite your floor team, and the guest data is yours. No commission per cover and no platform sitting between you and your regulars.
Learn the calendar layout in Learn, recurring runs in Learn, and deposits in Learn. Browse live builds in the Community Gallery. Pair this with the no-show reminder cadence, which matters more in hospitality than almost anywhere else, and the waitlist backfill app for a fully booked Saturday.
Frequently Asked Questions
Does it assign tables automatically?
No, and that is a deliberate choice. Table assignment depends on turn times, the shape of the room, and who is on the floor tonight. The app shows you party sizes and load per service so the decision is easy, and the seating call stays with your host.
How does it stop us overbooking a service?
A cover count per service against a capacity you set. When the count approaches capacity the app flags it, and new requests for that service can be diverted to a waitlist or offered an earlier or later sitting instead.
Can we take deposits for large parties?
Yes. Set a party-size threshold and the automation sends a hosted Stripe Checkout link with the confirmation for anything above it. Large-group no-shows are the most expensive kind, and a deposit removes most of them.
Where do guest notes live?
On the guest record, which persists across visits. Allergies, favourite table, anniversary dates, and the fact that they always want the bill split. A returning party arrives with all of it visible.
Can the whole floor team use it?
Yes. Invite them to the workspace and everyone sees the same live book. Roles run from Owner through Viewer, so a host can confirm and edit tonight without touching settings or history.
Does it print or send a run sheet?
A scheduled automation can email or Slack the day's Table view to the team before service, which is usually more useful than printing. The Table view itself is the run sheet.
What about walk-ins?
Add them as records on the night. Counting walk-ins alongside reservations is the only way to know your real cover load, and after a few weeks the pattern tells you how many seats to hold back.
Can we take reservations from our own website?
Yes. Embed or link the request form from your site, and publish it on your own domain with app sign-in on Business plans and above if you want returning guests to see their booking history.
