Turn every table into a returning customer — automated WhatsApp follow-up for every dine-in visit

Yes — Beejek needs the diner's phone number to deliver the WhatsApp receipt. For dine-in, the phone number can be collected at reservation or at the table. For takeaway and delivery orders, it's typically already captured. Encouraging cashiers to collect phone numbers increases receipt delivery coverage.

Yes. Beejek processes any POS transaction where a phone number is attached — dine-in, takeaway, and delivery all trigger the same WhatsApp receipt and automation sequence.

Yes. Beejek supports multiple locations under one account. Each location can have its own Google review link, its own branding, and its own analytics. Multi-location restaurant groups see per-venue NPS and retention data in a single dashboard.

Yes. Each Beejek store is configured with its own Google Business Profile review link. Diners from a specific location are sent to that location's Google listing.

Yes. NPS scores are timestamped and visible in the Beejek dashboard. A restaurant that consistently gets lower NPS on Friday evenings can identify the pattern — and investigate kitchen capacity, service speed, or staffing before it compounds.

Beejek's templates are per-merchant — one language is configured per store. For multi-language audiences, Arabic and English templates can both be submitted and the routing set per merchant account. Contact the Beejek team for multi-language configuration.

Beejek only sends messages when a phone number is captured. Cash diners who don't provide a number are not contacted. Encouraging cashiers to collect phone numbers — even for cash transactions — increases your reachable customer base over time.

Smart Reminder templates are pre-approved by Meta and send from fixed template content — they can't dynamically reference a specific order. The message is warm and personalised with the customer's name, but doesn't include order history details.