For a South African restaurant, AI is worth having for exactly three jobs: taking the booking when nobody can get to the phone, answering the same eight questions about parking, dietary options and closing time, and following up the enquiry that arrived at 22:40. It is not worth having for cooking, for menu design, or for anything that needs a person to make a judgement call about a guest.
What does an AI chatbot actually do for a restaurant?
It sits on your website and answers instantly, at any hour, in any of the eleven official languages. The four things it handles best, in the order restaurants notice them:
- Table bookings. It takes the date, the party size and the dietary requirements, checks the diary and confirms — including at 23:00 on a Saturday when the phone is nowhere near anyone.
- The eight repeated questions. Where to park. Whether you are open on a public holiday. Whether the kitchen closes before the bar does. Whether there is a halaal or a vegan option. Whether children are welcome. Whether you take the card the bank just reissued.
- Function and large-group enquiries. These are the highest-value messages a restaurant gets and the ones most likely to be answered two days late. The bot captures the date, the headcount and the budget and puts it in front of a person the same minute.
- Post-visit review requests. A timed message asking for a Google review, sent once, to people who actually came.
How much does it cost a South African restaurant?
A single-site restaurant is a Starter build: R299 a month plus a R250 once-off setup fee, so R549 at checkout and R299 a month after that. Month to month, no contract. A group with several sites, a separate functions diary and a booking system to talk to is usually Intermediate at R649 a month.
The comparison worth making is not against nothing. It is against what happens now.
| The phone and the inbox | A trained chatbot | |
|---|---|---|
| A booking at 22:40 | Answered tomorrow, if at all | Confirmed in about a second |
| Six enquiries during service | A queue, or missed | All six, at once |
| A function enquiry on Sunday | Read Monday, quoted Tuesday | Captured and escalated immediately |
| Afrikaans, isiZulu, isiXhosa | Whoever is on shift | All eleven official languages |
| Load-shedding | Phone lines and card machines down | Runs in the cloud, unaffected |
| Cost | Staff time during service | R299/month, whole restaurant |
What should the bot never do in a restaurant?
Three things, and getting these wrong is how a chatbot becomes the thing guests complain about:
- Never invent an allergen answer. If somebody asks whether the sauce contains nuts, the correct behaviour is to hand over to a person, not to guess from a menu description. We configure that as a hard rule, not a preference.
- Never handle a complaint. A guest who had a bad evening needs a human within one message. Anything with an emotional temperature goes straight to a person with the conversation attached.
- Never pretend to be one. If a guest asks whether they are talking to a person, it says what it is.
Does it work for a takeaway rather than a sit-down restaurant?
The jobs change. A takeaway gets fewer booking questions and far more "how long", "do you deliver to my suburb" and "where is my order". Those are all answerable from your own delivery-zone list and trading hours, which is exactly the material the bot is trained on. Ordering and payment are a bigger build and usually sit with whichever ordering platform you already use — we connect to it rather than replacing it.
What about load-shedding?
This is the South African question that does not come up in overseas write-ups of the same subject. Your phone line, your card machine and your Wi-Fi go down with the power; the chatbot does not, because it runs in the cloud and your guests are on their own phones. In practice the bot is answering hardest at exactly the hour your restaurant is least able to.
How long does it take to set up?
Thirty minutes during business hours, Monday to Friday, 08:00 to 16:30 SAST. You send us your menu, your trading hours, your parking situation and your booking policy; we train it, you check it, it goes live. Sign up outside those hours and it lands at 08:30 the next business day.
The booking you lose is never the one you turned down. It is the one that arrived at 22:40 and went to the restaurant down the road that answered.
What is the honest version?
If your phone is answered promptly all day and your inbox is empty by close, a chatbot will not change your revenue much. If you know there are enquiries sitting unread from the weekend, that is what this fixes, and it fixes it for R299 a month rather than another pair of hands. Our Website Chatbot page sets out the tiers, and there is a free trial if you would rather watch it answer your own questions than take our word for it.
Where we do this
We run AI for restaurants for businesses across South Africa. Cape Town, Paarl and Knysna each have a page covering what is different about doing it there, down to the suburbs and the languages.