Resy Waitlist vs Notify: What Each Does, Which Gets the Table

The confusion is understandable, because Resy itself blurs the line: its own help material describes Notify as "a future waitlist." But the two features are built for different days and behave in opposite ways. Notify is for a future date that is already sold out: you tell Resy the date and time range you want, and if a matching table comes back (almost always a cancellation), you get a push or email alert. It is a broadcast, not a queue. You have no position, no place in line, and no hold on the table; everyone watching that slot is pinged at once and the seat goes to whoever completes checkout first. The Waitlist is for tonight, right now: it is the host stand's live walk-in list in digital form, an ordered queue where you genuinely hold a spot and the restaurant seats you when your turn comes. Current as of September 2026.

So which one actually gets you the table? For same-day seating at a restaurant that runs a live waitlist, the Waitlist does, reliably, because a queue with an order can only move forward. For a future date at a genuinely hard restaurant, Notify mostly does not, and the reasons are structural rather than bad luck. The rest of this guide walks through what each feature really does under the hood, restaurant side and diner side, and where each one is worth your time.

What Notify is under the hood

On any sold-out Resy date you will see a Notify button under the booking calendar (on the web it reads "Notify Me"). Tap it, pick the time range you would accept, and you are added to a list the restaurant can see in its own dashboard. When a matching table opens, Resy sends the alert. That is the entire feature. Nothing is reserved for you, no order is kept among the people waiting, and the table itself simply returns to open inventory, bookable by anyone who happens to be looking at the page, whether or not they ever set an alert.

Two consequences follow. First, at a hard restaurant the Notify list for a Saturday prime slot can hold dozens or hundreds of people, and one returned four-top triggers all of their phones in the same second. Your alert arriving is evidence the table exists, not evidence you can have it. Second, there is a tier above you: Resy's help center documents Priority Notify, which gives Amex Global Dining Access cardholders their alerts before the general list is told at all. On the most contested tables, some of the race is over before your starting gun fires. The fuller autopsy of why the alert so rarely converts is in why Resy Notify never gets you the table, and the second-scale disappearance it feeds into is covered in why Resy tables vanish instantly.

What the Waitlist is under the hood

The Waitlist is a different animal because it belongs to service, not to the booking calendar. In ResyOS, the software the restaurant runs, Notify and Waitlist are separate tabs: Notify manages future-date alert requests, while the Waitlist is the live list the host works from tonight, alongside reservations and walk-ins. When you are on it, you occupy a numbered place. The host quotes a wait, works down the list in order, and texts or calls when your table is ready. Nobody with a faster thumb can take your spot, because there is nothing to race for; the queue advances at the speed the dining room turns.

Some restaurants extend this beyond the front door. Resy's Mobile Waitlist feature (shown as "Remote Waitlist" in the consumer app) lets you join the evening's list from your phone before you arrive, with quoted waits by party size. Two honest caveats, both straight from the restaurant-side documentation. The restaurant controls the tap: it can snooze the remote list for 30, 60, or 90 minutes during a slammed stretch, or switch it off entirely, so the option appearing and disappearing is normal. And it is strictly same-day. There is no such thing as joining a waitlist for next Friday; the moment your question is about a future date, you are back in Notify territory.

The real difference: a queue versus a race

Strip the branding away and the comparison is simple. The Waitlist is a queue: ordered, same-day, and fair in the boring way queues are fair. Notify is a race: unordered, future-dated, and won by reaction time. That framing also explains the failure modes. A waitlist can be slow, and at a no-reservations hotspot it can be hours, but it cannot be lost. Notify is instant when it fires, but at any restaurant worth setting it for, the list of people it fires to is so long that the alert functions mostly as a notification that someone else got a table. People often conclude the feature is broken. It is not; it is doing exactly what an alert can do, which is less than what people want it to do.

It is worth saying that Notify is not useless. At a mid-demand restaurant, or for an off-peak slot, or on a weeknight, the alert list is short and a fast tap-through genuinely wins. The feature fails specifically where the stakes are highest, because the tables people most want alerts for are precisely the tables with the deepest alert lists. Demand concentrates the competition exactly where you care most.

Which one to use, by situation

• Eating tonight at a walk-in-friendly place: the Waitlist, without question. Join remotely if the restaurant offers it, or put your name down at the door and go get a drink nearby. Your spot holds.
• A future date that shows sold out: set Notify, because it is free and occasionally pays off, but do not build the evening around it. Treat it as a lottery ticket, not a plan.
• A date that has not opened for booking yet: neither feature applies. That is a release-time problem, covered in how the Resy 10am opening works. Be ready at the venue's opening hour instead.
• A hard table on a specific future night: Notify alone will probably not get you there. Pair it with checking the book yourself at low-competition hours, since cancellations land at random times and returned tables are visible to everyone, not just the alert list.

What happens to the table itself

One detail ties the whole comparison together: when a reservation is cancelled, the table does not pass to the Notify list. It goes back into the restaurant's open inventory, and the alert merely announces that fact. This is why someone who never set an alert, but happened to be browsing the page at 11:40pm, can book a table "ahead of" a hundred Notify subscribers. The alert list has no claim on anything. The Waitlist is the mirror image: the seat that comes up is genuinely assigned to the next party in line, which is why it feels trustworthy in a way Notify never quite does.

Closing the gap Notify leaves

The gap between the two features is the future-date queue that does not exist: nothing on Resy holds your place for a table that might come back next Thursday. That gap is what SeatSwiper fills. It watches the exact restaurant, date range, and party size you want on Resy, SevenRooms, or OpenTable, around the clock, and when a matching table reappears it books it immediately on your own account, in your own name, instead of sending you an alert to race on. The first booking is free, then a flat $5 only when it actually lands you the seat. The mechanics are laid out in how SeatSwiper works. For tonight, at a restaurant with a live waitlist, you do not need any of this: just join the queue.