WhatsApp Chatbot for Restaurants in Qatar: Orders, Tables, Iftar

A restaurant in Doha does not get one kind of WhatsApp message. It gets twelve. «وين موقعكم؟» at 1pm from someone already in the car park of the wrong tower. "Do you have a family section?" at 7pm. A voice note at 11:40pm asking whether the kitchen is still open. A screenshot of a dish someone saw on Instagram, with the question «كم سعره؟». An order for six mixed grills to West Bay, sent as three separate messages, the last one being the building name. And somewhere in the middle, a catering enquiry for forty people on Friday that is worth more than the whole evening's covers and gets answered four hours later, because the phone is behind the till and the till is busy.

That is the real problem. It is not that restaurants ignore WhatsApp — it is that WhatsApp is busiest exactly when the floor is busiest. The lunch rush, the 8pm-to-11pm peak, the hour before iftar in Ramadan. The staff member holding the phone is the same person seating guests or packing a delivery bag. Messages pile up, half get a one-word reply, and the ones that would have turned into bookings quietly go cold. An assistant on the same number does not replace anyone; it covers the hours and the overflow where nobody was replying anyway.

What does a WhatsApp chatbot for restaurants actually do all day?

Strip away the demos and the feature lists, and the work is narrow and repetitive. Here is what lands on a Doha restaurant's number in a normal week, and what an assistant can genuinely close without a human:

• Location and parking. The pin, the landmark, whether there is valet, which entrance of the mall. In Arabic or English, depending on how the customer wrote.
• Opening hours and kitchen closing time. Including the fact that Friday starts late, and that last orders are earlier than the door closing time.
• Menu questions. Prices, what is in a dish, what is spicy, what is vegetarian, what contains nuts or dairy. Sending the menu itself when someone just says «المنيو لو سمحت».
• Delivery and pickup. Whether you deliver to that area, the minimum, roughly how long it takes, and taking the order itself — items, quantities, name, location, phone — then handing a clean summary to the team instead of a scroll of six messages.
• Table bookings. Date, time, number of people, indoor or outdoor, family section, high chair, birthday cake on the table.
• Large groups and catering. The questions nobody wants to answer on the floor: trays for fifty, majlis setups, corporate lunch boxes, Eid gatherings. These are captured as leads with the details already collected, so the manager calls back with everything in hand.
• The handover. A complaint, a refund, a wrong order, a VIP regular, anything unusual — straight to a person, with the conversation history attached.

The pattern matters more than the list. Roughly the same twenty questions, asked thousands of times, in two languages, at hours when nobody is free. That is the part worth automating. The judgement calls stay human.

Is a WhatsApp chatbot free?

Partly, and the free part is smaller than it looks. The WhatsApp Business app costs nothing: you get a business profile, a catalogue, quick replies, labels, a greeting message and an away message. For a single small outlet with one person on the phone, that is a real tool and you should be using it before you buy anything.

What it does not do is understand. An away message replies the same sentence to «عندكم توصيل للوكرة؟» and to "can I book a table for 12 on Saturday?". It cannot read the order, check whether Saturday 9pm is already full, or notice that the customer switched to Arabic halfway through. The moment you want actual answers instead of an acknowledgement, you move to the WhatsApp Business Platform, where Meta charges per conversation, and you add software on top that knows your menu and your tables. So: the channel is cheap, the intelligence is not.

How do you set up a WhatsApp chatbot for a restaurant?

The mechanics are less dramatic than most owners expect. You need a phone number that is not tied to the WhatsApp app on a handset in the kitchen — usually a new line, sometimes your existing landline, migrated. You verify the business with Meta, connect the number to the platform, and from there the work moves off the phone and into a dashboard.

The real setup is content, not technology. Someone has to write down what the restaurant actually knows: the menu with current prices, the delivery zones, the hours including the late-night exception on weekends, the rule about bookings of more than eight, who gets called when a customer is unhappy. With CARE this is all done from a dashboard with no code — you type the answers, you set the booking rules, you decide which messages go to which person — but any tool will ask you for the same material. A restaurant that already has a tidy menu PDF and a clear booking policy is set up in an afternoon. One that has three price lists and nobody sure which is current spends the afternoon on the price list.

How do you use a chatbot in WhatsApp without sounding like a machine?

The thing that gets a Gulf customer to stop replying is not automation — it is a stiff, translated tone. Someone writes «السلام عليكم، عندكم طاولة اليوم ٩؟» and gets back formal classical Arabic with a menu tree: Press 1 for reservations. They close the chat and call the place next door.

Three rules hold up well in Qatar. Reply in whichever language the customer used, and follow them if they switch mid-conversation — people here mix Arabic and English in one sentence and expect you to keep up. Keep the Arabic natural and Khaleeji, the way your own staff would type it, not the way a manual would print it. And make the handover fast and obvious: if the message is a complaint, a special request or anything the assistant is not sure about, a human takes over on the same thread, with no "an agent will contact you within 24 hours".

Can you create a WhatsApp chatbot free, and what breaks when you do?

You can build something free. Button menus, keyword triggers, a flow that asks for a number and then a time. They work until a customer does something human. They break on "actually make it 7 instead of 6", on orders sent as a voice note, on «نفس الطلب اللي قبل», on a booking for the second night of Eid when your hours are different, on a customer who answers a question with another question.

They also break on ownership. A free flow built on someone's personal account, with no record of where the chats live and no way to hand a conversation to a manager, is a liability in a business where orders are money. For a quiet café taking four messages a day, a free setup plus the Business app is honestly enough. For a restaurant doing delivery and bookings through WhatsApp, it is a prototype, not a system.

What does a WhatsApp chatbot for business price look like in Qatar?

Published, in our case: CARE is QAR 4,800 or QAR 9,600 per year depending on how much the assistant has to handle, with larger multi-branch setups quoted. On top of that sit Meta's conversation charges, which depend on volume.

The comparison owners actually make is against the cost of the message nobody answered. One catering enquiry for a company lunch, one group booking of fifteen, one delivery order that went elsewhere because the reply came at midnight — that is the arithmetic. Judge it against covers and orders, not against the price of a free app.

Can a WhatsApp chatbot for website visitors work the same way?

Most restaurant websites in Qatar exist to be scrolled on a phone for two things: the menu and the number. The useful move is not a chat window in the corner — it is a WhatsApp button that opens a conversation on the number you already answer, with the same assistant behind it. The customer stays in the app they live in, you keep one thread per customer instead of two, and the conversation carries on after they have closed the browser. The same goes for the link in your Instagram bio and the QR code on the table.

Is this the same as a WhatsApp chatbot for healthcare, ecommerce or real estate?

The plumbing is the same. The conversation is not. A WhatsApp chatbot for healthcare spends its day on appointment slots, doctor availability and privacy. A WhatsApp chatbot for ecommerce answers "where is my order" and sizing questions. A WhatsApp chatbot for real estate qualifies budget and area before anyone drives to a viewing.

Restaurants are the fastest-moving of the three. The decision window is minutes, not days — someone is hungry now, or is choosing between two places for tonight. The same assistant also handles WhatsApp chatbot for appointment booking work when you need it: private dining rooms, chef's table, event enquiries, a tasting for a wedding caterer. Those behave like bookings, with a date, a time and a confirmation, and they are usually the highest-value messages your number receives.

What changes during Ramadan and Eid?

Everything about the timetable, which is why a static away message fails every year. The kitchen is closed through the day, the phone fills with iftar bookings from mid-afternoon, suhoor service runs past 2am, and ghabga enquiries for groups of thirty arrive from companies and families at once. Then Eid arrives with different hours again, fully booked lunches, and a spike in large family tables.

An assistant handles this if someone remembers to update it: Ramadan hours, the iftar seating times, which packages exist, when bookings close, what happens to a table held past the call to prayer. It is a fifteen-minute edit in the dashboard before the month starts. The restaurants that skip it spend Ramadan correcting an assistant that is still quoting January's hours. The same applies to Qatar National Day, school holidays and the weekends around big matches at Lusail.

What should you prepare before switching it on?

Before you connect anything, get these in one place:

• The current menu and prices, in Arabic and English, in a file you can actually send.
• Hours per day, including last orders, weekend differences, and your Ramadan and Eid schedule.
• Delivery zones and minimums, and how you want orders passed to the kitchen.
• Booking rules: how far ahead, maximum group size without a manager's approval, how long a table is held, which areas can be requested.
• Allergen and dietary answers you are willing to put in writing.
• Escalation: who takes over for complaints, large groups and catering, and on which phone.
• One number that everyone — the sign, the delivery bag, Instagram, Google — points to.

Write those down and the setup is straightforward. Skip them and you will be debugging your own restaurant, not the software.

Book a demo on thamragroup.com.