When should you use it?
- You want to know whether delegating bookings is worth it
- You tend to write short prompts
- You can step in when asked
Not for: Time-critical reservations; Bookings needing deposits without supervision
What do you need, and what do you get?
You need
- A location, date and time
- Party size and dietary needs
- An agent with a browser
You get
- A shortlist of suitable restaurants
- A completed reservation
- Notes on where the agent struggled
How does it work, step by step?
- Give the essentials up frontInclude party size, purpose, budget and allergies, since the agent may not ask.
- Review the shortlistPick from its table of options.
- Expect slow formsBooking widgets and dropdowns are where it loses minutes.
- Watch for substitutionsIf your time is taken, it may choose a nearby slot and tell you afterwards.
- Approve personal detailsEnter or confirm contact details when it hands back control.
The prompt
Our own prompt, inspired by Evan Sunwall and written to work in ChatGPT agent. Values in lime are placeholders.
Suggest three places for a work meal with [number] people close to [address] on [day] at [time]. Budget [range]. One guest has [dietary need]. Before searching, ask me anything else you need. Give a table with name, distance, price level, noise level and booking link. Do not book until I choose and confirm.
Inspired by Evan Sunwall: Initial Impressions of ChatGPT’s Agent: Successful, Shaky, and Slow. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Holds on reservation sites can expire while the agent fumbles with forms.
- It added a guest's shellfish allergy only after being told mid-task.
Our take
Evan Sunwall at Nielsen Norman Group gave ChatGPT agent mode a deliberately thin request for a work lunch close to a given Houston street address. It asked no clarifying questions, ran many searches and proposed three sensible options, then booking took far longer than doing it himself, with a mis-clicked time slot and a timed-out hold. A valuable reality check from a usability researcher: the research step is genuinely helpful; the clicking step is where agents still lose time. Give the agent the full brief at the start, party size, budget, cuisine limits and time window, and let it do the shortlist, then decide whether to finish the booking yourself. Watch for substitutions of restaurant or time without clear notice. Approve personal details and payment yourself. Re-run this kind of test every few months, because form-filling is exactly the part that improves quickly. Prefer agents that show each click so you can interrupt. Keep confirmations in your own email, not only in the chat.
Where the time goes back: Research and shortlisting are offloaded, but form-filling is still faster by hand today.
FAQ
Was the shortlist good?
Was it faster than doing it yourself?
Source and credit
Inspired by Evan Sunwall. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Initial Impressions of ChatGPT’s Agent: Successful, Shaky, and Slow
- Creator
- Evan Sunwall
- Published on
- nngroup.com
- Original date
- Aug 8, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT 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 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.