Branch-aware restaurant enquiries and permitted reservation changes, with managers retaining food safety, deposit, compensation, and serious complaint decisions.
A guest asks about a reservation, change or visit at a specific branch.
AI agents
Workflow steps
4 operating rules · 4 decision rules · 4 channels · records to verify
A reservation request or manager-owned case, with deposits, event terms, food safety and recovery decisions retained by staff.
Keep reservation enquiries, changes and guest notes together so staff can follow the next step without asking guests to start again. Voxistry coordinates AI workers using approved branch information and permitted booking actions. Managers keep responsibility for allergies, food safety, accessibility and commercial exceptions.
A fictional guest asks to move a reservation for six from 19:00 to 19:30 at a named branch. Identity and access to the booking are checked before the current branch availability is read.
The worker confirms the guest may access the reservation, then reads the current availability returned by the configured branch pathway. A failed or uncertain check goes to staff without disclosing booking details.
In this fictional scenario, the booking system reports that the authorized change request was saved. The revised reservation is still awaiting confirmation. The worker does not tell the guest that the new time is confirmed or that an update message has been delivered.
If the result is uncertain, the worker checks the existing booking before trying again. The named restaurant manager owns pending follow-up and any branch or commercial exception.
Agree the outcomes with your restaurant team and compare them with your current process.
Example division of work between AI workers and your team.
Answers approved branch, menu, access, and reservation questions with the current guest context.
Checks the configured availability pathway and records permitted bookings or modifications.
Records concern details and prepares the guest’s notes and history for manager review.
Owns food-safety, accessibility, event, deposit, compensation and serious complaint decisions.
Use this sequence to agree the workflow and test each step before launch.
Which branch and reservation context are verified, and may this guest access or request a change to the booking?
What live availability and permitted options can be offered through the configured pathway?
Is this booking or modification inside the configured rules, and what state did the configured pathway return?
What dietary, accessibility, event, or dissatisfaction information must be recorded verbatim?
Does food safety, accessibility, a deposit, compensation, event terms or a serious complaint require manager ownership?
What approved update or next step can be shared with the guest after the manager decision?
Proposed operating requirements to configure and verify, including what happens when a system or human handoff is unavailable.
Explore how the selected tools support this restaurant process, then confirm the actions and records your setup can provide.
Carry the available booking and guest context across selected channels into the next staff review.
ExploreAnswer approved branch questions and record guest notes without interpreting food safety or commercial exceptions.
ExploreCheck identity-authorized bookings and current branch availability, then inspect the existing booking before retrying an uncertain update.
ExploreKeep permitted changes and manager-owned exceptions visible from request through the returned booking and guest-update states.
ExploreScope these around the selected implementation.
Select and validate the required provider pathways.
Pilot measurement definitions, not claimed customer results.
Measures the share of routine enquiries that reach a confirmed booking through the verified availability pathway.
Tracks whether a guest needed to contact the team again after a routine confirmation or permitted modification.
Measures the time from a recognised dissatisfaction signal to a named manager receiving the complete context.
Start with approved branch information and routine reservation enquiries while managers review any modification outside the agreed rules.
Use the configured availability pathway for permitted confirmations and modifications, recording the guest context for each handoff.
Add more branches only after their manager escalation, event, deposit, and food-safety boundaries are documented and tested.
