Give the role a reliable starting point.
Share booking rules, opening hours, party-size limits, and the person who approves exceptions.
Reservation inbox support
Reservation inbox support
Handle reservation correspondence using the availability and booking policies set by your restaurant.
Book a free consultationScope, access, and coverage are agreed with your team.
The day-to-day work
A clear queue. A useful handoff.
Define the recurring work and the evidence your team needs to review it. These building blocks become a role-specific operating plan.
- Record reservation requests
- Share available options
- Confirm authorized changes
- Keep booking notes current
What comes back to your team
Work you can see and review.
Reservation correspondence log
A working record with source references, current status, and the person responsible for the next step.
Change-request queue
A focused view of missing inputs, unanswered questions, and items that need your decision.
Confirmed booking notes
A dated handoff that distinguishes completed work from pending review and unresolved exceptions.
Put the role into practice
From the first brief to the final check.
A practical handoff
A guest requests a larger table than the online inventory offers. The assistant collects the details and asks the host manager what can be accommodated.
Illustrative workflow, not a client case study.Check the work before closing the loop.
Match each message to the right date, time, party, and current reservation status.
Your systems, your permissions
Fit the role to your environment.
Tool familiarity is considered when defining the role. Your team approves every platform, access level, and source of truth.
OpenTableResySevenRoomsEmail
Platform names describe possible working environments, not endorsements or a promise of certification.
Inside the responsibility
What reservation inbox support looks like in practice.
Handle reservation correspondence using the availability and booking policies set by your restaurant. The scope below connects each recurring responsibility to its source information and a checkable working record. Your team confirms the exact steps, templates, and approval limits before work starts.
Record reservation requests
Begin with the latest request and its approved source record. Check that the necessary information is present, identify the owner, and clarify conflicting details before making an update.
Working output: Reservation correspondence log. Include the source reference, current status, and next owner when an item remains open.
Share available options
Use the agreed template or checklist to carry out this task. Record what was checked and the date of the action so another team member can understand the current position.
Working output: Change-request queue. Include the source reference, current status, and next owner when an item remains open.
Confirm authorized changes
Keep this work connected to the wider queue. Note dependencies and unanswered questions, and use the agreed escalation route when the next step requires a decision.
Working output: Confirmed booking notes. Include the source reference, current status, and next owner when an item remains open.
Keep booking notes current
Complete the task only when its agreed checks have passed. If an input is missing or an approval is pending, keep that status visible rather than treating the item as finished.
Working output: Reservation correspondence log. Include the source reference, current status, and next owner when an item remains open.
A handoff you can act on
Keep ready work separate from unresolved work.
A guest requests a larger table than the online inventory offers. The assistant collects the details and asks the host manager what can be accommodated.
Ready for review
The agreed task is complete and the supporting information is available in your approved system. Attach or link the relevant record and identify any final reviewer before closing the item.
Review against: Match each message to the right date, time, party, and current reservation status.
Waiting on an input
Name the missing information, where it was requested, and who is expected to supply it. Keep a follow-up date visible. An unanswered request should not disappear into a completed-work total.
Starting requirements: Share booking rules, opening hours, party-size limits, and the person who approves exceptions.
Needs your decision
Summarize the exception and the information already checked. Ask a specific question and route it to the authorized person. Keep the original source intact while the decision is pending.
Approval boundary: Your restaurant controls table allocation, capacity, deposits, and policy exceptions.
Set the role up well
Agree what good work means before the first handoff.
Access and examples
Provide individual, approved access to the systems used for this responsibility. Share a completed example, an incomplete example, the relevant template, and a named reviewer. Sensitive working records belong in those systems, not in a public inquiry form.
Possible working environments include OpenTable, Resy, SevenRooms, Email. Tool access and familiarity are confirmed as part of the role brief.
Review and workload measures
Agree which measures are useful for this queue: completed items, items awaiting an input, age of unresolved work, and corrections requested by the reviewer. Review these together with actual examples; volume alone does not establish that work is accurate.
Set response expectations from your operating needs. Coverage, turnaround targets, and the amount of work assigned are agreed separately rather than assumed from the service name.
Before you start
A few useful questions.
What should we prepare for reservation inbox support?
Share booking rules, opening hours, party-size limits, and the person who approves exceptions.
How will we know what is complete?
Match each message to the right date, time, party, and current reservation status.
Which decisions remain with us?
Your restaurant controls table allocation, capacity, deposits, and policy exceptions.
Can the role work in our existing tools?
We scope the role around your approved systems, including environments such as OpenTable, Resy, SevenRooms. Access, training, and the final tool requirements are confirmed before the role begins.
Related support
Connect the work around this role.
Guest inquiry coordination
Guest inquiry coordination
Give routine guest questions clear answers and sensitive requests a direct route to the right manager.
Explore the service ↗
Private dining inquiries
Private dining inquiries
Organize event leads so your events manager can respond with the right offer and next step.
Explore the service ↗
Guest feedback administration
Guest feedback administration
Bring feedback from your approved channels into a clear queue for thoughtful management responses.
Explore the service ↗
Supplier correspondence
Supplier correspondence
Keep purchase-related messages and delivery questions visible to the people running the kitchen and office.
Explore the service ↗A role shaped around your operationStart with the work
Start with the work
you want to hand over.
Tell us where the queue slows down. We’ll discuss the scope, tools, coverage, and review points that belong in your support role.
Book a free consultation
Define the role before making a commitment.