Decide what closed actually means for callers
A restaurant can be closed to diners while still receiving questions about tomorrow’s service. Equally, the dining room may be open after takeaway orders have stopped. Write down your opening hours, kitchen cut-off, collection arrangements and any exceptional closures separately. The person maintaining your reception information should check these against the instructions staff give customers.
Closed-message handling should explain the situation without suggesting that an order or reservation has been accepted. A callback request records a need for follow-up; it does not reserve a table. If future orders or bookings are available through enabled NeroWeb or NeroBooking workflows, confirm exactly what those workflows support rather than treating every after-hours enquiry as a transaction.
- Ask the restaurant manager to approve the hours and service boundaries.
- Agree which questions can be answered from configured business knowledge and which need a person.
Choose a busy-service response without overstating capacity
During a rush, distinguish pressure on the telephone from pressure on the kitchen or dining room. If staff cannot answer calls but can still fulfil orders, an enabled ordering workflow may remain appropriate. If fulfilment capacity is exhausted, answering more calls must not create the impression that more orders can be accepted. Agree how intake will be restricted and confirm the supported controls with the team.
Handover is useful only when someone can respond. AI Reception supports handover to a configured UK number or SIP destination, but sending every busy-period call to an unattended phone simply moves the problem. Use callbacks where suitable, with wording that reflects actual staffing. Current call and usage limits apply; do not plan around unlimited call handling.
- Give the duty manager responsibility for deciding when intake needs restricting.
- Confirm who updates the relevant configuration and who checks it before normal intake resumes.
Make callbacks a named responsibility
Choose a callback owner for each shift, plus a replacement for breaks or absence. Agree when that person will review requests and what they can realistically tell callers about timing. Avoid promising a response within minutes if the same person is seating guests and managing collections. A useful commitment is one the shift can consistently meet.
Staff should distinguish a request awaiting contact from an accepted booking or order when they follow up. Before making arrangements, they should check current availability and confirm the outcome with the customer. Optional recordings and transcripts depend on settings and retention, so confirm what is available rather than assuming every conversation can be replayed.
- Include outstanding callbacks in the shift handover.
- Give unresolved requests an owner rather than leaving them for whoever notices first.
Test a closed-to-busy evening before relying on it
Hypothetical example: a restaurant opens at 17:00, expects a busy 19:00 service and stops takeaway orders at 21:00. At 16:00, a caller asks for a table that evening. The response should explain the opening hours and follow the agreed booking or callback route, without presenting a callback request as a reservation.
At 19:00, the duty manager decides the kitchen cannot accept further takeaway orders. Test that the agreed intake restriction is reflected in the customer journey, while general enquiries still receive appropriate information. At 21:15, ask to place an immediate order: the response should explain the cut-off, not imply that the kitchen will fulfil it.
- Have a colleague make test calls for each scenario using ordinary customer language.
- Check that handover reaches the intended staffed destination and callback requests can be found by their owner.
- Test the return to normal intake and check that any order or booking outcome matches what the caller was told.
Check the outcome, not just whether the call was answered
A successful test leaves no ambiguity: the caller knows whether they received information, requested a callback or completed a supported order or booking process. The responsible colleague can find the request, and the restaurant has not accepted work outside its agreed capacity. If those checks fail, revise the information, routing or workflow before relying on it during service.
Keep payment instructions equally clear. Where card payment is needed, use secure checkout links; customers must not speak full card details to the AI. After the first live service, ask the callback owner and duty manager where callers became confused, then review the relevant settings and repeat the affected test.
GOOD TO KNOW
Common questions
Can we answer enquiries while order intake is paused?
Plan these as separate activities. Configured business knowledge can support enquiries, while enabled workflows govern orders and bookings. Confirm how intake restrictions will work in your setup before service.
Does requesting a callback secure a table?
No. A callback request is a request for contact. The customer needs a clear booking outcome through the supported booking process or confirmation from your team.
Should every busy-period call be handed to the manager?
Only if the manager can realistically answer. Otherwise, an agreed callback route may be more useful. Test the configured UK number or SIP destination with the person responsible.
Can we promise that every call will be handled?
Do not promise unlimited availability or capacity. Current call and usage limits apply, and your plan must also account for staffing, fulfilment capacity and follow-up.