Food · Community report
Book a hard-to-get restaurant reservation
Book a hard-to-get restaurant reservation. Get a table at a restaurant that is normally impossible to walk into, confirmed on the platform itself.
What you can get
Reaches your accounts Creates or changes things in accounts you connect, with your approval.
-
It does
- Books or joins a waitlist for the table once you approve the details
- Does not create a table where the restaurant has released none
-
It stops and asks
- Before it starts: confirm the restaurant, platform, party size and date window.
- While it searches: ask for a status update rather than assuming silence means nothing happened.
- Before you rely on it: check the confirmation on the platform itself, especially if a deposit was involved.
-
You approve
- Approval before any deposit or card hold is placed
Derived from this task's own brief and steps, not from the source.
- Set the real targetStops for your approval
Restaurant, party size, date/time window and how flexible it is.
- Identify the platform
Confirm which booking system the restaurant actually uses.
- Watch and act
Checks or waitlists on the platform, acting fast when a slot opens.
- Confirm before you trust itStops for your approval
You verify the platform's own confirmation before relying on the table.
Editorial, not from the source
Works when
- The restaurant uses a booking platform like Resy or OpenTable rather than phone-only reservations.
- You can give a real date and time window instead of 'whenever works'.
- You will check the confirmation yourself before counting on the table.
Does not work when
- The restaurant takes reservations by phone only.
- You need a specific date with no flexibility and the platform shows nothing open.
- You are not willing to let it keep checking over multiple days.
Book a hard-to-get restaurant reservation: review template
| Request | Platform result | Your check |
|---|---|---|
| [Restaurant, party size, date/time] | [Booked / waitlisted / nothing open] | [Confirm on platform] |
| [Deposit required?] | [Amount and hold] | [Approve before charge] |
| [Flexibility window] | [Checks made] | [Still open / closed] |
The source case
On X, @jackybuilds lists three things Instinct can book after a week of use, including hard-to-get Resy reservations, alongside tennis courts and theater tickets, and suggests treating it like an AI concierge rather than a chief of staff. The post is a capability summary, not an account of one specific reservation: no restaurant name, confirmation, or party size is given, and nothing here has been run by this directory.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
3 things you can get it to book for you TODAY: - Hard to get Resy reservations
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring Restaurant and party size, Date and time window, Which booking platform the restaurant uses. Acts Books or joins a waitlist for the table once you approve the details. Does not create a table where the restaurant has released none. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- Restaurant and party size
- Date and time window
- Which booking platform the restaurant uses
Connected
- The booking platform account, such as Resy or OpenTable
- A payment method, if the restaurant requires a deposit
How to try it
Editorial, not from the source
- Name the restaurant, the party size, and the date and time window you actually want, including how flexible you are on time.
- Say which booking platform you use for that restaurant, such as Resy or OpenTable, since a hard-to-get table is usually gated by one specific system and its release schedule.
- Ask for a status update rather than a silent retry: whether the slot opened, whether a waitlist or notify option was used instead, and when.
- Confirm the booking yourself against the platform's own confirmation before telling anyone else the table is secured.
Say exactly what you want, including how flexible you are
A hard-to-get table is hard because the restaurant releases a fixed number of slots against far more demand, so vague instructions waste the one advantage an agent has: persistence. Name the restaurant, the party size, and a real date and time window, then say explicitly how much flexibility exists on both. A table at 6pm on a Tuesday behaves differently from a table any night that week, and the difference changes whether it should check once a day or sit on a booking page watching for a cancellation. If the restaurant runs a release at a fixed time, such as a nightly 10am drop, say so if you know it. The more precisely the target is defined, the more useful repeated checking becomes, because each check tests the same narrow window rather than a moving target.
Match the platform the restaurant actually uses
Hard-to-get reservations are usually gated by one specific booking platform, most often Resy or OpenTable, and that platform's own rules decide what is possible. Tell the agent which platform the restaurant uses if you know it, and let it tell you if the name doesn't match what it finds, since restaurants do switch platforms. Ask for the platform's own features to be used where they exist, a waitlist, a notify-me alert, or a cancellation feed, rather than only a repeated manual-looking check, which platforms are increasingly built to detect and throttle. If the platform requires an account login, decide in advance whether you are comfortable sharing that access, and keep in mind that some platforms cap how far in advance a table can even be requested, which is worth confirming before you expect a result that week.
Treat a confirmation as the real finish line
A reservation that exists only in a chat summary is not a reservation yet. Ask for the platform's own confirmation, whether that is an email, a confirmation number, or a screen you can check directly, and treat that as the point the task is actually done. If the restaurant requires a deposit or a card hold to secure a hard-to-get slot, that is a payment decision and should come back to you before it happens, not after. Build in a status check rather than silence: a hard-to-get table might take days of watching, and you want to know whether nothing has opened yet or whether something went wrong with the search itself. Before you tell anyone else the table is secured, open the platform and confirm it yourself.
Open Instinct to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
- The source is a short capability list from one week of use, not a detailed account of a specific reservation: no restaurant, date, party size or confirmation is shown.
- Hard-to-get tables are hard precisely because demand outstrips releases; an agent checking a booking platform does not create a table the restaurant has not released.
- Booking platforms rate-limit and block automated-looking activity; an approach that works for one restaurant's release pattern may not work for another's.
- Some popular restaurants require a deposit or card hold to secure a hard-to-get slot, which is a payment decision that should stay with you.
Editorial, not from the source
- Before it starts: confirm the restaurant, platform, party size and date window.
- While it searches: ask for a status update rather than assuming silence means nothing happened.
- Before you rely on it: check the confirmation on the platform itself, especially if a deposit was involved.
Editorial, not from the source
- No slot ever opens for your date
- Ask it to widen the time window or days first; hard-to-get restaurants often release in narrow nightly windows rather than a steady stream.
- The booking platform blocks repeated automated checks
- Space out the checks or switch to a waitlist/notify feature if the restaurant offers one, rather than hammering the same page.
- A deposit was charged without your approval
- Treat that as a stop condition: cancel if the restaurant allows it and require explicit approval before any future card hold.
Common questions
Can an agent get a table that the restaurant has not released?
No. It can watch for a release, a cancellation, or a waitlist opening and act quickly when one appears, but it cannot create availability a hard-to-get restaurant has not put on the booking platform.
Which booking platforms does this work with?
Most hard-to-get restaurants use a platform like Resy or OpenTable rather than taking reservations by phone. Name the platform if you know it; a restaurant that is phone-only is not a fit for this task.
Will it keep checking over several days?
Only if you ask for that and say how long. A single check against a fully booked restaurant will usually come back empty; persistence over time is the actual advantage here, not a one-off attempt.
Does it need my payment details?
Only if the restaurant requires a deposit or card hold to secure the reservation, and that should be approved by you before it happens rather than assumed.
How do I know the table is really booked?
Check the platform's own confirmation, email or confirmation number yourself. A chat summary saying a table is booked is not the same as the restaurant's own record of it.
Next in Food
Get recurring task recommendations — ask your own agent to check for relevant updates.