--- title: "WhatsApp Bot for CDMX Restaurants: Dynamic PDF Menu" description: "Deploy a WhatsApp Business bot for your CDMX restaurant with dynamic PDF menu, real-time reservations, and Stripe payments. No locked licenses. Code is yours." slug: "bot-whatsapp-business-para-restaurante-cdmx-con-menu-pdf-en" url: "https://catalizadora.ai/blog/bot-whatsapp-business-para-restaurante-cdmx-con-menu-pdf-en" cluster: "implementacion-ia/bot-whatsapp-business" author: "Pablo Estrada" published_at: "2026-05-13T19:25:15.555328+00:00" updated_at: "2026-05-13T19:25:15.555328+00:00" read_minutes: "8" lang: "en" --- # WhatsApp Bot for CDMX Restaurants: Dynamic PDF Menu > Deploy a WhatsApp Business bot for your CDMX restaurant with dynamic PDF menu, real-time reservations, and Stripe payments. No locked licenses. Code is yours. 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. Total investment starts at $4,500 USD one-time, operational from $200 USD/month. Your bot handles WhatsApp 24/7 in your restaurant's voice — customers won't notice the difference. No retainers. Code is 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 (40 sends per day = 4 hours of lost labor) - 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: 26.5% Conversion, 7,197 Organic Sessions Although the documented case comes from an educational institution, the mechanics are identical for hospitality. Real metrics from the case: - 113 total conversations handled by the bot - 30 reservations closed (26.5% conversion) - 79 automated follow-ups at 24, 72, and 168 hours - 57 handoffs to a human when complexity was detected - 7,197 organic sessions in 60 days with zero additional ad spend - 32.9% bot conversion vs. 14.1% paid traffic conversion For a restaurant, those metrics translate to: 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: 1. Customer: "I want a table for 4 on Saturday at 9pm" 2. Bot: "Hi Sofía, let me check. We have 8:30 or 9:15 available. Which works for you?" 3. Customer: "9:15" 4. Bot: "Confirmed. I'll send you a reminder Saturday at 7pm. Here's the updated menu: [PDF link]" 5. Bot sends reminder 2 hours before 6. 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 MAGIA / Solo covers the use case for an independent restaurant or small restaurant group: - $4,500 USD one-time - 15 calendar days - WhatsApp bot + dynamic PDF menu + reservations + CRM + Stripe - 3 training sessions for the manager or operator - 4 weeks of support Operating cost: $200 to $400 USD/month pass-through. No monthly licenses. No conversation caps. ## 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 (4 hours of wasted operations per day) 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, the bot pays for itself within 2 months in operational time savings alone. - [MAGIA / Solo](https://catalizadora.ai/magia/solo) for an independent restaurant or 1 to 3 locations - [MAGIA / Core](https://catalizadora.ai/magia/core) for a restaurant group with 4 to 30 locations and fragmented operations 30-minute call with the team that actually builds it — not with an SDR. ## Preguntas frecuentes ### How does the bot send an updated PDF menu over WhatsApp? The PDF menu is uploaded to your own storage (Supabase or S3) and the bot sends a signed link or attachment. When you update the PDF, every new customer automatically receives the current version. Zero outdated copies. ### How much does the bot cost for a CDMX restaurant? MAGIA / Solo delivers everything in 15 days for $4,500 USD: WhatsApp bot, dynamic PDF menu, reservation system, CRM with returning customers, and Stripe payment gateway. Operational from $200 USD/month. ### Can the bot take reservations and notify customers when a table is available? Yes. The bot checks your calendar in real time, proposes available time slots, confirms the reservation, and sends a reminder 2 hours before. If no table is available, it automatically offers a waitlist option. ### Can I still send voice messages to regular customers? Yes. The bot handles what's automatable (menu, reservations, location, hours) while your restaurant team maintains personal voice contact when it makes sense. A frictionless hybrid model. ### Does it work if I have multiple locations in CDMX? Yes. The bot identifies each customer by phone number, asks for their preferred location (Polanco, Condesa, Roma), and from there manages the menus, reservations, and calendar specific to that location. --- Source: https://catalizadora.ai/blog/bot-whatsapp-business-para-restaurante-cdmx-con-menu-pdf-en Author: Pablo Estrada — AI Catalyst, LLC (catalizadora.ai)