Catering and Majlis Orders on WhatsApp in Qatar

    November 2, 20267 min read

    A catering enquiry in Qatar almost never arrives as a form. It arrives as a WhatsApp message, usually late, usually short, and usually missing the one thing you need to quote it.

    "Thursday night, 40 people, machboos and salads. How much?"

    "Do you deliver to Al Khor?"

    "Is the mandi tray enough for 12 or should I take two?"

    Every caterer in Doha knows this inbox. It fills up at night, it fills up hardest in the two weeks before Ramadan and the days before Eid, and it fills up with the same eight questions. The difference between a caterer who converts those messages and one who does not is rarely the food. It is who answered while the customer was still deciding.

    This post is about that inbox specifically: what a catering business gets asked, which parts an AI assistant on WhatsApp can genuinely take down, which parts it must look up rather than guess, and which parts should never leave your team.

    A catering order is not a restaurant order

    It is worth separating these two, because they look similar and behave nothing alike.

    A restaurant order is for now, for one or two people, off a fixed menu, at a fixed price. The customer picks items, the kitchen makes them, and the whole thing is over in an hour.

    A catering order is a future commitment with four variables that all move at once:

    • A head count, which the customer will revise at least once.
    • A date and a time window, which is often tied to an event nobody controls — a wedding, a majlis, a company iftar, a graduation.
    • A quantity decision, not an item decision. The customer is not choosing between lamb and chicken; they are asking whether four trays feed thirty-five people.
    • A delivery and setup question — to a majlis, a farm in Al Shahaniya, a tower in West Bay with loading-dock rules.

    That difference is why generic order-taking automation reads so badly to a catering customer. It wants to put items in a basket. The customer wants to know whether Thursday is still open and whether two trays is embarrassing.

    The eight questions, and who should answer them

    Sort the inbox honestly and most of it is eight questions. Four are pure front-desk work. Two need a look-up. Two belong to a person.

    Front-desk work: take it down

    "Are you free on this date?" The single most common opener, and the one that most often goes unanswered until morning. Availability for a date and a time window is a fact your business already knows.

    "How many does this feed?" A tray-to-head-count question. If your own menu records that a mandi tray serves ten to twelve, that is an answer, not an opinion — and it is the question that most often decides the order size.

    "What is on the menu for a majlis of forty?" Your packages, read back in the customer's language, with the options you actually offer at that size.

    "Do you deliver to Al Khor / Al Wakrah / the Pearl?" Your delivery zones and the cut-offs attached to them.

    An assistant that answers those four, in Arabic or English, at eleven at night, has already done the useful part of the job. The order is not closed, but the customer has stopped shopping.

    Needs a look-up, not a guess

    "Is the Thursday before Eid still open?" This is the question where guessing is actively harmful. A confident "yes" on a date that is already committed costs you a customer and a reputation. The right behaviour is to look the date up in the business's own system and answer from what is there — and when the answer is not there, to say so and pass it on rather than improvise.

    "What did we order last time?" Repeat customers ask this constantly, and it is a look-up too. Note what this is not: it is not the assistant remembering a customer's personal preferences on its own. It is reading the record your business already keeps.

    Belongs with a person

    "Can you do it for 3,000 instead of 3,800?" Negotiation. A discount is a commercial decision with your margin attached, and it should sit with whoever owns that margin.

    "My cousin has a nut allergy — is the kabsa safe?" Allergy and dietary-safety questions are the clearest hand-over case in catering. The honest answer depends on your kitchen, your suppliers and your cross-contamination reality on that day. This is one to route to a person immediately, every time, and the sensible configuration makes it a fixed rule rather than something the assistant decides case by case.

    What a WhatsApp assistant should actually do with a catering enquiry

    Taking an order down is a sequence, and the order of the questions matters more than people expect.

    1. Date and window first. Everything else is wasted effort if the date is gone. Ask it first, look it up, and say plainly whether it is open.
    2. Head count second, because it drives every other answer — package, tray count, price band, delivery vehicle.
    3. Menu or package third, read from your own list, with the sizes you offer at that head count.
    4. Delivery, setup and address fourth, with your zones and cut-offs applied.
    5. Read the whole thing back and confirm before anything is committed. For a catering order this is not a nicety. A tray count the customer did not intend is a loss on the day, and an event date entered wrongly is a disaster. Nothing should be booked or ordered until the customer has confirmed it in the chat.
    6. Tell the owner. A caterer wants to know that a forty-head order for Thursday landed, at the moment it lands, not in a weekly report.

    Ramadan and Eid are the whole year

    Every caterer in Qatar runs a flat line for ten months and two spikes that pay for the year. Ramadan iftar and suhoor volume, and the Eid family orders immediately after.

    Two things break during those spikes, and they are both inbox problems rather than kitchen problems.

    The first is simultaneity. Fifty enquiries arrive in the same evening, and the ones answered at midnight convert while the ones answered at nine the next morning do not. The kitchen capacity did not change; the answering capacity did.

    The second is changed hours. Your Ramadan hours are not your normal hours, your delivery cut-offs move, and your menu is different. An assistant answering from last month's hours during Ramadan is worse than no assistant, because it answers confidently and wrongly. Whatever you use, the hours, the menu and the cut-offs have to be the ones you are actually working to that week — which means they have to be something you can change yourself, in minutes, without filing a request with a developer.

    Voice notes are not an edge case here

    Catering enquiries arrive as voice notes more often than almost any other kind of business messaging in the Gulf. A customer standing in a majlis describing what they need for Thursday is not going to type it.

    So "does it understand a voice note in Arabic?" is a real procurement question for a caterer, not a feature-list curiosity. CARE understands voice notes and replies in text — which is the combination that works in practice, because the customer wants to speak the order and read the confirmation back.

    What this does not solve

    Being straight about the limits is the only way this advice is worth anything.

    An assistant on WhatsApp does not make your kitchen bigger. If you are already at capacity on the Thursday before Eid, answering faster converts enquiries you then cannot deliver, which is worse than a slow reply. Capacity first, answering second.

    It does not negotiate, and it should not. It does not hold a deposit or take a payment — CARE never takes payments and never holds card details, so the money conversation stays exactly where it is today.

    And it does not replace the relationship. Catering in Qatar runs on repeat customers and word of mouth inside families and companies. What the inbox work buys you is the time to have those relationships instead of spending the evening typing tray counts.

    If you are deciding what to use

    Three questions separate tools that will survive a Ramadan from tools that will not.

    Can you change the hours, menu and delivery zones yourself? If every change is a support ticket, the system will be wrong during exactly the two weeks that matter.

    Does it look up the date, or guess it? Ask to see what happens on a date that is already fully booked. A tool that answers "yes, we are available" to that question will cost you more than it earns.

    Does it hand over cleanly? Watch an allergy question and a discount request. You want both out of the assistant's hands and in front of a person, with the whole conversation visible to whoever picks it up.

    Those three are worth more to a caterer than any feature list — and they are the questions a vendor who has actually run this in Doha will be comfortable answering.

    Want to see what CARE would book for you?

    CARE is the AI receptionist on WhatsApp for businesses that take bookings in Qatar and the GCC. It replies in Arabic and English around the clock, books and follows up — and its Value tab shows you what it booked.

    Wondering what setup involves? How CARE is set up, step by step

    Thamra Group

    Written by

    Thamra Group

    Editorial Team · Thamra Group

    Thamra Group builds CARE — the Arabic-first AI receptionist on WhatsApp, from Doha.

    Related Articles