Delivery updates for your own drivers
Talabat and Deliveroo keep their customers updated inside their own apps. Direct orders don't have that, so the customer messages to ask where the food is while the driver is on the road. Three short templates do the job: order received with the estimated time, out for delivery with the driver's name, and delivered. Keep them to the order and the time — no 'try our new dessert' — so they stay utility and don't get approved as marketing.
KNET links for direct orders and catering deposits
Meta's in-chat payments aren't available in Kuwait, so a direct order is paid through a link from your gateway — MyFatoorah, Tap, UPayments or your bank — or in cash at the door. Send the link with the order summary before the kitchen starts. For catering, large Eid trays and big group bookings, a deposit link turns a verbal order into a commitment, and one reminder the day before covers anyone still unpaid.
One number for the counter, the host and every branch
In a shared inbox, orders go to the cashier on shift, bookings go to the host, catering enquiries go to whoever prices events, and complaints go to the branch manager. With more than one branch, chats are routed by area so the nearest kitchen takes the order. Shift changes stop losing orders, because the next person sees the notes and who is still waiting — not a phone left in a drawer.
Bringing regulars back after they go quiet
A regular who ordered every week and then stopped is worth more than a new follower. From your direct-order history, message the opted-in customers who haven't ordered in two weeks, then 30 days, then 60, each time with one specific reason: a new dish, the Ramadan ghabga menu, a catering tray for Eid, or a deal only on direct orders. Leave anyone with an open complaint out until a manager has spoken to them.
Google reviews after the meal
For dine-in, send the review link the same evening, once. For delivery, send it an hour or two after the order arrives, while the food is still fresh in their mind. If the reply says the food came cold or something was missing, route it to the branch manager to put right before it turns into a public one-star review. Keep the request apart from any offer — a discount in exchange for a review breaks Google's rules.
The mistakes that send customers back to the apps
Replying 'check the menu on Instagram' instead of sending it. Leaving the WhatsApp number unanswered during the rush, which is exactly when people are hungry. Broadcasting the daily special to everyone who ever ordered, until they block the number and Meta restricts it. Attaching a promo to a delivery update, which gets it approved as marketing. And taking a large catering order on a verbal 'confirmed' with no deposit.
Four numbers that show direct orders are growing
Count them for a month before and a month after: how fast the first reply goes out during the lunch and dinner rush, how many chats become an order or a booking, how many bookings don't show up, and how many direct customers order again within the month. Set those next to what you paid the delivery apps in commission over the same weeks — that comparison decides whether the API is paying for itself.
What we need to get your restaurant live
Your commercial licence for Meta's business verification, the number customers already know from your Instagram and delivery bags, the restaurant name exactly as it appears on your sign, your menu with prices and photos for the catalogue, and your delivery areas and fees. Verification is the step that waits longest, so we start it first and build the menu and flows while it runs. If the number is already on the WhatsApp Business app, coexistence may let you keep using the app alongside the API.