Guest experience
Why guests no longer want to give their phone number to wait for a table
Guests are increasingly reluctant to share their phone number just to wait for a restaurant table. An anonymous app can improve the experience while making service easier for restaurants.

For years, the scene was always the same. A guest arrived at a full restaurant and the team asked for a phone number so they could call when a table became available.
Simple, fast and efficient. At least until recently.
Today, consumers pay much closer attention to their personal data. Giving a phone number for a twenty or thirty-minute wait no longer feels as harmless as it once did.
At the same time, smartphones have changed expectations. People will install a small app when it brings real value, provided it respects their privacy.
What is your phone number? We will call you when a table is available.
A phone number has become sensitive personal data
Ten years ago, sharing a phone number felt almost automatic.
Today, that number can often be linked to online accounts, consumption habits, marketing campaigns, commercial text messages or phishing attempts.
Even when a restaurant has no commercial intention at all, guests cannot know what will happen to their number. The result is simple: many now hesitate to share it.
Baymard Institute, a global reference in user experience, explains that many consumers abandon a process when they feel a phone number is requested without an obvious reason. Some even provide a fake number when the information seems unnecessary.
For a simple wait of a few dozen minutes, that reluctance is perfectly understandable.
GDPR changed expectations
Since GDPR came into force in Europe, consumers are much more aware of their rights.
They know that a business should only collect data that is strictly necessary to provide a service.
That awareness leads more guests to ask a very simple question: why do you need my number?
When there is no convincing answer, trust immediately decreases.
Installing an app no longer means sharing more data
Many people still assume that installing an app necessarily means handing over more personal information. In reality, it depends entirely on how the app is designed.
A modern app can work without an account, email address, phone number, permanent location tracking, contact access or photo access.
The CNIL reminds app publishers that mobile apps must follow the principle of data minimization and request only the permissions that are truly necessary.
In other words, a well-designed app can be more privacy-friendly than a simple reservation notebook.

The paradox: an app can be more anonymous than a paper notebook
A traditional reservation notebook usually contains a first name, last name, phone number and sometimes an email address.
By contrast, an app designed only to manage a waitlist can work with a fully anonymous technical identifier.
With WaitAway, no account is required. Guests do not need to provide their name, phone number or email address. The app does not request intrusive permissions.
The smartphone simply becomes a way to receive a notification when the table is getting close. This follows the Privacy by Design principle recommended by GDPR.
The limits of a simple phone call
A phone number essentially allows one thing: calling the guest.
In practice, this often forces staff to call several times, reach voicemail, try again a few minutes later, handle fake numbers or start over when the guest does not hear the phone.
Meanwhile, a table can remain unused for several minutes. When the restaurant is full, those minutes can represent lost covers during the evening.
An app transforms the waiting experience
An app does more than replace a phone call. It creates an interactive waiting experience.
With a traditional process, the guest has to stay nearby, cannot see progress, receives an approximate estimate and depends on a phone call.
With WaitAway, guests can move around freely, follow their position in real time, receive a recalculated estimate, get instant notifications and manage their own wait without giving their number.
Guests can also pause their wait voluntarily, then resume according to the rules defined by the restaurant. That flexibility is impossible to reproduce cleanly with a simple phone call.
Smarter estimates and notifications
A paper notebook cannot analyze anything. An app can learn from the restaurant’s real operation.
As services go by, WaitAway can analyze average table turnover times, variations by day, lunch and dinner differences and real observed wait times.
Estimates gradually become more reliable. Guests know what to expect and staff receive fewer repeated questions.
Notifications efficiently replace calls: your table is close, prepare to return, your table is ready, your return window is about to expire.
A better experience for everyone
For guests, the benefit is direct: more freedom, stronger privacy, less stressful waiting, visibility on progress and no personal data to share.
For restaurants, the benefit is operational: fewer calls, less wasted time, fewer errors, better table rotation and a more modern guest experience.
In tourist areas, where visitors often want to enjoy nearby shops while waiting, that difference matters even more.
Conclusion
The phone number was long the simplest way to manage a waitlist. But consumer expectations have changed.
Guests now want more transparency, more control over their personal data and a smoother experience.
An app designed from the start to respect privacy answers those expectations while offering features that a simple call cannot provide: notifications, real-time progress, smart estimates, dynamic queue management and freedom to move around.
The real question is no longer: what is your phone number? It is: why ask for it when a simpler, more modern and more privacy-friendly solution exists?
References
- Baymard Institute. Phone Number UX: Always Explain Why the Phone Number Field Is Required.
- CNIL. Mobile app permissions: recommendations to respect privacy.
- General Data Protection Regulation (GDPR) - Regulation (EU) 2016/679.
- Harborth, D., & Pape, S. (2018). Investigating privacy concerns related to mobile app installation decisions.
- Wang, T., Duong, T., & Chen, C. (2016). Intention to disclose personal information via mobile applications.
- Google Android Developers. Permissions overview.
