A restaurant’s WhatsApp is busiest exactly when the staff are least able to look at it. Lunch service and Friday evening are when the messages arrive and when nobody is free.
The questions that repeat
- "Menu eka ewanna" — the same request, dozens of times a day.
- "Delivery karanawada [area]?" — a yes or no you already know.
- "Dæn open da?" — answerable from opening hours.
- "Kiyada [dish]?" — a price.
- "Table ekak thiyenawada 7ta?" — the one that genuinely needs a person.
Four of those five are lookups. Only the last needs judgement — and it is the one that gets missed while staff type out the menu for the twentieth time.
What automation should handle
What it must not do
- 1Confirm a table without a person checking. An overbooked Saturday is a real cost.
- 2Promise a delivery time the kitchen has not agreed to during a rush.
- 3Take an order for a dish that has run out — which means the menu it reads from has to be current.
- 4Handle a complaint about food. That needs a person, immediately.
The rule is the same as everywhere else: automate the lookups, escalate the promises. Anything that commits the kitchen belongs to a human.
The menu problem
Most restaurants send a photo of the menu, which cannot be searched and goes stale the day a price changes. An agent working from a real item list can answer "kiyada kottu?" directly — but only if somebody keeps that list current. A stale list quoted confidently is worse than a photo.