All your guest data, shared by your team.
Preferences, allergies, history, occasions: every guest becomes a profile that fills itself in, booking after booking, service after service. And everyone has access.
- Apr 12, 20264 covers · terrace
- Feb 28, 20262 covers · birthday
- Jan 10, 20266 covers · work lunch
Always orders the same wine. Likes to be seated away from the kitchen.
Everything a profile remembers for you.
Contact & channel
Name, contact, and where the booking came from: site, Google, WhatsApp, phone.
Preferences & allergies
Favourite table, diet, wine, intolerances. What you need before they arrive.
Visit history
Every visit, its service, its party size. You spot a regular instantly.
Occasions
Birthdays, dates that matter. Enough to mark the moment at the right time.
Tags & segments
VIP, big spender, noise-sensitive… Tag once, find them all.
Team notes
A note added by one server stays visible to the whole team at the next service.
Tag once. Find them all.
A guest tagged "gluten-free"? Find them all in one click to announce a new menu. "Not in for 3 months"? One targeted nudge, and they're back.
Before centralising guest data
Can I enrich profiles during service?
Yes. Notes, tags (VIP, allergies), preferences: data builds up progressively and stays accessible to the whole team.
What's the point if I don't do marketing?
Even without campaigns, the CRM improves service: recognition, personalisation, consistency, which drives repeat visits and reviews.
How do we avoid a "messy" database (duplicates, missing info)?
We centralise the sources (phone + online) and apply simple rules. The goal is useful data, not perfect data.
Does it work across several venues?
Yes. You standardise tags and share a consistent guest view across venues, while keeping rules specific to each.
Bring your whole room onto EatNow.
Reservations, deposits, WhatsApp confirmations, CRM, reporting — one single system. Human support, in French and English, from people who've worked service.