1. Reservations, reminders and post-visit feedback
Bookings come by call and DM; reminders and feedback rarely happen.
Trigger: WhatsApp / Call (booking request)
How the workflow runs
- Trigger
Guest requests a table. A WhatsApp or Call trigger captures the request.
- Agent
Confirm the booking. An Agent node checks availability and confirms details.
- Tool (MCP)
Write to the booking system. A Tool (MCP) node records the reservation.
- Output
Reminder + feedback. An Output node sends a day-of reminder, then a feedback ask after the visit.
Channels & connectors
- Voice / Call
- Tool (MCP → bookings)
Outcome
Bookings are confirmed and logged, reminders cut no-shows, and feedback arrives without staff chasing it.
Why it helps
Closes the loop from booking to feedback with zero manual follow-up.
Build spec
1 agent — 1 reservations agent; the booking write, reminder and feedback are workflow nodes.
System prompt (paste-ready)
You are a reservations assistant for {{venue}}. From a WhatsApp or voice request, capture party size, date, time and any special requests, check availability, and confirm the booking in the guest's language. Only confirm a slot the availability check actually returned — never promise a table you haven't verified. After the visit, send a short feedback request. Be concise and gracious.MCP connectors
- Booking/table-management system — via a Tool (MCP) node
- WhatsApp / Voice — request + confirmation channel
Built-in tools
- http_request (availability check)
Guardrails
- Only verified-available slots are confirmed — no double-booking or unverified promises
- The reservation is written by the Tool node and keyed to the booking id — idempotent on retries
- Reminder and feedback are each sent once, on the guest's channel
Output & delivery
The agent confirms the booking, a Tool node records it in the booking system, and Output nodes send a day-of reminder and a post-visit feedback request automatically.
