A restaurant owner finishes service at 11pm, closes up and sits down with their phone. Twenty-three new messages. Can we book for Saturday? Do you have a vegan menu? Is there parking? Can you do a birthday cake? Are you open on Monday? They answer until 12:30am. Tomorrow will be the same.
Restaurant owner time saving is rarely about the kitchen. It is about the stream of messages that arrive while the owner is working and pile up for the end of the night.
The week before
Monday. Day off, spent partly answering weekend messages.
Tuesday. Messages during lunch service go unanswered. A group booking enquiry waits until midnight.
Wednesday. A guest asks about allergies at 3pm. The owner replies at 11pm, and the guest has booked elsewhere.
Thursday. A catering enquiry for an office lunch sits for two days.
Friday and Saturday. Too busy to look at messages until after service. Twenty to thirty messages each night.
Sunday. A quieter day, spent catching up.
Total time on messages: ten to twelve hours, mostly late at night.
What the messages were
- Booking requests.
- Menu and dietary questions.
- Opening hours and parking.
- Group and event enquiries.
The first three had standard answers. The last needed the owner.
The week after
The owner updated the website with menus, dietary labels, hours and parking details, then added SpideyChat for restaurants, which answers those questions at any hour and captures booking and event requests.
Tuesday. A group enquiry during lunch was captured with dates, numbers and dietary needs. The owner confirmed it in five minutes after service.
Wednesday. The allergy question at 3pm got an instant answer from the menu, and the guest booked.
Friday and Saturday. Routine questions answered while the owner cooked. After service, a short list of requests to confirm.
Total time on messages: two to three hours.
What the owner did with the time
The hours back went into things that had been postponed for months: planning a new seasonal menu, training a new server, and simply sleeping. The owner also started replying to reviews, which had been neglected, and noticed more guests mentioning how quickly they got answers before booking.
What still needs a person
Complaints, large events, press enquiries and supplier issues still reach the owner. The difference is that they arrive in a short, clear list rather than buried among questions about parking and vegan options. The owner can deal with the important things properly, instead of rushing through everything at midnight with a tired head.
The same pattern elsewhere
Owner-operators in every industry face this. Solo estate agents lose evenings to listing enquiries, as described in solo agents and the evenings spent answering listings, and founders lose them to support, as covered in time-saving chatbot workflows for busy founders.
Why guests benefit too
Guests used to wait hours for a reply, often until after midnight. Now they get answers in seconds. Late-night booking requests, covered in booking requests that arrive after the kitchen closes, are captured instead of lost, and guests who cannot get through by phone find answers on the website, as described in what happens to restaurant enquiries when the phone rings out.
To see how your messages would be handled, try an assistant on your restaurant website, or see the features.