“Something spicy with chicken under 40.” “A starter, main and drink for 70.” “Nothing with nuts.” Guests type, tap a suggestion or speak, and your menu answers with your own dishes — price, spice and an Add button — instead of making them scroll every category.
What a guest sees after asking, and what you see at the end of the month.
A long QR menu on a phone means scrolling categories, opening dishes to check what is in them, and guessing what fits the budget.
A search box helps only if the guest knows the dish name. “Something light”, “not too spicy” or “dinner for two under 100” finds nothing.
The guest describes what they feel like, sees a few of your dishes that fit with the reason each one matched, and narrows it with a follow-up or by removing a filter. The full menu is one tap away the whole time.
The menu stays the menu. It just listens.
It reads the menu you already have. A few minutes of tags make it sharper.
Add Smart Menu for the branches you want. The ask bar appears at the top of your guest menu in place of the search box.
Dish names and descriptions in English and Arabic, categories, allergens and dietary tags. Changes to the menu are picked up within minutes.
In each dish, set a spice level and a few search words like “grilled”, “light” or “kids”. Guests then find it by those words too.
Pick up to six quick suggestions — spicy, light, under a budget, popular, surprise me, vegetarian, drinks, dessert — and your own welcome line.
They type, tap a suggestion or speak, follow up to narrow it down, and add dishes to the order with the normal Add button.
Your Smart Menu page shows how many guests used it, what they added to the cart and the sales of the dishes they found through it.
Changes to Smart Menu settings are written to the audit log with who made them.
Most requests are understood from your menu and a built-in vocabulary, with no AI call at all. Only unusual phrasing goes further — and even then the answer still comes from your menu.
Grouped by the job, not by the screen it lives on.
Guests describe what they feel like instead of hunting for it.
Each answer can be narrowed without starting again.
Answers come from your menu and nothing else.
For “feed us” rather than “find me a dish”.
Simple to run, and honest about what it earns.
The worry with “AI on the menu” is a chatbot that invents a dish, a price or an ingredient. Smart Menu is built so that can’t happen.
Results are read from your menu at the moment the guest asks, with today’s price and availability. Nothing is generated.
Where unusual phrasing needs an AI model, it only turns the guest’s words into filters like “chicken” or “under 40”. It never sees your dishes or prices, and never chooses one.
An excluded allergen stays excluded even in “closest options”. A dish whose own description names meat or fish is never shown as vegetarian.
Each restaurant’s Smart Menu searches that restaurant’s menu and nothing else — enforced by the database, not by instructions to a model.
It sits on your guest menu and hands everything after “Add” to the rest of Tahlib.
Smart Menu reads your dishes, categories, allergens and dietary tags, plus the spice level and search tags you add.
Dishes found through Smart Menu go into the same cart and checkout. Without ordering, guests still find dishes on your view-only menu.
An order placed from a Smart Menu result reaches the kitchen like any other QR order.
Guests who found their meal through Smart Menu pay for it the same way, into your own gateway.
Products are switched on individually, each priced per branch. View all products
Same menu, different reason to care.
Not a translated chatbot — a vocabulary built for menus here.
“أبغى دجاج حار بس مو ثقيل” is understood as spicy chicken, not heavy — along with Modern Standard Arabic and Arabic digits.
“spicy دجاج under 40” works. So do Hindi and Malayalam phrasing for the dishes and spice levels guests ask about most.
“Under 40” means 40 in your menu’s currency, and every result shows the price exactly as your menu does.
The ask bar, suggestions and reasons switch with the rest of your guest menu, right to left in Arabic.
No. Every result is one of your dishes, read from your menu when the guest asks, at today’s price. Where an AI model helps with unusual phrasing, it only turns the guest’s words into filters — it never sees your dishes or prices and never chooses one.
English and Arabic, including Gulf phrasing, plus common Hindi and Malayalam requests, and mixes of them. The ask bar and results are shown in English or Arabic, following the guest’s menu language.
Voice search is in Beta. Where it is switched on, guests tap the microphone and speak; the recording is turned into text and discarded, never stored. Typing and quick suggestions always work.
A guest who says “no nuts” never sees a dish you tagged with nuts, or one whose description names nuts, pistachios or similar — even among the closest options — and the exclusion stays on for their visit. It works from the allergen information you enter, so every allergen answer comes with a note to confirm with your staff.
No. It reads the names, descriptions, categories, allergens and dietary tags you already have. Adding a spice level and a few search tags to each dish makes the answers sharper.
Yes, with QR Ordering: results have the normal Add button, dishes with options open the usual options sheet, and checkout is unchanged. Without QR Ordering, Smart Menu still helps guests find dishes on your view-only menu.
No. Each restaurant’s Smart Menu searches only that restaurant’s menu, and the separation is enforced by the database itself — not by instructions to an AI model.
No. Tahlib keeps what was searched for — like “chicken, spicy, under 40” — to count usage, but not the guest’s own words or recordings, and nothing that identifies the guest.
Your Smart Menu page shows how many guests used it, how many searches they made, how many dishes they added to the cart from the results, the orders that included one, and the sales of those dishes before tax.
Ordinary use is included in the per-branch price, and most questions use no AI at all. A fair-use limit applies to the AI-assisted part; if a branch ever reaches it, Smart Menu keeps answering from your menu and your guests can still order.
Adding to the cart by voice (“add the second one”), comparing dishes side by side, suggestions based on a guest’s past orders, and asking through WhatsApp are not in the product yet. Smart Menu is on the guest menu, not the POS.
It is priced per branch, monthly or yearly for less, with a free trial and no per-question charges — switched on and off from your dashboard. The pricing section above shows both figures.
Switch Smart Menu on, add a few tags to your best dishes, and tonight’s guests can ask for what they feel like.
No card to start · nothing to install · AI included in the price