WhatsApp Chatbot for Restaurants: What Your Kitchen Really Needs

It is Friday, 8:30 pm, at a busy burger place in Johar Town. The counter phone has 63 unread WhatsApp chats. Somewhere in that pile are eleven real orders, four people asking "delivery DHA Phase 5 tak hoti hai?", two complaints about a cold order, one voice note from a regular who wants his usual, and a family asking if you have a table for eight at 9:30. The cashier answers in order of arrival, so the PKR 6,000 order waits behind someone asking for the menu again.

That is the problem a WhatsApp chatbot for restaurants is supposed to solve. But "restaurant" covers very different businesses, and a bot that is perfect for a cloud kitchen in Karachi will annoy the customers of a family restaurant in F-7. So here are five kinds of restaurants: what each should automate, what it should leave to a person, and what to connect. Find yours.

Before you pick features, read last Friday's chats

Scroll back through one busy evening on your WhatsApp and sort every chat into three piles: questions (menu, prices, timings, delivery areas), orders, and things that need a human (complaints, refunds, special requests). In many restaurants the question pile turns out to be the biggest, and those chats are the easiest to automate safely.

If questions dominate, you need a bot that answers well. If orders dominate, you need one that takes orders cleanly and gets them to the kitchen. If the human pile is big, a bot will not fix that. Look at your food and delivery first.

The delivery-heavy fast food outlet: speed beats charm

Burgers, pizza, shawarma, broast. Orders peak between 8 pm and midnight, many pay cash on delivery, and the same people order every week.

What the chatbot should do

• Send the current menu and deals instantly, as text with prices, not only a blurry photo of the printed menu.
• Check the delivery area first. If you do not deliver to Bahria Town, say so in the first reply, not after the customer has built a full order.
• Take the order item by item, read it back with the total and delivery charge, and ask for the address and a landmark.
• Ask how they will pay: cash, JazzCash or EasyPaisa. For a first-time customer with a large COD order, a quick confirmation step saves you a wasted rider trip. We wrote about that in our COD order confirmation guide.

What it should NOT do

Do not let it promise delivery times it cannot know. "40 minutes" on a Friday night becomes a complaint when the rider takes 75. Let the bot give the range your manager sets for that evening, and let the manager change it in one place when things get busy.

What to connect

The order has to reach the kitchen without someone retyping it. The simplest version is a kitchen printer or a screen that shows each confirmed order. If your POS has an API, the order can go straight into it so stock and sales stay correct. If not, even a shared Google Sheet is better than copying from the phone. This is the kind of link we build under API integration.

The family dine-in restaurant: reservations, not just menus

Think of a desi or BBQ restaurant in Gulberg or Blue Area where most revenue comes from tables, not deliveries. Here WhatsApp is mostly about bookings, birthdays and big family groups.

The bot should collect the date, time, number of people, a name and any request (high chair, cake, separate family section) and then check against your available slots. When a slot fills, it offers the next free time instead of a flat no.

What it should not do: confirm bookings for 20 or more people on its own. Large groups need a manager to discuss set menus and advance payment.

Connect it to whatever holds your bookings today, even if that is a Google Sheet, and send a reminder message on the morning of the booking. The reminder also gives people an easy way to cancel, so the table goes to a walk-in instead of sitting empty.

Honestly, if you take ten bookings a week, you might not need this yet. A well-organised WhatsApp Business App with saved quick replies will do the job. The bot starts paying for itself when bookings and questions arrive faster than one person can answer during service.

The cloud kitchen living on Foodpanda: your own channel, slowly

If almost all your orders come through Foodpanda, you already know the problem: the commission eats a big part of every order, and the customers belong to the app, not to you. Many try to move repeat customers to direct WhatsApp orders with a card in the bag.

A chatbot helps because nobody sits at a counter. It answers the menu, takes the order, asks for payment and pushes it to the same screen the kitchen uses for app orders, so the cooks see one queue.

What it should not do is start sending deal broadcasts to everyone who ever ordered through Foodpanda. You do not have their permission, and in most cases you do not have their numbers at all. Build your own list from people who message you directly.

You might not need a bot yet: if direct orders are a handful a day, the WhatsApp Business App and a good menu link are enough for now.

The cafe or bakery with custom cake orders: let a human close the order

A bakery in Faisalabad or a cafe in Clifton gets two very different kinds of chats. Routine ones: "Is the cafe open?", "Do you have chocolate fudge today?", "What is the price of a 2 pound cake?". And custom ones: a three tier wedding cake with a photo reference, a name in Urdu on top, delivery on Saturday at 4 pm.

Let the bot answer the routine ones fully. For custom orders, the bot should collect everything in a structured way: date, weight, flavour, design photo, message on the cake, pickup or delivery, and advance payment by JazzCash or bank transfer. Then a person confirms the design and the final price. A wrong cake on a wedding day is not something an apology fixes.

Connect custom orders to a simple order board, a Google Sheet or a basic CRM, with the pickup date as the main column.

The multi-branch chain: routing is the whole job

With three branches in Lahore and one in Islamabad, the main question is not "what is on the menu". It is "which branch should this chat go to". The bot should work out the branch from the area or a pin location, send the order to that branch's screen or printer, and route complaints to that branch manager.

What it should not do is let every branch run its own number and its own answers. Prices drift and customers notice. One number, one set of answers, and a shared inbox where each branch sees only its own chats is far easier to control.

Chains are also where WhatsApp Coexistence helps most. The head office keeps the WhatsApp Business App on its phone as before, and the official platform adds AI replies around the clock, the shared inbox and template broadcasts on the same number. Our plans start from PKR 12,000/month. How the phone and platform share one number is in our Coexistence explainer.

Friday 9 pm and Urdu voice notes: where restaurant bots break

Most bots look fine on a quiet Tuesday. They break at peak hour, in three predictable ways.

The menu is out of date. The bot happily sells the BBQ platter the kitchen ran out of at 8. Give the manager one simple way to switch items off for the night.

Orders arrive faster than the kitchen can cook. The bot can take fifty orders in ten minutes. Your tandoor cannot. Set a limit per time slot, and have the bot offer a later time once it is reached.

Voice notes. In Pakistan, a lot of food orders come as voice notes, especially from older customers and from anyone who would rather talk than type with one hand on the steering wheel. When we set up voice note understanding for clients, we found that speech-to-text sometimes wrote Urdu in Hindi (Devanagari) script, and the AI then replied in Hindi. We fixed it by forcing Urdu transcription. The lesson for you: before going live, have your staff send ten real voice notes with real dish names, area names and some background noise, and read what the bot understood.

Our optional WhatsApp Voice Replies add-on (PKR 2,500/month for 400 voice replies) also lets the AI answer as a voice note, which suits customers who never read long text. It is worth testing for a desi place with an older customer base.

At iftar in Ramadan, all of this happens inside one hour. Test before Ramadan starts, not on day one.

WhatsApp rules that catch restaurants out

Many owners expect to message their whole customer list from the dashboard for free. That is not how the official platform works. When a customer messages you, you can reply freely for the next 24 hours. When you start a conversation yourself, for example a "Weekend deal: 2 pizzas for PKR 2,499" broadcast, it must be an approved template, and Meta charges for it per message. Across a list of 5,000 customers that adds up, and Meta sets and changes those prices, so check the current rate before you plan a big campaign.

Two more rules matter for restaurants:

• Opt-in. Only send deal broadcasts to people who agreed to receive them. A simple line on the order confirmation ("Reply YES to get our weekend deals") builds a clean list over time.
• Easy opt-out. When someone replies "stop" or "band karo", remove them right away. Customers who block or report your number put the number at risk, and a restricted number on a Friday night is a real loss of orders.

The wider safety side, including warm-up and opt-out handling, is part of how we run WhatsApp automation.

What to do before this weekend's rush

You do not need any software to start. Do these this week:

1. Sort one busy evening of chats into questions, orders and human issues, and count each pile.
2. Write your delivery areas as a clear list, with the delivery charge and minimum order for each.
3. Type out your menu with current prices as text. This is what any bot will learn from, so it must be right.
4. Write the five answers your staff type most often and save them as quick replies in the WhatsApp Business App.
5. Decide who handles complaints and large group bookings, and what time the bot should hand over to them.
6. Record ten real voice notes in Urdu and Roman Urdu with your dish names. Keep them for testing.

Then you will know which type you are and what your bot actually needs to do. If you want us to look at your chats and tell you honestly whether a bot is worth it yet, message us on WhatsApp at 0339 4285556 or use our contact page. You can also see how we work with businesses in Pakistan.

Further reading

See how this looks in practice across our AI automation, custom CRM and lead generation services, or tell us the outcome you need.