Phones and call handling

Collecting phone numbers on bookings: why and how

Why a guest's mobile number cuts no-shows and day-of problems, and how to ask for it, explain it and store it lawfully under UK GDPR and PECR.

Ava research teamPublished 7 min read

On this page
  1. What the number is actually for
  2. Ask at the right moment, in the right words
  3. The legal basics in plain terms
  4. Marketing texts are a separate question
  5. Keep the numbers safe
  6. Decide how long you keep them
  7. Example: rewriting a booking form
  8. Checklist
  9. Frequently asked questions
  10. References

Key takeaways

  • A mobile number lets you remind, reschedule and rescue a booking on the day; an email address alone often arrives too late to help.
  • Service messages about a booking and marketing messages are different: marketing texts need consent or a valid soft opt-in under PECR.
  • UK GDPR expects you to tell guests why you want the number at the moment you collect it, in plain words.
  • Limit who can see guest numbers, keep them out of paper diaries on the bar and delete them on a fixed schedule.

What the number is actually for

Most booking systems ask for a phone number by default, and most venues never think about why. It is worth thinking about, because the reason you collect a number decides what you are allowed to do with it and what you need to tell the guest.

For a restaurant or pub, a guest's mobile does a handful of practical jobs that an email address does badly, because email is checked hours later while a text or call reaches someone who is already on their way.

  • Reminding the guest the day before, which gives them an easy moment to cancel and lets you resell the table.
  • Calling a party that is twenty minutes late before you release the table.
  • Warning guests about a problem on the day: a kitchen fault, a power cut, a flooded cellar or a road closure.
  • Confirming the details of a large party, such as pre-orders, a deposit or dietary needs across the group.
  • Returning lost property, or following up a complaint the guest raised after leaving.

Write these purposes down. They become the basis of your privacy wording, your staff script and your decisions about who may use the number later.

Ask at the right moment, in the right words

Guests give a number more readily when they can see why it is needed. On an online form, put a short line beside the field rather than relying on a privacy link at the bottom of the page. On the phone, say why before you ask.

  1. Online form

    Label the field Mobile number, with the hint: So we can text a reminder and contact you on the day if anything changes. Make it required only if you will genuinely use it.

  2. Phone bookings

    Say: Can I take a mobile number in case we need to reach you on the day? Read it back in pairs of digits, because a single wrong digit makes the number useless.

  3. Walk-in waitlist

    Ask only if you will text when the table is ready, and say so: If you leave a mobile, we will text you when your table is free.

  4. Large parties

    Ask for the organiser's mobile and, for parties above your set size, a second contact in case the organiser is unreachable.

Keep the marketing question separate from the booking question, both on screen and on the phone. A guest who is happy to receive a reminder may not want your newsletter, and running the two together is where most venues go wrong.

UK GDPR says that when you collect personal data from someone, you must give them certain information at the time you obtain it[1]. That includes who you are, how to contact you, why you are processing the data and on what legal basis, and who will receive it[1]. For a booking this does not need to be long. It needs to be clear and easy to find at the point of collection.

Matching each use of a guest's number to a lawful basis and a plain explanation
PurposeUsual lawful basis to considerWhat to tell the guest
Reminders and day-of contact about this bookingNecessary to deliver the booking the guest asked for, or legitimate interestsWe use your number to confirm and manage your booking
Large-party arrangements and depositsNecessary to deliver the bookingWe may call to confirm numbers, menus and deposit terms
Following up a complaintLegitimate interestsWe may contact you about feedback you have given us
Offers, events and newsletters by textConsent, or the soft opt-in where it appliesOnly if you tick to receive offers; you can opt out at any time

This is general guidance, not legal advice. If your venue does anything unusual with guest data, such as sharing it across a group of brands, take advice and record your reasoning.

Marketing texts are a separate question

Under the Privacy and Electronic Communications Regulations, marketing emails and texts to individuals need their prior consent[2]. Consent under UK GDPR means a freely given, specific, informed and unambiguous indication, given by a statement or a clear affirmative action[3]. A box that is already ticked, or a line buried in the booking terms, does not meet that standard.

There is one exception that matters to hospitality. The soft opt-in lets a business market its own similar products by email or text to customers whose details it obtained during a sale or negotiation[4]. For it to apply, the guest must have been given a simple way to refuse at the point of collection and in every message after that. If you rely on it, add an unticked Do not send me offers option to the booking form and put an opt-out in every text.

A rule of thumb for the team: anything about the guest's own booking is a service message; anything about a different visit, a new menu or an event is marketing.

Keep the numbers safe

A booking diary is a list of names, numbers and dates, which makes it worth protecting. In the government's 2025 cyber security survey, 30% of food or hospitality businesses had identified a cyber breach or attack in the previous 12 months, against 43% of businesses overall[5]. A lower figure is not a reason to relax: smaller businesses often notice fewer incidents rather than suffer fewer.

Businesses that identified a cyber breach or attack in the last 12 monthsUK, 2025
Businesses that identified a cyber breach or attack in the last 12 monthsComparison. Food or hospitality: 30%; All businesses: 43%.30%Food or hospitalityFood or hospitality: 30%43%All businessesAll businesses: 43%Businesses that identified a cyber breach or attack in the last 12 monthsComparison. Food or hospitality: 30%; All businesses: 43%.30%Food or hospitalityFood or hospitality: 30%43%All businessesAll businesses: 43%

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

Show the data
ItemValue
Food or hospitality30%
All businesses43%
  • Give each staff member their own login to the booking system, and remove leavers on their last day.
  • Restrict exports of the guest list to the owner or general manager.
  • Do not keep a paper diary with guest numbers open on the bar, or photograph booking sheets on personal phones.
  • Call guests from the venue's phone or the booking system, not from staff members' personal mobiles.
  • Turn on two-step sign-in for the booking system and the email account linked to it.

Decide how long you keep them

UK GDPR does not set a number of months for guest data, but it does expect you to keep personal data no longer than you need it and to be able to explain your choice. Set a period, write it in your privacy notice and switch on automatic deletion or anonymisation in your booking system if it offers one.

A sensible starting point is to keep contact details for as long as you need them to manage the booking and handle any follow-up, then remove them. Marketing lists are different: keep a record of when and how each person opted in, and remove them when they opt out. If your booking provider holds the data for you, check what its settings do and whether you or the provider decides. The same questions apply to any phone assistant that takes details for you; see what separates a basic AI receptionist from an AI employee.

Example: rewriting a booking form

Example: The Larder, a fictional neighbourhood bistro, had a booking form with a required phone field, a pre-ticked Keep me updated box and a privacy link in grey text at the foot of the page. Guests often typed 00000 into the phone field, and the bistro could not tell who had actually agreed to marketing.

Example: the owner changed three things. The phone field now reads Mobile number, so we can remind you and reach you on the day. The marketing box is unticked and reads Send me occasional news and offers by email or text. A two-line note under the button says who the bistro is, what the details are used for, how long they are kept and links to the full privacy notice. Fake numbers dropped away, reminders reached guests, and the marketing list became smaller but trustworthy.

Checklist

  1. List every purpose you use guest phone numbers for, and drop any you cannot justify.
  2. Add a one-line reason beside the phone field and in the phone script.
  3. Separate the marketing question from the booking question, unticked by default.
  4. Put a short privacy note at the point of collection, linked to the full notice.
  5. Give staff individual logins and limit exports.
  6. Set a retention period and switch on deletion where your system allows.
  7. Brief the team on the difference between a service message and marketing.

Done well, collecting numbers is a small courtesy rather than a data grab. Guests understand why a restaurant wants to reach them about their own table, and most will happily give a number once you have told them why. Those same numbers also matter when you think about refusing repeat no-shows, because you can only spot a pattern if the contact details are real.

Frequently asked questions

Can we make a phone number compulsory for bookings?

Yes, if you genuinely need it to manage the booking, for example to send reminders or reach the guest on the day. Tell guests why it is required. Do not make it compulsory just to grow a marketing list.

Do we need consent to send a booking reminder by text?

A reminder about the guest's own booking is a service message rather than marketing, so it does not need marketing consent. Keep it free of offers; adding a promotion turns it into marketing.

Can we text guests about a last-minute free table?

Only if they have agreed to receive offers, or the soft opt-in applies and they were given the chance to refuse. A waitlist text to a guest who asked to be told when a table is free is different, because it is the service they requested.

A guest asked us to delete their details. What do we do?

Remove their contact details from the booking system and any marketing lists, unless you need to keep something for a specific reason such as an open dispute, and confirm to the guest what you have done.

References

  1. legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 13: Information to be provided where personal data are collected from the data subject (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 4: Definitions (opens in a new tab) ↑

  4. legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22(3) soft opt-in (opens in a new tab) ↑

  5. Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (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