OpenTable Notify Me Not Working? What Is Actually Happening

There are two completely different problems hiding inside "OpenTable Notify Me not working," and the fix depends on which one you have. The first is a delivery problem: you set the alert and nothing ever arrives, no push, no email, silence. That one is usually fixable in five minutes, and the checklist is below. The second is the one that sends people searching in frustration: the alert arrives, you tap it within seconds, and the table is already gone. That is not a bug, and no setting fixes it, because Notify Me is doing exactly what it was built to do. It just was not built to do what most people assume.

The short version, as of September 2026: OpenTable's Notify Me is an alert, not a hold. When a table matching your search opens up, OpenTable tells you it exists. It tells everyone else watching that restaurant too, and the table goes to whoever completes the booking first. Nothing is reserved for you at any point. So if your alerts are arriving and you keep losing anyway, the feature is working and the model is the problem. This guide covers both failures: how to get the alerts flowing if they are not, and what is actually happening when they flow and you still cannot convert one into a seat.

First, which failure do you have?

Ask one question: has an alert ever arrived? If you have never received a single notification since setting one up, you likely have a delivery problem, and the settings checklist below will probably solve it. If alerts do arrive but the table is gone by the time you get there, skip the checklist entirely. Your phone is fine, your settings are fine, and the rest of this page explains the race you are losing and the two honest ways to stop losing it.

The delivery checklist (alerts never arrive)

• System-level push permissions. The most common culprit by far. On iOS, Settings, Notifications, OpenTable, and confirm Allow Notifications is on. On Android, Settings, Apps, OpenTable, Notifications. If you tapped "Don't Allow" when the app first asked, possibly years ago, every alert since has been silently dropped, and the app cannot override that choice.
• In-app notification preferences. Inside the OpenTable app, check your account's notification settings and make sure availability alerts are enabled there too. Push permission at the OS level and alert preferences inside the app are separate switches, and either one alone can kill delivery.
• Focus modes and Do Not Disturb. An alert that fires at 2pm while your phone is in a work Focus that only lets favorites through is delivered and never seen. Check whether OpenTable is on your allowed-apps list.
• Email lands in promotions or spam. If you are relying on email alerts, search your mail for OpenTable before assuming nothing was sent. Gmail in particular files a lot of transactional restaurant mail under Promotions.
• The search is too narrow. An alert set for exactly 7:30pm for exactly four people only fires on inventory matching it. If the restaurant only ever releases 5:45 and 9:15 slots, your alert can be healthy and still never have a reason to fire. Widen the time range and try a smaller party size.
• Nothing ever actually opened. The quietest explanation is the most common: at a genuinely hard restaurant, weeks can pass without a matching table reopening at all. No cancellation, no alert. Silence is not proof the feature is broken.

What Notify Me actually is

Notify Me appears when the restaurant has nothing available for your search. You register interest in a date, a party size, and a time window, and if matching availability shows up later, OpenTable sends you a notification. That is the whole feature. The part the help pages tend to leave implicit is what happens on the other side of that alert: the table is not set aside for you, there is no claim window reserved to your account, and you are not the only person who was told. Everyone with a matching alert on that restaurant hears about the same table at roughly the same moment. One table, many phones. The notification is a starting gun, and the race is from lock screen to confirmed booking.

This is the same structural model as Resy's version of the feature, and it fails for the same structural reason, which is covered in why Resy Notify never gets you the table: an alert broadcast to the whole waiting list is worth almost nothing to any single person on it. The harder the restaurant, the longer the list, and the longer the list, the closer your personal odds get to zero.

Where the tables come from, and where they go

A Notify alert fires because inventory appeared, and on OpenTable that happens in two main ways. The first is a cancellation: someone gives up a booked table and it returns to the public book at an unpredictable hour. The second is restaurant-side release: many OpenTable venues run a rolling booking window, where each new date becomes bookable as the calendar advances, and some hold seats back and release them in batches closer to service. Both paths drop tables at moments no diner can predict, which is exactly why the alert feature exists, and exactly why it is so hard to act on. How windows open across the platforms is covered in when restaurant reservations open.

As for where the table goes when you lose: to the first account that finished checkout. That is often someone who happened to be in the app already, sometimes someone camped at a laptop, and sometimes automated tooling. There is no queue and no priority for how long you have been waiting or how early you set your alert. A Notify set three weeks ago and one set this morning hear the same gun at the same time.

Notify Me is not the waitlist

One more source of confusion worth clearing up: OpenTable also has a waitlist, and it is a different feature with different rules. The waitlist is a same-day, restaurant-run queue for people who are essentially in or near the room, and the restaurant works through it in order as tables turn. Notify Me is a future-dated availability alert with no queue and no order at all. People report waitlist behavior, like being passed over or never called, under the same "not working" phrase, but the failure modes are unrelated. If your issue is a same-day waitlist, the person to ask is the host stand, because the restaurant controls that list. If your issue is an availability alert for a future date, no host can help you, because the contest happens entirely inside the app.

Why tapping fast is not enough

Count the steps between the buzz and the booking: wake the phone, get through the lock screen, let the app open, land on the right restaurant and date, pick the slot, confirm. Each step costs seconds, and at a hard restaurant the whole contest is routinely over in fewer seconds than that. Losing by that margin feels like a glitch, which is why this query family fills up with people asking what is broken. Nothing is. You brought human reaction time to a contest that is decided at software speed, and the outcome was set before your thumb hit the screen.

What actually improves your odds

Manually, two things move the number. The first is flexibility: alerts and searches for a 2-top at off-peak times fire more often and convert more often, because the competition concentrates on Friday and Saturday prime time for four. The second is checking the book yourself at low-competition hours instead of waiting to be told. Cancellations land at random times around the clock, and at 11:45pm on a Tuesday almost nobody else is looking. The one thing that does not improve your odds is setting more alerts at more restaurants, since every alert buys you entry into another race with the same losing shape.

The structural fix

The gap in the alert model is the gap between knowing and booking, and that gap is what SeatSwiper closes. Instead of notifying you that a table appeared, it watches the exact table you want on OpenTable, Resy, or SevenRooms and books it the moment it shows up, on your own account and in your name, then tells you it is done. No lock screen, no tap-through, no racing the rest of the alert list. It can still lose a contested table to whoever got there first, and when it loses you pay nothing: first booking free, then a flat $5 only when it wins. The side-by-side with OpenTable's own alerts is in OpenTable Notify versus SeatSwiper, and the mechanics are in how SeatSwiper works.

The honest summary

If your alerts never arrive, it is almost always OS-level push permission, an in-app setting, a Focus mode, or a search too narrow to ever match, in roughly that order. Fix those and delivery resumes. If alerts arrive and you keep losing, stop troubleshooting, because there is nothing to fix: Notify Me is a broadcast to everyone watching, the table goes to the fastest checkout, and at a hard restaurant the fastest checkout is rarely a human holding a phone. Widen your search, hunt during quiet hours, or put a watcher on the table that books instead of alerting. Those are the three plays that actually change the outcome.