Technology, data and AI

Automating booking enquiries across phone, web and chat

Build one booking enquiry flow for phone, web form, chat and email: the fields to capture, routing rules, what stays with staff, and an Example Saturday.

Ava research teamPublished 7 min read

On this page
  1. Why enquiries leak between channels
  2. Step 1: define one enquiry record
  3. Step 2: set routing rules
  4. Step 3: connect each channel to the record
  5. Step 4: write the acknowledgements
  6. Example: one Saturday, five channels
  7. Setup mistakes that undo the work
  8. Step 5: measure it weekly
  9. Frequently asked questions
  10. References

Key takeaways

  • Treat every enquiry, whatever the channel, as one record with the same fields, owner and status.
  • Automate the capture and the acknowledgement; keep confirmation of tricky bookings, allergen answers and complaints with a person.
  • Evening and late-night demand is when staff are busiest and enquiries are most likely to be missed.
  • Measure response time and the share of enquiries that become confirmed bookings, by channel, every week.

Why enquiries leak between channels

A typical venue receives booking enquiries in five places: the phone, a web form, a booking widget, website chat and social media messages, plus the odd email to a personal inbox. Each channel has its own owner, or none. The result is familiar: a party of 14 asks about Saturday on Instagram, the same guest emails two days later, and nobody knows which reply went out.

The pressure peaks when the team has least time. Restaurants, cafés, bars and nightclubs took 42% of time-stamped consumer spending between 6pm and 6am in an ONS sample week, ahead of groceries at 22%[1], and night-time spending was a third of all time-stamped spending in that week[2]. Those are the hours when the person who should answer the phone is also running the floor. Many guests also plan around shifts: in 2022, 4% of the UK workforce usually worked evenings or nights but not days, and 23% worked both[3], so enquiries arrive late in the evening and early in the morning, outside the hours when most venues answer messages.

Who takes the night-time spend: share of time-stamped spending, 6pm to 6amONS sample week, November 2022. 'All other categories' is the remainder.
Who takes the night-time spend: share of time-stamped spending, 6pm to 6amDonut chart. Restaurants, cafés, bars and nightclubs: 42%; Groceries: 22%; All other categories: 36%.Restaurants, cafés, bars and nightclubs: 42%Groceries: 22%All other categories: 36%42%
  • Restaurants, cafés, bars and nightclubs 42%
  • Groceries 22%
  • All other categories 36%

Source: Office for National Statistics, 2022[1]

Show the data
ItemValue
Restaurants, cafés, bars and nightclubs42%
Groceries22%
All other categories36%

Step 1: define one enquiry record

Before you automate anything, agree the fields every enquiry must end up with, whichever channel it came from. If the phone, the form and the chat each ask different questions, you cannot compare or follow up.

A single enquiry record used across every channel.
FieldWhy it mattersRequired?
Name and contact number or emailNeeded to confirm or declineYes
Date, time and party sizeCore of the requestYes
Flexibility (earliest and latest time)Lets staff offer an alternative without another round of messagesRecommended
Occasion or enquiry typeSeparates a table for two from a private hireYes
Dietary or access needs flaggedA yes or no flag, with detail handled by a personYes
Channel and time receivedFor response-time trackingAutomatic
Owner and statusNew, offered, confirmed, declined, lostAutomatic
Marketing consentSeparate tick, never bundledOptional

Keep the dietary field as a flag. Detail about allergies is health information and the decision about whether the kitchen can cater safely belongs with trained staff. For food sold online or by phone, allergen information must also be available at two stages of the ordering process[4], which is easier to get right when one person owns the conversation.

Step 2: set routing rules

  1. Standard tables

    Up to your largest standard table, within opening hours: the booking system confirms instantly if there is availability, or the enquiry is saved for a person to confirm within your target time.

  2. Large parties

    Above the standard table size: always to the bookings or events lead, who checks the floor plan, deposit terms and set menu.

  3. Private hire and events

    Straight to the events owner with date, numbers, budget range and occasion captured, so the first reply can be a proposal rather than a list of questions.

  4. Dietary and access flags

    Any yes goes to the duty manager or chef for a personal reply before the booking is confirmed.

  5. Complaints and refunds

    Never automated. Routed to the general manager with the full conversation.

  6. Everything else

    Out-of-hours enquiries get an instant acknowledgement and join the morning queue.

Step 3: connect each channel to the record

Each channel needs a different kind of automation to feed the same record.

  • Phone: an assistant or call-handling service that answers when staff cannot, captures the fields above and passes urgent calls to a person. Ava, for example, takes booking requests and saves them for your team to confirm rather than promising a table.
  • Booking widget: the most automated channel. Check it writes dietary notes and occasion into the same fields you use elsewhere.
  • Web form: a short form with the same fields and an automatic acknowledgement that states when the guest will hear back.
  • Website chat: answers questions and collects the record. See what guests ask in website chat for the common topics.
  • Social messages: an auto-reply that points to the booking link or asks for the required fields, then a person picks it up.
  • Email: one shared bookings address, never a manager's personal inbox, with a rule that forwards to the same queue.

Guests are used to typing to automated assistants: six in ten UK adults had used an AI chatbot in the previous three months[5]. What irritates them is being asked the same questions twice, so the handover from automation to a person must carry the record with it.

Step 4: write the acknowledgements

An acknowledgement buys time without making a promise. Write one per enquiry type and keep the wording identical across channels.

Example acknowledgement: 'Thanks, we've got your request for 8 people on Saturday 12 December at 7.30pm. This isn't confirmed yet. Our bookings team will reply by 11am tomorrow. If you mentioned an allergy, our duty manager will contact you personally before we confirm.'

Do not add marketing to the acknowledgement unless the guest has opted in. Marketing emails and texts to individuals need prior consent under PECR[6]; a booking enquiry is a service message, and keeping it that way avoids muddling the two.

Example: one Saturday, five channels

Example. A fictional 90-cover bistro in Bristol logs its enquiries for one Saturday after setting up a single queue.

  1. 6.40pm, phone: a caller wants a table for 4 at 8pm. Staff are busy, so the call is answered automatically; the request is saved and the host confirms it from the queue at 6.55pm.
  2. 7.15pm, Instagram: a message about a 30th birthday for 16 in January. The auto-reply asks for date, numbers and budget; the events manager replies with a set menu proposal on Monday morning.
  3. 8.30pm, website chat: a guest asks if the kitchen can cater for a sesame allergy next Friday. The chat collects the booking request and flags it; the head chef calls back on Sunday.
  4. 10.50pm, web form: a request for Sunday lunch for 6. Acknowledged instantly; confirmed at 9.30am.
  5. 11.20pm, email: a complaint about slow service. Routed to the general manager, who replies personally.

None of the five was lost, and the only enquiry answered entirely by automation was the acknowledgement. People handled every decision.

Setup mistakes that undo the work

Most failed attempts at a single enquiry queue fail for the same handful of reasons. Check for these in the first month.

  • Two queues by stealth: the events manager keeps private hire in a personal inbox 'just for now'. Within weeks the shared view is missing the most valuable enquiries.
  • Acknowledgements that sound like confirmations. Words such as 'see you on Saturday' in an automatic reply create disputes when the table was never available.
  • No owner overnight. Enquiries that arrive after close need a named person who clears them first thing, with a fixed time such as 10am.
  • Different questions in every channel. If the web form asks for party size and the chat does not, staff have to go back to the guest, which is the delay you were trying to remove.
  • Free-text allergy notes copied into the booking system and printed on the floor plan for every server to read. Keep the flag visible and the detail with the manager and kitchen.
  • Nobody checks the numbers. If response times are not reviewed weekly, the queue drifts back into five separate habits.

A short weekly review with the bookings lead fixes most of these. Look at five random enquiries from different channels and follow each one from first message to outcome. Where it stalled, change the rule, the template or the owner, and note the change so the next review can see whether it worked.

Step 5: measure it weekly

  • Median time from enquiry to first human reply, by channel.
  • Share of enquiries that became confirmed bookings, by channel and enquiry type.
  • Enquiries with no owner after 24 hours (target: none).
  • Duplicate enquiries from the same guest across channels.
  • Calls that rang out or reached voicemail during service.

Before connecting a new tool to the queue, check the data protection side using the DPIA guide for guest tech, and agree with staff what they may paste into AI tools in your AI use policy. For the wider picture of what automation can remove from a manager's week, see what an AI employee can take off a manager's plate.

Frequently asked questions

Should every booking enquiry be confirmed automatically?

No. Standard tables within your rules can be, but large parties, private hire, dietary or access needs and anything unusual should be confirmed by a person who can check the floor and the kitchen.

What is a good response time for booking enquiries?

Set a target you can keep, such as within two hours during opening hours and by mid-morning for overnight enquiries, and state it in the acknowledgement so guests know what to expect.

Can I add guests who enquire to my mailing list?

Only with their consent, or under the soft opt-in where they have bought or negotiated with you and were given a clear chance to opt out. Keep the marketing tick separate from the booking request.

Do I need a separate system for private hire enquiries?

Not necessarily. What matters is that private hire enquiries land in the same queue with an owner, and that the record captures numbers, date, occasion and budget range.

References

  1. Office for National Statistics (2022). The night-time economy, UK: 2022 (opens in a new tab) ↑

  2. Office for National Statistics (2022). The night-time economy, UK: 2022 (opens in a new tab) ↑

  3. Office for National Statistics (2022). The night-time economy, UK: 2022 (opens in a new tab) ↑

  4. Food Standards Agency (2026). Allergen guidance for food businesses (opens in a new tab) ↑

  5. Department for Science, Innovation and Technology (2024). Public attitudes to data and AI: Tracker survey (Wave 4) report (opens in a new tab) ↑

  6. legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (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