How Restaurants Decide Who Gets Tables

The short answer: for most of the room, nobody decides. The public book on Resy, OpenTable, or the restaurant's own site is first come, first served, and the software gives the table to whoever taps fastest. But at a busy restaurant a meaningful slice of the seats never reaches that public book at all, and that slice is allocated by people, using data. Every modern reservation platform ships a guest database on the restaurant side. A host running SevenRooms or ResyOS can see, before you walk in, how many times you have visited, what you spent, whether you cancel late, whether you tipped the sommelier, and whatever tags the staff attached to your name. A regular with a fat profile gets a held table released to them by a human. A first-timer gets whatever the algorithm had left. Current as of September 2026.

So the honest picture has two lanes. Lane one is the race everyone knows: inventory goes live at a set hour, hundreds of people hit it, and the platform is a neutral referee. Lane two is the house book: holds for regulars, investors, friends of the chef, VIP tags, and concierge relationships, filled by phone, email, and the host's judgment. This guide explains how lane two actually works, because it is the part no platform help center will describe, and it changes how you should play lane one.

The guest profile: what the restaurant knows about you

When you book anywhere that runs a serious front of house, you are not just claiming a slot, you are updating a file. SevenRooms, which powers booking for many of the hardest rooms in the country, is explicit about this in its own product marketing: profiles carry over 100 data points per guest, including dining preferences, order history, and lifetime and itemized spend pulled in through point of sale integrations. Restaurants can attach unlimited tags to a profile, and the system also applies auto-tags from rules, with the company's own examples including labels like "positive reviewer" and "steak lover", plus segments like "big spenders." Resy's restaurant side, ResyOS, describes the same toolkit in its own terms: customizable tags, notes, visit history, and spend data, visible to the team before service starts. OpenTable's restaurant software keeps guest histories and notes as well. All of this is as of September 2026, and all of it comes from the platforms' own public product pages, not speculation.

In practice a profile at a busy restaurant tends to accumulate a few kinds of information. Visit count and recency: are you a regular or a tourist. Spend: check averages, wine purchases, whether you order the tasting or split an appetizer. Behavior: no-shows, late cancellations, chronic lateness, how you treated the staff. Occasions and preferences: anniversaries, allergies, favorite table, favorite server. And the free-text notes, which are exactly what you imagine, ranging from "loves the corner banquette, always sends a glass to the kitchen" to warnings about difficult guests. None of this is sinister. It is the digital version of what a great maitre d' always kept in their head. What changed is that it now persists, syncs across a restaurant group, and can be queried.

What a VIP tag actually does

A tag by itself seats nobody. What it does is change how the machine and the humans treat your requests. Concretely, at restaurants running this kind of system, a strong profile can mean: your booking request from the waitlist or an email gets answered instead of ignored; the host releases one of the held tables to you when the public book says sold out; you get the better table within your time slot, because table assignment is a manual pass the host does before service; your slightly late arrival is absorbed instead of forfeited; and at some rooms, you get access to times that were never posted publicly at all. The reverse is also true. A profile with two no-shows and a nasty note is quietly deprioritized, and at some restaurants it will simply never win a discretion call again.

Who earns the tag? Less glamorous people than the mythology suggests. Genuine celebrities and industry friends, yes, but the bulk of any VIP list is regulars: people who come monthly, spend decently, cancel like adults, and are pleasant. Spend matters but consistency matters more. A guest who visits eight times a year at a normal check is usually worth more to a restaurant than a whale who appeared once, because the entire point of the guest database is predicting who will keep the room full in February.

Where the held tables come from

The reason lane two has anything to give is that restaurants rarely put the whole room online. Some seats are held for walk-ins and the bar. Some are held back as service insurance, so a double-sat section or a lingering table does not wreck the night. And some are held for exactly the discretionary use this page is about: the investor, the regular, the concierge at the hotel that sends steady business. How large that hidden slice is varies by restaurant and is almost never published, so treat any specific percentage you read online as a guess. What is verifiable is the mechanism: platform software lets restaurants control inventory by time and table, which means the public book is whatever the restaurant decided to show you, not a picture of the dining room. This is one of the reasons a room can look sold out for weeks while the bar seats walk-ins all night, a dynamic covered in whether hard restaurants take walk-ins.

What this means if you have no profile

Here is the practical takeaway, and it is more encouraging than it sounds: if the restaurant does not know you, the held tables are not your game, and pretending otherwise wastes effort. Emailing a hard room to explain that it is your anniversary does occasionally work, but you are asking for a discretion call with an empty file. Your real lanes are the public ones, and they are genuinely winnable. The first is the release: know exactly when the restaurant opens its book, covered in when restaurant reservations open, and be ready at that minute. The second is the cancellation: every restaurant's book churns as plans collapse, and each cancelled table goes straight back into the public pool, where it belongs to whoever sees it first. Cancellation deadlines and fees shape when those tables reappear, which is the subject of restaurant cancellation policies. A returned table is the one moment the anonymous diner and the regular compete on even terms, because the software does not consult the VIP list before showing availability to the public.

The other move is slower but real: become a regular somewhere. Not everywhere, one place. Sit at the bar, come back, be remembered, cancel properly when you must. The entire machinery described above exists to find and reward exactly that behavior, and it works at neighborhood restaurants just as it does at famous ones. Six months of showing up beats any booking trick ever invented, at that one restaurant.

Common myths, checked

• "The apps give VIPs first access to reservations." Mostly false as stated. The diner-facing apps run the public book first come, first served (Resy's paid Amex-linked perks and OpenTable's points exist, but they do not reorder the general queue for a specific table). The preference happens on the restaurant side, with inventory that never went public.
• "Sold out means full." False. It means the public allocation is taken. Holds, the bar, and service insurance are not in that number, and cancellations flow back into it constantly, which is why sold-out tables appear and vanish in seconds.
• "Slipping the host cash works." Occasionally, at some rooms, and it is a poor bet at exactly the restaurants people ask about. A hard room's host stands to lose more than a tip is worth, and the guest database means they do not need your twenty to know who matters to the house.
• "My data is only on one app." Within a restaurant group running shared CRM, your profile can follow you between sister restaurants. The no-show you logged at one room can be visible at its sibling.

Playing the lane that is actually open

You cannot automate becoming a regular, and nothing reputable can get you onto a VIP list. What can be automated is the public lane, which is a pure attention contest. SeatSwiper watches the restaurant you want on Resy, SevenRooms, or OpenTable around the clock and books the moment a table appears, at the release or when a cancellation puts one back at some unwatchable hour. It books on your own account, in your own name, so the profile being built is yours. First booking free, then $5 only when it actually gets you the seat. The full mechanics are in how SeatSwiper works. It does not touch lane two, because nothing honest can. It just makes sure you never lose lane one for the one reason that is entirely fixable: not looking at the right second.