Guest inbox sorting and reply drafts
An agent sorts the restaurant's shared inbox into reservations, lost items, gift cards, complaints, job inquiries, and vendor pitches, then drafts replies for routine messages and routes the rest.
The use case
A restaurant's general inbox collects everything: reservation changes, lost sunglasses, gift card balance questions, complaints, job applications, and sales pitches. When nobody owns it, guests wait days for simple answers and complaints go unseen. This agent reads each message, sorts it into a category, and drafts a reply for routine questions using the restaurant's FAQ, such as hours, parking, corkage, or how to change a booking. Complaints, health or allergy concerns, and anything about staff are routed to the manager with no draft. Job inquiries go to whoever handles hiring, and vendor pitches are filed. A staff member reviews each draft and sends it. The agent does not change reservations, issue gift card credit, or make offers to guests.
Example workflow
- New messages to the shared inbox are passed to the agent as they arrive.
- The agent sorts each message into reservations, lost and found, gift cards, complaints, private events, job inquiries, vendor pitches, or other.
- Complaints and messages about health, allergies, or staff conduct are routed to the manager with no draft.
- For routine categories, it drafts a short reply using the restaurant's FAQ document.
- A staff member reviews, edits, and sends drafts, and makes any reservation change in the booking system.
- Job inquiries and event leads are forwarded to their owners, and counts by category are logged weekly.
Tools
- Gmail
- Google Docs
- OpenTable or Resy
- Slack
- Claude
- Zapier or Make
Risks and guardrails
- A complaint about illness could be treated as routine — guardrail: health and allergy terms send the message to the manager immediately with no draft.
- A reply could give wrong hours or policies — guardrail: drafts use one FAQ document that the manager keeps current.
- The agent could promise a reservation or refund — guardrail: it cannot change bookings or payments, and drafts never make offers.
- Job applicant messages could be handled inconsistently — guardrail: all job inquiries are forwarded unchanged to the hiring owner without replies or judgments.
Related recipe
Support Ticket and Review Triage with Policy-Cited Draft Replies: An agent tags every helpdesk ticket and public review by intent, urgency, and sentiment, routes it, and drafts a reply that cites your help center. People approve refunds and all public replies.
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:
- Gmail (official page): developers.google.com/workspace/gmail (checked 2026-11-19)
- Resy (official page): www.americanexpress.com/content/dam/amex/en-us/credit-cards/benefits/resy/resy_mcp_app_claude.pdf (checked 2026-11-19)
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)
- 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)