---
title: "Salon waiting lists: offering and confirming appointments · Lyntev"
description: "Organise preferences, offers, deadlines and appointment confirmations in your salon. Includes statuses, competing replies and a practical waiting-list worksheet."
url: "https://lyntev.com/en/guides/manage-salon-waiting-list"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. How to manage a salon waiting list and fill available appointments fairly

# How to manage a salon waiting list and fill available appointments fairly

A useful waiting list brings together requests that could fill a specific appointment slot. It needs the service, duration, acceptable professionals, availability and a clear way to confirm. This guide helps you turn a list of names into an offer and booking routine that your team can explain and check.

By [Lyntev](<https://lyntev.com/en/company>). Updated on 20 November 2026.
About 5 minutes to read.

[Start reading](<https://lyntev.com/en/guides/manage-salon-waiting-list#leitura>)[Download worksheet](<https://lyntev.com/recursos/en/gerir-lista-espera-salao.txt>)

**One opening, one confirmation**Illustrative schedule: a waiting-list invitation still needs a reply and confirmation.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/gerir-lista-espera-salao>); source revision 20 November 2026.

By the end, you can:

- Collect enough preferences without collecting too much
- Handle offers and competing replies
- Check filled appointments and closed requests

In this guide

1. [Describe the request before ordering the list](<https://lyntev.com/en/guides/manage-salon-waiting-list#pedido-compativel>)
2. [Choose an understandable order and handle incompatible requests](<https://lyntev.com/en/guides/manage-salon-waiting-list#regra-de-ordem>)
3. [Separate active requests, offers and confirmations](<https://lyntev.com/en/guides/manage-salon-waiting-list#estados-de-oferta>)
4. [Test two people replying to the same opportunity](<https://lyntev.com/en/guides/manage-salon-waiting-list#duas-respostas>)
5. [Keep the list current without turning preferences into commitments](<https://lyntev.com/en/guides/manage-salon-waiting-list#prazo-e-manutencao>)
6. [Assess compatibility and appointments actually filled](<https://lyntev.com/en/guides/manage-salon-waiting-list#medir-recuperacao>)
7. [Document the rule and test the journey in your chosen system](<https://lyntev.com/en/guides/manage-salon-waiting-list#ficha-lista>)
8. [Sources and criteria](<https://lyntev.com/en/guides/manage-salon-waiting-list#fontes>)

## Describe the request before ordering the list

Record the service required, the time needed, possible dates and the professionals the person is willing to see. Distinguish “any afternoon” from “Friday after 17:00”. Also record the minimum notice they need to get there. These details let you match a real appointment slot without repeatedly contacting people for whom it would never be useful.

Avoid lengthy notes about the client’s personal life. A time preference is enough when the purpose is to organise availability. Confirm the contact channel and explain what the list is for. Joining it does not guarantee an appointment or provide general permission for advertising. The European Commission recommends limiting data to its purpose; apply that rule to the small record your reception team actually needs.

## Choose an understandable order and handle incompatible requests

You can order compatible requests by the date they were added and set operational priorities that you can justify. The team should know the rule so that nobody promises preferential treatment without authorisation. Do not order requests by name or phone number alone: first check compatibility with the service, professional, location and available resources.

Fictional example: a sixty-minute appointment becomes available on Tuesday morning. The first request on the list needs ninety minutes; the second only accepts another professional; the third is compatible. Contacting the third person does not mean letting someone jump a queue of equivalent requests. Record the reason for the selection and keep the first two requests active for a suitable appointment. This lets you explain the decision without revealing other clients’ data.

Choose an understandable order and handle incompatible requests

| Fictional request | Condition | Decision for this appointment |
| --- | --- | --- |
| E-01 | Needs 90 minutes | Does not fit a 60-minute slot |
| E-02 | Only accepts a professional who is unavailable | Keep on the waiting list |
| E-03 | Compatible service and time | Can receive an offer |
| E-04 | Can only attend with 24 hours’ notice | Check the notice period |

## Separate active requests, offers and confirmations

Use statuses that correspond to verifiable events: active request, offer sent, reply received, booking confirmed and request closed. If you temporarily hold the appointment, record when the hold expires and what the client sees. Square’s documentation distinguishes waiting-list requests from contact about an opening; this separation avoids treating a message as a reservation.

Define who updates each status and how work resumes after an interruption. If a receptionist makes an offer by phone, another team member needs to be able to see that it is being handled. When the person replies through another channel, link the reply to the same request. Creating a second entry for the same offer increases the risk of confirming twice or continuing to send notices after closure.

## Test two people replying to the same opportunity

Choose whether to offer the appointment to one person at a time or use an offer where the first valid confirmation takes priority. If you contact people simultaneously, explain the rule and check the calendar again before confirming. The button, message or telephone reply must lead to the same operational decision.

In a fictional test, two people accept at 15:00 an appointment starting at 17:00. Reception confirms just one booking in the main system and tells the other person that the opportunity has been filled, keeping their waiting preference if they wish. Acceptance criteria: one valid booking, no duplicate charge, understandable replies and enough history to explain the outcome.

## Keep the list current without turning preferences into commitments

Someone may no longer need the service or may change their availability. Define when the team reviews old requests and how an entry is closed at the client’s request. Do not choose a retention period for technical convenience: relate it to the purpose and the salon’s data policy. The record should make the latest update identifiable.

When an offer expires, release any temporary hold according to the rule communicated and check the calendar again. Do not automatically send the next offer using an outdated snapshot of availability. If the salon withdraws the opening, notify those who received it and close the pending status. Someone must remain responsible for maintaining the list, even when software prepares or sends notifications.

## Assess compatibility and appointments actually filled

Track appointments offered, replies, confirmations and services delivered. Count incompatible offers and requests that were no longer active separately. A large number of notices may indicate poor selection. The fill rate should state its denominator: appointment slots eligible for the waiting list, rather than every salon booking.

In the fictional scenario, ten slots are considered, seven have at least one compatible request and four result in a service being delivered. You can report four recovered services out of seven compatible slots, while also explaining the ten initial opportunities. Do not add the duration of overlapping slots as if they were independent capacity. Compare the routine with the time reception spends on it and with cases where a promise had to be corrected.

## Document the rule and test the journey in your chosen system

Prepare three fictional incompatible requests and two compatible ones before configuring automation. Run through entry, offer, rejection, expiry, confirmation and closure. Check team access and the content shown to the client. Only approve the process when the active record matches the calendar and repeating a reply does not create another booking.

BeautyFlow IA has a waiting list and appointment offers; check the criteria and messages in a demonstration of the version you will use. If your process needs special priorities or deadlines, treat them as requirements to verify. A waiting-list menu item does not prove that every rule in this guide is automated. The worksheet below lets you compare observed behaviour with what you need.

### Worksheet for your project

```
Waiting-list rule
Requested service, duration and location:
Acceptable professionals and required resources:
Availability windows and minimum notice:
Contact channel and purpose:
Order among compatible requests:
Individual or simultaneous offer and conditions communicated:
Temporary hold, start and end:
Statuses and responsibility for each change:
Late reply, rejection and withdrawn opening:
Condition ensuring a single confirmed booking:
Review, closure and retention of requests:
Test with two replies and observed result:
```

- [Prepare general appointment-booking rules](<https://lyntev.com/en/guides/organise-online-appointments-resource-conflicts>)

## Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

- [Square — Set up and manage your appointments waitlist](<https://js.squareup.com/help/us/en/article/7923-waitlist-with-square-appointments>)
- [Odoo 19 — Appointments: duração, recursos e cancelamentos](<https://www.odoo.com/documentation/19.0/applications/productivity/appointments.html>)
- [Comissão Europeia — Principles of the GDPR](<https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/principles-gdpr_en>)

## Continue to your next decision.

- [Reduce no-shows with a verifiable routine](<https://lyntev.com/en/guides/reduce-salon-no-shows>)
- [Define team access](<https://lyntev.com/en/guides/define-team-permissions>)
- [Explore BeautyFlow IA](<https://lyntev.com/en/salon-management-software>)

This guide is part of [Organise work in your salon.](<https://lyntev.com/en/guides#gestao-saloes>)

- [How to reduce salon no-shows without putting clients off](<https://lyntev.com/en/guides/reduce-salon-no-shows>)
- [How to organise colouring times, professionals and washbasins in a salon](<https://lyntev.com/en/guides/organise-salon-colouring-times-resources>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Put this decision into practice.

Steps, examples and worksheets to prepare the work in your business.

[Find a reading path](<https://lyntev.com/en/guides#percursos-title>)

### [How to reduce salon no-shows without putting clients off](<https://lyntev.com/en/guides/reduce-salon-no-shows>)

Investigate why an opening was lost and test one change at a time.

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

Technology with context, original analysis and sources you can consult.
