Aller au contenu principal
Tous les articles
POSSep 1, 2026

How to run a restaurant waitlist on fully booked nights

A restaurant waitlist on a fully booked night does two jobs. Before service, it gives people who could not get a table a way to claim one when a booking is cancelled. During service, it manages walk-ins who are happy to wait. Run them as separate lists with their own rules: advance requests get a time-limited offer when a table frees up, and walk-ins get a wait time based on when tables are due to finish.

The aim is to put every released table in front of someone who wants it, quickly, without the host promising tables the room cannot deliver.

Why keep a waitlist when you are already full?

A full book rarely stays full. Plans change and some guests cancel on the day. Without a list, a cancellation at 5pm can easily become an empty table at 8pm, because nobody outside the restaurant knows it is available. With one, the host has a queue of people who have already said they want that sitting.

The list also tells you about demand. If Friday at 8pm builds a long waitlist every week while 6pm has space, that is a case for adjusting your sittings or pricing a set menu for the early slot.

How should an advance restaurant waitlist work?

Treat a waitlist entry as a request and say so clearly. Guests should know they do not have a booking until they accept an offer. Capture enough to match them to a table:

  • Party size, and whether the group could sit at two tables
  • The times they could make, ideally a window rather than a single slot
  • A mobile number or email address they will check on the day
  • Allergies or access needs, so an offer goes to a party you can seat properly

When a table becomes free, offer it to the first party on the list whose size and time window fit. Strict first-come order can leave a released two-top unused while a party of four waits at the top of the list. Tell guests the list is matched by party size and time, so the order makes sense to them.

Joining the list should cost nothing. Where the sitting needs a deposit or card guarantee, take it when the guest accepts an offer, on the same terms as a normal booking.

How long should a waitlist offer stay open?

An offer should stay open long enough for a guest to see it and short enough that the table can go to someone else if they do not respond. The right window depends on how close the booking is. An offer for a table next Saturday can stay open for a few hours. An offer for a table in 45 minutes needs a much shorter window, and the host may need to phone the guest.

When an offer expires, the guest should go back on the list unless they ask to leave it, and the table should go to the next party that fits. Automating that step helps on busy nights, because nobody on the door has time to chase replies.

Running the walk-in waitlist on the night

Walk-in waits go wrong when the host guesses. Quote times from the room: which tables are due to finish, which bookings are still to arrive and which tables can be combined. A host who can see bookings, seated tables and their timings together can give a realistic range.

  • Take a mobile number and let guests wait at the bar or nearby so the door stays clear
  • Quote a range and update it if it slips; a revised estimate is easier on everyone than silence
  • Seat by fit, so a walk-in couple does not take a four-top that a booked party needs at 8.30
  • Combine tables for a larger walk-in only when every table in the combination is clear for the whole sitting
  • Release no-show tables to the walk-in list once the grace period in your policy has passed

How to get tables back before the night

A waitlist only works if cancellations reach you in time. Send reminders a day or two ahead with a simple way to cancel or change the booking, and let guests manage bookings online within your rules. A card guarantee or deposit also gives guests a reason to tell you when they cannot come. Our guide to restaurant no-shows covers how to set those up fairly.

What to do with waitlist data afterwards

Review the list after a few busy weeks. Count how many requests each sitting attracted, how many became bookings and how many offers expired. Long lists for the same slot point to demand you could serve with a second sitting or more bar seating. A high share of expired offers suggests the window is too short or offers are reaching guests too late.

Guests who joined the list and never got a table still wanted to eat with you. If they agreed to hear from you, a message about a quieter night or the next booking window is a reasonable follow-up. Check what each guest agreed to before you send anything promotional; our guide to UK GDPR and PECR for hospitality email marketing covers the consent rules.

How Tiquo runs restaurant waitlists and walk-ins

In Tiquo, you enable Waitlist on the inventory that should offer it, and customers can join when a slot is full. Joining does not take payment. When capacity becomes available, Tiquo sends a temporary offer that the customer can accept before its expiry time. Offers can be free or require payment, and an expired offer returns the request to the waitlist instead of becoming a confirmed booking. Card guarantees can also be configured where a waitlist flow requires them, and joining still does not collect a payment.

On the night, Tiquo's live floor plan handles walk-ins. Staff start a walk-in with the booking type and party size, then review suggested tables or choose an available table themselves. A larger party can use a combination of tables, and every selected table is reserved for the booking period with the same capacity and conflict checks used elsewhere in Tiquo.

The floor plan's date and timeline let the host review covers across the evening and open the booking or order that needs attention, which makes it easier to quote waits from the room. When a booked party needs to move, compatible tables are shown while conflicting tables stay unavailable. If you are rethinking the room itself, our guide to restaurant floor plan design covers table mix and combinations.

Before the night, Tiquo can automate booking confirmations and reminders, and guests can cancel online within the cancellation rules you set for the service, which gives them an easy way to release a table they no longer need. For peak sittings, a deposit or a no-show card guarantee gives guests another reason to tell you in time.

© 2026 Tiquo. « Tiquo » et le logo Tiquo sont des marques déposées de Tiquo Ltd.

GDPR · CCPA · PCI DSS · ICO · Cyber Essentials Certified · EU–US DPF · SOC 2 Type II (in progress) · ISO 27001 (in progress)

Security & Operational

  • 99.99% SLA Uptime
  • AES-256 encryption at rest
  • TLS 1.3 in transit
  • AES-256 / TLS 1.3
  • Perfect Forward Secrecy (PFS)
  • HTTP Strict Transport Security (HSTS)
  • 99.999999999% (11 nines) data durability
  • Automated backups
  • DDoS protection
  • Web Application Firewall (WAF)
  • Zero Trust posture
  • Role-Based Access Control (RBAC)
  • Principle of Least Privilege
  • Secret scanning in CI
  • SBOM generation
  • Dependency supply-chain controls
  • 24/7 infrastructure monitoring
  • GDPR Article 22 safeguards
  • Data Protection Impact Assessments (DPIAs)
  • Records of Processing Activities (ROPA)
  • SAML 2.0 SSO
  • EASIE SSO
  • OAuth 2.0 / OpenID Connect (OIDC)
  • SCIM 2.0 provisioning
  • MFA / 2FA enforcement
  • Responsible disclosure / bug bounty programme

Privacy, Data Protection & Statutory Obligations

  • ICO Registered
  • UK Modern Slavery Act 2015 compliant
  • UK Public Interest Disclosure Act 1998 compliant
  • EU Article 27 Representative appointed (Paris, France)
  • Swiss FADP Article 14 Representative appointed
  • UK GDPR compliant
  • EU GDPR/DSGVO compliant
  • UK Data Protection Act 2018 compliant
  • Swiss revFADP compliant
  • CCPA / CPRA compliant (California)
  • VCDPA compliant (Virginia)
  • CPA compliant (Colorado)
  • CTDPA compliant (Connecticut)
  • TDPSA compliant (Texas)
  • OCPA compliant (Oregon)
  • MCDPA compliant (Montana)
  • FDBR compliant (Florida)
  • ICDPA compliant (Iowa)
  • ICDPA compliant (Indiana)
  • TIPA compliant (Tennessee)
  • DPDPA compliant (Delaware)
  • NJDPA compliant (New Jersey)
  • NHDPA compliant (New Hampshire)
  • NDPA compliant (Nebraska)
  • MCDPA compliant (Minnesota)
  • MODPA compliant (Maryland)
  • KCDPA compliant (Kentucky)
  • RIDTPPA compliant (Rhode Island)
  • Canada PIPEDA compliant
  • Quebec Law 25 compliant
  • Alberta PIPA compliant
  • British Columbia PIPA compliant
  • Singapore PDPA compliant
  • Hong Kong PDPO compliant
  • Brazil LGPD compliant
  • Japan APPI compliant
  • Australia Privacy Act / APPs compliant
  • India DPDPA 2023 compliant
  • Thailand PDPA compliant
  • Malaysia PDPA 2010 (as amended 2024) compliant
  • New Zealand Privacy Act 2020 compliant
  • South Africa POPIA compliant
  • UAE PDPL compliant
  • Mexico LFPDPPP compliant
  • Kenya Data Protection Act 2019 compliant
  • Ghana Data Protection Act 2012 compliant
  • Nigeria NDPA 2023 compliant
  • Indonesia PDP Law 2022 compliant
  • Philippines Data Privacy Act 2012 compliant

Global Fiscal & E-Invoicing

  • EN 16931 - EU e-invoicing core standard
  • UBL 2.1 - Universal Business Language
  • Austria - RKSV
  • Belgium - Peppol BIS 3.0 (B2B)
  • Czechia - fiscalization
  • Croatia - Fiscalization 2.0
  • Denmark - Peppol BIS 3.0 (B2B)
  • France - NF525 / LNE / Infocert, Factur-X / PDP, E-Reporting
  • Germany - KassenSichV / TSE, DSFinV-K, GoBD, E-Rechnung B2B (XRechnung / ZUGFeRD)
  • Hungary - Online Szamla
  • Italy - Scontrino, FatturaPA (via SDI)
  • Lithuania - i.SAF / i.MAS
  • Norway - Peppol BIS 3.0 (B2B), SAF-T
  • Poland - KSeF
  • Portugal - ATCUD/QR, SAF-T PT
  • Slovakia - eKasa
  • Slovenia - fiscalization (davcno potrjevanje)
  • Spain - FacturaE, SII, VeriFactu, TicketBAI
  • Sweden - SKVFS (certified cash registers)
  • Argentina - ARCA (Q4 2026)
  • Australia - Peppol PINT A-NZ (Q4 2026)
  • Brazil - NFe, NFCe, NFSe (Q4 2026)
  • Chile - SII Chile (Q4 2026)
  • Colombia - DIAN (Q4 2026)
  • Finland - Finvoice, TEAPPSXML (Q4 2026)
  • Japan - JP PINT (Peppol) (Q3 2026)
  • Malaysia - Peppol Malaysia (Q4 2026)
  • Mexico - CFDI (Q4 2026)
  • New Zealand - Peppol PINT A-NZ (Q4 2026)
  • Peru - SUNAT (Q4 2026)
  • Romania - Peppol (RO e-invoice) (Q4 2026)
  • Saudi Arabia - ZATCA (Q4 2026)
  • Singapore - Peppol BIS 3.0 (Q4 2026)
  • United Arab Emirates - Peppol (5C) (Q4 2026)

Standards & Frameworks

  • Cyber Essentials Certified
  • SOC 2 Type II - audit in progress
  • ISO/IEC 27001 - audit in progress
  • NIST Cybersecurity Framework - aligned
  • NIST Privacy Framework - aligned
  • NIST SP 800-53 / 800-63 / 800-63B - aligned
  • NIST AI Risk Management Framework - aligned
  • CIS Critical Security Controls / CIS Benchmarks - aligned
  • OWASP ASVS & OWASP Top Ten - aligned
  • ISO 25010 (quality) - aligned
  • ISO 31000 (risk) - aligned
  • ITIL - aligned
  • W3C Web Standards - aligned
  • OpenAPI Standard - aligned
  • DevSecOps practices - aligned
  • ePrivacy Directive - aligned
  • EU Whistleblowing Directive (2019/1937) - aligned

Payments Compliance

  • PCI DSS Level 1
  • PSD2 / Strong Customer Authentication
  • 3D Secure (3DS)
  • EMVCo Level 1 & 2
  • AML / KYC controls
  • Sanctions screening (OFAC, UN, EU, HMT)

International Data Transfer Mechanisms

  • EU-US Data Privacy Framework
  • EU Standard Contractual Clauses (Decision 2021/914) - Modules 2 & 3
  • UK International Data Transfer Agreement (IDTA) + ICO Addendum
  • Swiss FDPIC-recognised transfer mechanisms
  • APEC Cross-Border Privacy Rules (CBPR)

Accessibility Compliance

  • ADA (Americans with Disabilities Act) - aligned
  • European Accessibility Act (EAA) 2025 - aligned
  • WCAG 2.2 - aligned
  • EN 301 549 - aligned
  • WAI-ARIA - aligned

Une plateforme unique pour hôtels, spas, cours, événements, restaurants et plus encore.

Tiquo Ltd
Londres, Royaume-Uni

LinkedInTop Performer Spring

Nous utilisons des cookies

Choisissez si vous autorisez les cookies d’analyse et de publicité. Vous pouvez les accepter ou les refuser. Fermer cet avis revient à les refuser.

En savoir plus