Restaurants & cafes
Handle reservations and private-event requests
Guest requests usually slows down when reservation notes, event forms, guest emails, capacity rules, menus, and calendars do not tell the same story, or when a guest asks about a reservation, private event, or special accommodation. Imagine keeps those sources in view, prepares a guest summary, availability recommendation, and response draft, and separates the ready work from the judgment calls. After review, the approved update goes back to the reservation system and guest thread, so guests get fast answers without managers living in the inbox.
The manual reality today
-
01
The guest requests handoff starts cold
reservation notes, event forms, guest emails, capacity rules, menus, and calendars each hold part of the answer, so the team burns time piecing together what happened before they can respond.
-
02
Small guest requests delays become customer-facing
When a guest asks about a reservation, private event, or special accommodation, the next step can sit until someone checks the right queue, thread, portal, or spreadsheet.
-
03
Guest requests decisions are hard to retrace
Approvals, notes, and updates end up in side channels, making it hard to tell what was sent, what changed, and who signed off.
How Imagine handles it
-
01
Collect live guest requests context
Imagine watches reservation notes, event forms, guest emails, capacity rules, menus, and calendars for new activity, stale items, and changes that affect the work.
-
02
Group the facts for guest requests
Messages, records, dates, and prior decisions are grouped so the next step starts with the facts already attached.
-
03
Prepare the guest requests response
Imagine drafts a guest summary, availability recommendation, and response draft using your rules, tone, and thresholds, then flags anything that needs judgment.
-
04
Close the loop on guest requests
After review, approved actions are recorded in the reservation system and guest thread with the context, approver, and timestamp preserved.
Works with the tools you already run
- OpenTable
- Resy
- Toast
- Square
- Google Calendar
- Gmail
What changes
The guest requests queue starts warm
Prep work and status checks run continuously, so the team sees the few items that actually need a decision.
Guest requests follow-up feels consistent
Each next step follows the same rules and cadence, so customers, clients, candidates, and vendors get a reliable experience.
Managers can trust the guest requests trail
Source context, approver, and destination update stay together, so the workflow is easier to audit or explain.
Frequently asked questions
How does Imagine handle guest requests?
Imagine watches reservation notes, event forms, guest emails, capacity rules, menus, and calendars, spots when a guest asks about a reservation, private event, or special accommodation, and prepares a guest summary, availability recommendation, and response draft for review. Approved actions sync back to the reservation system and guest thread with the supporting context attached.
When does guest requests need a person?
You decide what can move automatically and what needs review. Anything outside your rules is routed to the responsible person before the reservation system and guest thread is updated.
Can this use our current guest requests systems?
This workflow can connect to systems such as OpenTable, Resy, Toast, Square, Google Calendar, Gmail. Imagine works on top of those tools instead of replacing the system of record.
How does the guest requests queue change the day?
The team stops rebuilding status by hand. They open a queue that shows what changed, what is ready, and what still needs approval so guests get fast answers without managers living in the inbox.