Reservations and table management

One diary for Google, Instagram and third-party bookings

Bring Google, Instagram, platform, phone and email bookings into one diary, stop double entry and see which channel brings which guests.

Ava research teamPublished 7 min read

On this page
  1. The problem with many doors
  2. Where guests look before they book
  3. Map your channels first
  4. Choosing the hub
  5. Connecting each channel
  6. Tag the source of every booking
  7. Reading channel data each month
  8. One diary, fewer logins to lose
  9. When a channel will not sync
  10. Walk-ins belong in the diary too
  11. Who owns the diary
  12. Frequently asked questions
  13. References

Key takeaways

  • Every booking channel should write into one live diary. If a channel cannot, close it or give it a single owner.
  • Tag every booking with its source so you can see which channels bring guests who turn up and come back.
  • Choose tools that connect easily: ease of integration and use is the factor hospitality businesses cite most often when deciding on AI[1].
  • More connected channels mean more logins to protect: only 25% of food and hospitality businesses had sought external cyber guidance[2].

The problem with many doors

A typical restaurant or pub now takes bookings through five or six doors: the website widget, Google, Instagram, one or two booking platforms, the phone, email and the occasional message on Facebook. Each door is useful. Together they create the classic failure: a booking taken in one place that the host stand cannot see, or the same table sold twice.

The fix is not fewer channels; guests use the one in front of them. It is one diary that every channel writes into, with a clear rule for any channel that cannot. The diary becomes the single source of truth for tables, notes and guest history, and everything else is a way in.

Where guests look before they book

Your own website remains one of the main places guests check before choosing you, and apps carry weight too. In the Food Standards Agency’s 2025 survey, of consumers who knew the hygiene rating scheme, 44% had come across a rating on a food business’s own website and 26% on a food ordering or delivery app[3]. The lesson for bookings is simple: wherever guests are already looking, the Book button should lead to the same diary, with the same tables, the same policy and the same confirmation.

That also means keeping the basics right across every profile: opening hours, the phone number, the booking link and any special hours for bank holidays. A guest who books through Google for a time you are closed is a double problem, a lost booking and a bad first impression.

Map your channels first

Example channel map for a restaurant or pub
ChannelHow bookings usually arriveTypical riskFix
Website widgetDirect into the booking systemOld widget left on a second pageOne widget, one link, everywhere
Google Business ProfileReserve button via a connected partnerButton linked to a platform you no longer useCheck the partner link quarterly
InstagramBook button or messagesBookings made in direct messagesUse the Book button; reply to messages with the link
Third-party platformsSynced or emailed to the venueSync failures and separate availabilityShare one availability pool
PhoneTyped in by staffPads and memory during serviceStraight into the diary, read back, confirm
Email and social messagesTyped in by whoever reads themUnread inboxes and slow repliesOne owner, checked twice a day

Make the map for your own venue by booking a table through each channel yourself. Note where each booking ends up, how long it takes to appear in the diary and whether the guest gets a confirmation. Most venues find at least one door that nobody knew was still open.

Choosing the hub

The hub is the booking system that holds the master diary. Choose it for how well it connects to the channels you use, not for the longest feature list. Hospitality businesses say the same about new technology generally: among accommodation and food businesses using or unsure about AI, ease of integration and use was the factor most often influencing adoption, at 25.5%[1]. Many in the sector start with free-to-use software rather than purchased tools[4], which is fine as long as it connects.

  • Does it connect directly to Google’s booking button and to the platforms you rely on?
  • Does it share one pool of tables across channels, rather than separate allocations?
  • Can it tag the source of every booking automatically?
  • Does it hold guest profiles that merge bookings from different channels?
  • Can staff on the floor see and change it on a tablet during service?
  • Can you export your data if you leave?

Connecting each channel

  1. Website

    Replace every booking link and old widget with one current widget. Check the menu page, the contact page and any event pages.

  2. Google

    In your Business Profile, check which partner the Reserve button uses and that it writes into your hub. Remove links to platforms you have left.

  3. Instagram and Facebook

    Add the Book button linked to your hub. Save a quick reply for messages that ask for a table, with the booking link.

  4. Platforms

    Connect each platform to the hub with shared availability. If a platform cannot sync, give it a small fixed allocation and check it daily.

  5. Phone

    Staff enter phone bookings straight into the hub, read them back and trigger the standard confirmation.

  6. Email and messages

    Name one owner who checks them at set times, enters bookings in the hub and replies with the confirmation.

Tag the source of every booking

Once everything lands in one place, the diary can tell you which channels work. Tag each booking with where it came from. Most systems do this for online channels automatically; for phone, email and messages, staff choose a source when they enter the booking.

  • Source codes to use: WEB, GOOGLE, INSTA, PLATFORM (named), PHONE, EMAIL, WALK-IN, EVENT.
  • Add a “how did you hear about us” question for first-time guests only.
  • For platforms that charge per cover, record the cover count so you can compare cost per channel.
  • Keep the source on the guest profile so you can see where regulars first found you.

Reading channel data each month

Example. A fictional 80-cover restaurant reviews a month of bookings by source. Its own website brings the most covers and the most returning guests. One booking platform brings many first-time guests, but a higher share of no-shows and few second visits. Phone bookings are fewer but larger, mostly groups and older regulars. Instagram brings few bookings directly, but a lot of website visits that week after each post.

From this, the restaurant keeps the platform for discovery, makes sure first-time platform guests get a good welcome and a reason to book direct next time, protects phone answering at peak times for larger groups, and stops treating Instagram as a booking channel and starts treating it as an advertising one.

Look at five numbers per channel: bookings, covers, recorded no-show rate, share of guests who return within six months and any per-cover cost. Those five tell you more than any dashboard.

One diary, fewer logins to lose

Every connected channel is another account with access to your guests’ names, numbers and visit history. Hospitality is not well defended. In the 2025 cyber survey, only 25% of food or hospitality businesses had sought external cyber security information or guidance, against 42% of businesses overall[2].

Businesses that sought external cyber security guidance (2025)
Businesses that sought external cyber security guidance (2025)Comparison. Food or hospitality: 25%; All businesses: 42%.25%Food or hospitalityFood or hospitality: 25%42%All businessesAll businesses: 42%Businesses that sought external cyber security guidance (2025)Comparison. Food or hospitality: 25%; All businesses: 42%.25%Food or hospitalityFood or hospitality: 25%42%All businessesAll businesses: 42%

Source: Department for Science, Innovation and Technology, 2025[2]

Show the data
ItemValue
Food or hospitality25%
All businesses42%
  • List every account that can see or change bookings, and who holds the login.
  • Use individual logins rather than one shared password at the host stand.
  • Turn on two-step sign-in wherever it is offered.
  • Remove access for leavers the day they go, including on platforms and social accounts.

When a channel will not sync

Sometimes a channel cannot connect, or a sync fails on a Saturday afternoon. Decide in advance what happens, so staff are not improvising. The simplest rule: any booking that does not appear in the hub within ten minutes is entered by hand by the diary owner, who then checks for clashes. If a platform keeps failing, cap its allocation to tables you can afford to lose, or switch it off until it is fixed. A channel that creates double bookings costs more than the covers it brings.

Walk-ins belong in the diary too

A diary that only holds bookings gives a partial picture of the evening. Seat walk-ins through the same system, even with a name like “Walk-in 4”, so table status is accurate and turn times are measured. It also lets you see how many covers come through the door unbooked, which matters when you decide how many tables to hold back. If a walk-in becomes a regular, their profile already has history.

Who owns the diary

Technology does half the job. The other half is a person. Name a diary owner for each shift, responsible for checking that every channel has synced, that notes are clear and that any manual entries are done. Give them the authority to close a channel for the evening if it misbehaves, and the job of reporting channel numbers each month. Venues that run one diary well tend to have someone who cares about it; venues with chaotic diaries usually have everyone responsible and nobody in charge.

  • Opening check: bookings on each channel match the diary.
  • During service: only the owner moves tables or overrides limits.
  • Close: manual entries done, notes tidied, issues logged.
  • Monthly: source report and a review of any channel causing errors.

Frequently asked questions

Can Google and Instagram bookings go into my own booking system?

Usually yes, through booking partners that connect to Google’s reserve button and Instagram’s Book button. Check that each button links to the system holding your master diary.

How do I stop double bookings from several platforms?

Use one hub with a shared pool of tables. If a platform cannot sync, give it a small fixed allocation and check it before every service.

How can I tell which booking channel is best?

Tag every booking with its source and compare bookings, covers, no-shows, return visits and any per-cover cost each month.

Should we still take bookings by email and social messages?

Yes, but give them one owner who enters them in the main diary at set times, and reply with your booking link where you can.

References

  1. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 165 dataset (AI sheets) (opens in a new tab) ↑

  2. Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  3. Food Standards Agency (2025). Food Hygiene Rating Scheme (FHRS) Food and You 2 report: wave 11 (opens in a new tab) ↑

  4. Office for National Statistics (2026). Artificial intelligence in UK businesses: 2023 to 2026 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo