A WhatsApp Business bot for a CDMX restaurant with a dynamic PDF menu sends the updated menu in seconds, takes reservations connected to your real calendar, collects deposits via Stripe, and logs every customer into your own CRM. Your bot handles WhatsApp 24/7 in your restaurant's voice — customers won't notice the difference. The code, data and domain are yours.
If you run a restaurant in Polanco, Roma, Condesa, Coyoacán, San Ángel, or anywhere in CDMX and WhatsApp orders are getting out of hand, this post shows you how to build it.
Why a Dynamic PDF and Not a Static Menu
The average CDMX restaurant changes its menu 3 to 5 times a year: spring, summer, fall, winter, plus special seasons. If the menu is static and lives in a PDF uploaded to Drive, this is what happens:
- Regular customers receive an outdated link (dishes you no longer serve)
- Staff manually sends PDFs over chat every time
- Weekend promotions don't propagate
- There's no way to know which dish gets asked about most on WhatsApp
A dynamic PDF lives in your own storage. Update it once, and every customer receives the current version. The bot sends the link, logs which customer requested which menu, and leaves the full trail in your CRM.
The Real Case: Automated Follow-Up at a School
Although the documented case comes from a school, the mechanics are identical for hospitality. There, the bot handled WhatsApp inquiries, booked appointments, followed up automatically at 24, 72, and 168 hours, and handed complicated cases to a person.
For a restaurant, what you measure is: confirmed reservation rate, recovered no-show rate, average ticket per returning customer.
Technical Stack for a CDMX Restaurant
What we recommend for 1 to 3 locations:
| Component | Tool | Function |
|---|---|---|
| Channel | WhatsApp Business API via Twilio | Messaging |
| PDF Menu | Supabase Storage with signed URLs | Current version |
| Calendar | Google Calendar API or proprietary system | Reservations |
| Payments | Stripe Mexico | Deposits and charges |
| Bot | Python backend + Claude or GPT-4 | Responses |
| CRM | Supabase Postgres with returning customers | Pipeline |
Deep integrations with your existing reservation system (Resy, OpenTable if applicable) are evaluated during discovery. We do not use turnkey bot platforms.
Typical Conversational Flow
Saturday night reservation use case:
- Customer: "I want a table for 4 on Saturday at 9pm"
- Bot: "Hi Sofía, let me check. We have 8:30 or 9:15 available. Which works for you?"
- Customer: "9:15"
- Bot: "Confirmed. I'll send you a reminder Saturday at 7pm. Here's the updated menu: [PDF link]"
- Bot sends reminder 2 hours before
- Customer confirms, record is in the system
Total time: 60 to 90 seconds. Zero phone calls. Zero lost reservations from missed responses.
Handling Seasonal Menus and Promotions
The PDF menu is updated once in storage. The bot:
- Sends the current menu link to every new customer
- Quotes dishes when the customer asks without opening the PDF (prices queried from the database)
- Suggests pairings based on a returning customer's history
- Proactively mentions the daily special without being asked
Promotions are loaded into a separate table. The bot decides when to mention them based on context — not based on a rigid template.
Cost and Timeline
Here is what MAGIA Solo looks like for an independent restaurant or small restaurant group:
- From $4,500 USD
- 15 calendar days
- WhatsApp bot + dynamic PDF menu + reservations + CRM + Stripe
- 3 training sessions for the manager or operator
- training and 6 months by your side
Common Mistakes from Restaurants That Already Tried
Three recurring patterns:
- They contracted a reservation SaaS that charges per table and doesn't export customer history
- They deployed a generic bot with no training on their actual menu or restaurant voice
- They still send the PDF manually over chat, again and again
All three are avoided with a proprietary architecture. Your customers are yours. Your menu is yours. Your bot is yours.
Next Steps for Your Restaurant
If your CDMX restaurant handles more than 30 weekly reservations via WhatsApp or more than 100 menu inquiries, you already have enough volume for the bot to take daily work off your team.
- MAGIA Solo for an independent restaurant or 1 to 3 locations
- MAGIA Core for a restaurant group with 4 to 30 locations and fragmented operations
A call with the team that actually builds it, not with an SDR.