CRM and automation
Automatic data sync: one source of truth for restaurants
How a restaurant keeps bookings, guests and messages in sync without double entry: what to connect, in what order, and which mistakes create duplicates.

In a restaurant, guest data lives in four or five places: the booking app, the reception phone, Messenger, the birthdays spreadsheet the manager once made, and the till. The same guest exists in all of them, spelled differently. Automatic data sync is not a technology problem. It is the decision that one system is the source of truth and the others feed into it.
Put simply, automatic data sync means every booking, message and consent ends up on its own in one guest record, without anyone typing it again. For a restaurant this is done with a CRM as the central system and two or three workflows feeding it from the booking app and the messaging channels. The rest of this article explains the order, the settings and the mistakes we see most often.
Choose your source of truth
For a restaurant, the logical choice is the CRM: that is where the guest record lives, with phone number, visits, preferences and consent. The booking app sends every new booking to the CRM. Messenger and WhatsApp go into the same inbox. The till, if it allows it, sends the bill amount for the visit. Nobody types the same guest twice.
The phone number is the key
Duplicate records are created when the system matches by name. There are many "John Smith" entries, and just as many "Jon Smith" and "J. Smith". A mobile number is unique. Every sync workflow should first search for the phone number in one standard format (+44 followed by the number without the leading 0) and only create a new record if it does not find it. That one setting avoids 90% of the problems.
What you sync, in order
- Bookings into the CRM. Date, party size, notes. This is where the volume is.
- Messages into one inbox. Messenger, Instagram, WhatsApp, website form.
- Booking outcome. Came, did not come, cancelled. Without this you do not know who your good guests are.
- Consent. From the booking form to the record, with a date. If it is lost in the sync, you cannot lawfully send anything.
The till and the accounts come last, if ever. The value lies in the first four.
How n8n-style workflows work
An automation workflow is a simple sentence: "when X happens in system A, do Y in system B". When a new booking arrives, find or create the record, add the booking, schedule an SMS reminder. Workflows like these are built without code, but they need testing with real data: an empty phone field or a name with an apostrophe or accent is enough to break them. Make ten test bookings before you leave them to run on their own.
What your staff gain
Front of house sees on one record that the 21:00 table is a guest who comes every month, prefers the terrace and once cancelled without notice. That changes how you welcome them, and it does not require anyone to remember. That is what "one source of truth" means in practice.
Mistakes that create chaos
- Two-way sync. If the CRM writes back to the booking app and the app writes back to the CRM, you create loops. One direction per field.
- Importing the old spreadsheet without cleaning it. You bring in every duplicate from the last five years.
- Syncing without consent. Having a phone number from a booking does not mean you can send an offer.
- Nobody checks. Once a week, someone looks at the records created without a phone number.
Step by step: the first week
- Day 1, inventory. Write on one page where guest details live today: booking app, Messenger, WhatsApp, spreadsheet, till, the reception notebook. Next to each, who updates it.
- Day 2, clean the spreadsheet. One phone number format, remove rows without a phone number, mark who has genuinely given consent. Anyone without consent is imported as a plain record, with no marketing tag.
- Day 3, import into the CRM. Check 20 random records by hand before moving on.
- Day 4, connect bookings. One workflow: new booking, search by phone, create or update the record, log the booking. Test it with ten dummy bookings, including two with an apostrophe or accent in the name and one without a phone number.
- Day 5, messaging channels. Connect Messenger, Instagram and WhatsApp to the unified inbox. From now on, nobody replies from their personal phone.
- Days 6 and 7, observation. Let the system run over a weekend and check on Monday how many records were created without a phone number or twice.
A hypothetical example: a 60-cover restaurant
Take a hypothetical restaurant with 60 covers, open six days a week, with about 40 bookings a day in high season. Today front of house enters every phone booking into the app and, if there is time, into the spreadsheet. Bookings from Messenger are entered in the evening, as many as the manager remembers. Over a month that is about 1,000 bookings, and nobody knows how many belong to returning guests.
With sync, the same 1,000 bookings go into records automatically. If, hypothetically, 300 of them belong to 120 guests who came more than twice, the restaurant knows for the first time who those 120 are. We do not know in advance what it will do with that knowledge, or what it is worth. The point is that before, it did not have it at all. The numbers are illustrative and every restaurant will see its own.
What to measure in the first and third month
Do not measure revenue at the start. Measure whether the system is telling the truth. In the first month, three numbers from your own data:
- the share of bookings that reached the CRM without human intervention
- duplicate records found in the weekly check
- messages answered outside the unified inbox (ideally zero)
At three months, add: the share of bookings with a recorded outcome (came or did not come), the number of guests with two or more visits, and how many of them have consent to be contacted. Compare only with yourself. The "industry averages" that circulate rarely have a source.
When not to automate yet
If your booking app offers no export or integration, the workflow will need manual copying, and then the CRM just becomes one more place to enter data. Sort out the app first. Also, if your staff change every season and nobody will do the weekly check, the sync will pile up errors quietly. A small restaurant with 10 bookings a day and an owner who remembers their guests can wait. The cost of the chaos there is small.
With PandoraBot
Pandora CRM keeps contacts, conversations and sales in one place, with automation for follow-ups and reminders. See how it works and pricing, or start with a free scan of your website.
FAQs
Do I need a developer?
Not for the basic workflows, which are built without code. You do need someone to test them with real bookings before you trust them.
What do I do with the old guest spreadsheet?
Clean it first: one phone number format, duplicates removed, and a note of who has genuinely given consent. Then import it.
Should I connect the till as well?
Not at the start. Bookings, messages, booking outcome and consent deliver the value. The till is an optional extra.
How long does the initial setup take?
With a clean spreadsheet and a booking app that connects, one working week at a few hours a day, as in the plan above. Most of the time goes on cleaning, not on the workflows.
What if two guests share the same phone number?
It happens with couples and families. Keep one record per phone number with a note of the names. That is better than two records sharing the same history.



