Protect service periods from phone interruptions
During a busy service period, staff attention belongs with guests, food preparation, and the dining room. Elevoi can answer calls 24/7 and sort them into reservations, changes, hours, directions supplied by the restaurant, order questions, or a request for staff. For a Toronto restaurant, the useful outcome is not a long conversation; it is a confirmed reservation or a concise handoff.
The restaurant defines which requests can be completed automatically and which need a person. Calls outside those rules receive a clear pending status rather than an invented answer.
Keep the reservation record authoritative
The receptionist should search the connected reservation system using the restaurant’s real rules. It can collect party size, preferred time, name, and contact information, then confirm only an available option. Special requests are recorded as requests, not guarantees.
If the system is unavailable or the request falls outside configured limits, Elevoi captures the details for staff. SMS follow-up states whether the reservation is confirmed or waiting for review.
Answer menu questions without guessing
Elevoi can provide restaurant-approved information about service hours, ordering processes, and menu availability language. It should never guarantee that an item is in stock. For ingredient or allergen questions, the caller must confirm with the kitchen because recipes, preparation, and availability can change.
The AI should not infer dietary safety from a menu label. It can record the question and route it to staff. Learn about the general guest-call workflow at AI receptionist for restaurants.
Give large-party requests a complete handoff
A useful handoff includes the caller’s name, contact details, requested date and time, party size, and the specific decision they need from staff. It can also record an accessibility or seating request without promising that it can be met.
The restaurant chooses the owner for each category and an escalation route for time-sensitive issues involving an active reservation or order. If a person is unavailable, Elevoi sets an honest callback expectation using approved wording.
Review calls against real outcomes
Order-related calls need their own boundary. Elevoi can explain the restaurant’s approved ordering channels, capture a callback request, or route an issue involving an active order. It should not promise that a modification is accepted until the ordering system or a staff member confirms it. Item availability is never guaranteed, and questions about ingredients or allergens must be confirmed with the kitchen.
The restaurant can identify which active-order issues deserve immediate transfer and which can enter a callback queue. A useful summary includes the caller’s name, contact information, order reference when available, and the requested action. It avoids conclusions about fault and lets the responsible staff member review the current order record.
Voicemail fallback should follow the same categories as live handling. If a transfer fails, the message still needs the reservation or order reference, contact details, and requested action. Staff should be able to understand the issue without listening to an unstructured account during service.
The team can sample routine reservations, changes, menu questions, and calls that requested a person. Review whether the reservation record matches the confirmation, whether pending requests reached the right owner, and whether callers were told to confirm allergen or ingredient details with the kitchen.
Improvements may include shorter questions, clearer status language, or narrower booking permissions. A reliable AI receptionist reduces interruption while preserving staff judgement. It does not replace kitchen confirmation, hospitality decisions, or the team’s control of availability.