Reservation no-show and late cancellation follow-up
After each service, an agent lists no-shows and late cancellations from the reservation system, drafts a friendly follow-up for each guest, and notes repeat cases for the manager to decide on.
The use case
No-shows cost restaurants a full table during a busy service, but following up after a long shift rarely happens. When it does, the tone can be inconsistent, and decisions about deposits or booking limits are made on the spot. This agent reads the night's reservations from OpenTable, Resy, or SevenRooms after close, lists no-shows and late cancellations, and drafts a short, friendly message inviting the guest to rebook and reminding them of the cancellation policy. It notes guests with several no-shows in a set period so the manager can decide whether to ask for a card hold next time. It does not charge cancellation fees, block guests, or change account settings. The manager reviews the list the next morning, approves or edits messages, and makes any policy decision.
Example workflow
- After the last seating, the agent pulls the day's reservations with status, party size, and guest notes from the reservation system.
- It lists no-shows and cancellations made inside the policy window, skipping any marked with a staff note such as an emergency or a known regular.
- For each one, it drafts a short message inviting the guest to rebook and restating the cancellation policy in plain terms.
- It marks guests with repeat no-shows in the set period and lists their history for the manager.
- The manager reviews the list the next morning, edits or skips drafts, and sends approved messages from the reservation system.
- Any decision on card holds or fees is made and recorded by the manager, and the agent logs only which messages were sent.
Tools
- OpenTable or Resy
- SevenRooms
- Gmail
- Google Sheets
- Claude
- Zapier or Make
Risks and guardrails
- A message could reach a guest who had a real emergency or already called — guardrail: staff notes skip the guest, and the manager reviews every message before it is sent.
- The agent could appear to charge or penalize guests — guardrail: it has no access to payments or account settings, and drafts never mention fees unless the manager adds them.
- Policy wording in drafts could differ from what the booking page says — guardrail: the agent quotes the policy from one maintained document.
- Guest contact details could be copied into other tools — guardrail: messages are sent from the reservation system, and logs keep reservation IDs only.
Related recipe
B2B Invoice AR Reminder Agent with Approval Gate: An agent reads open invoices from QuickBooks or Xero, skips blocked accounts, and drafts tiered payment reminders in Gmail that a person approves one by one before anything is sent.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Resy (official page): www.americanexpress.com/content/dam/amex/en-us/credit-cards/benefits/resy/resy_mcp_app_claude.pdf (checked 2026-11-19)
- Gmail (official page): developers.google.com/workspace/gmail (checked 2026-11-19)
- Claude (official page): claude.ai (checked 2026-11-09)
- Zapier MCP (official page): zapier.com/mcp (checked 2026-11-09)
- Make MCP server (official page): developers.make.com/mcp-server (checked 2026-11-09)