When should you use it?
- You want an agent to watch for openings
- The site has an account you care about
- You can set limits in your agent
Not for: Sites that ban automated checks outright; Scalping or resale
What do you need, and what do you get?
You need
- Site and venues to watch
- Check interval and daily cap
- Notification channel
You get
- Alerts when an opening appears
- Daily count of checks
- Automatic stop on errors
How does it work, step by step?
- Read the termsCheck what the site allows for automated access, and prefer official alerts or waitlists.
- Set a slow intervalPick a gentle check interval and a hard daily maximum.
- Stop on warningsHalt on errors, captchas or unusual responses.
- Alert, then you bookHave it message you about an opening and let you confirm.
- Log every checkKeep a count so you can see what the agent actually did.
The prompt
Our own prompt, inspired by Brian Distelburger (@bdistel) and written to work in Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Check {site} for open tables at {venues} on {dates}. Check no more often than every {minutes} minutes and no more than {daily_cap} times per day. Stop and message me if you see an error, a captcha or an unusual response. When an opening appears, message me; do not book. Log each check with the time.
Inspired by Brian Distelburger (@bdistel): I'm sharing this so you can learn from my mistake and don't accidentally ruin your marriage.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Account loss is the real cost; one suspension can end access.
- Support may not respond quickly; the poster had to ask many times.
- Many sites offer notify features that are safer.
Our take
Brian's story is the cautionary tale to read before building any watcher. An agent told to find a table will check as often as it can, and from the site's side that looks exactly like the scalping bots booking platforms work hard to block. The penalty landed on his personal account, which is the asset he cared about. Start with the platform's own tools: Resy and similar services offer notify lists that cost nothing and break no rules. If you still automate, read the terms first, set a slow interval measured in minutes, cap the total checks per day, and stop at the first error, captcha or warning email rather than retrying. Let the agent alert you instead of booking, so a person makes the reservation through the normal interface. Keep a simple log of every request; it shows the real rate your agent is running at, which is often far higher than intended. The same discipline applies to concert tickets, appointment slots and limited product drops.
Where the time goes back: You get alerts about openings without risking the account you need to book with.
FAQ
What went wrong?
Did he get it back?
Source and credit
Inspired by Brian Distelburger (@bdistel). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I'm sharing this so you can learn from my mistake and don't accidentally ruin your marriage.
- Creator
- Brian Distelburger (@bdistel)
- Published on
- X
- Original date
- Aug 17, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.