How to send the menu via WhatsApp
A customer asking 'what do you have' shouldn't have to wait for a link to a heavy PDF. The menu can arrive directly in the chat.
One of the most common questions a restaurant receives is essentially "what do you serve" — whether directly or through a more specific question about a dish or a vegetarian option. Responding manually to this question, repeatedly, takes up time that the team could be using for another task.
This guide shows how to configure an AI agent to respond with the updated menu directly in the chat, in four steps.
Step 1 — Upload the menu to the agent's knowledge base
In the AI agent dashboard, upload the current menu PDF (or another catalog file) as a knowledge source. The agent now has direct access to the restaurant's actual information, without depending on someone manually writing every response.
Step 2 — Test the most common questions
Simulate typical customer questions — "what do you have," "are there vegetarian options," "how much does dish X cost" — and confirm that the agent responds correctly from the uploaded document, either by sending the full menu or by responding only to the specific question.
Step 3 — Configure responses filtered by preference
If the customer indicates a preference — "something gluten-free," "something lighter" — the agent can filter the menu options based on that information, instead of always sending the full list and leaving the customer to search on their own. This is particularly useful for restaurants with customers who have specific dietary needs.
Step 4 — Let the conversation advance to a booking
After clarifying doubts about the menu, the same conversation can naturally advance to a booking — without the customer needing to change channels or repeat information, which reduces the distance between initial curiosity and the decision to book.
Keep the menu always updated
When the menu changes — a seasonal dish, an adjusted price, a holiday menu — just replace the file uploaded to the knowledge base so that the agent's responses immediately reflect the new offer, without depending on manually reconfiguring every associated response.
Overall, a menu that is always accessible and updated within the conversation itself reduces friction between the customer's initial curiosity and the decision to book a table — and also works as a first impression of the attention to detail that the customer can expect to find later, once at the table.
You can configure this flow at no cost, uploading your restaurant's real menu and testing how customers react.
Frequently asked questions
What type of file can I upload as a menu?
The agent accepts PDFs, FAQs, and catalogs as a knowledge source — the most common is to upload the PDF of the menu that the restaurant already uses on other channels.
Does the agent respond only with the full menu or also to specific questions?
Both. It can send the full document when it makes sense, or respond directly to a specific question about a dish, ingredients, or options for particular diets.
How does the agent know that there has been a change in the menu?
It doesn't know on its own — you need to replace the file uploaded in the knowledge base whenever the menu changes. From that moment on, the answers will reflect the most recent version.
Can I filter suggestions by dietary restriction?
Yes. If the customer indicates a preference, such as 'gluten-free' or 'something lighter', the agent can filter the menu options based on that information instead of always sending the full list.
Can the conversation about the menu end in a booking?
Yes, in the same conversation. After clarifying doubts about the menu, the agent can proceed to propose a booking without the customer needing to change channels.