WhatsApp for Restaurants — Reservations, Menus and Guest Messages

The host’s personal phone is the booking line. Offers go out from unofficial tools. Night messages vanish before lunch service.

Wapikon does not seat tables, print tickets, or replace your POS.

Session chat for tonight’s availability (confirmed by staff). Utility templates for reminders if you use them. Marketing templates only to guests who opted in.

Flow Builder can collect date, time, and party size, then hand to the host. Shared inbox covers host and manager. AI can answer published hours and allergy-policy text you provide — not invent the kitchen’s yes.

Click-to-WhatsApp from ads or the site. Instagram DMs can share the same product inbox when Instagram is connected.

Ask party size, time, and occasion in a flow. Large events should go to a human immediately.

Reminder templates before a booking you have already confirmed. After-hours flow sets expectations until the host is back.

Allergies, accessibility, and complaints belong with a manager in the inbox, not a looping menu.

Opted-in guests can receive a weekend-hours or tasting-menu template. Do not buy “foodie” number lists.

Host and duty manager share one official number with notes. That is enough CRM for most dining rooms; HubSpot is optional.

Knowledge: hours, location, published menu notes. Human takeover for allergies, private dining, and anything the kitchen must confirm.