When should you use it?
- You keep client preferences in files on your computer
- You match clients to options and check availability
- You want a first draft shortlist, not a final answer
Not for: Sending output to a client without review; Relying on quoted prices or availability without confirming
What do you need, and what do you get?
You need
- A folder of client notes or history
- A desktop agent with file and web access
- The client's dates and constraints
You get
- A ranked shortlist with reasons for each
- Live availability and rate signals for the dates
- A longer document you can edit
How does it work, step by step?
- Point it at your notesGive the agent the folder holding past conversations and preferences.
- State the briefAdd the dates, budget and any constraints for this request.
- Let it match and checkHave it align options to stated tastes and verify live availability and rates.
- Ask for a comparisonRequest a table with fit reasons, availability signals and watchouts.
- Edit before sendingTreat the output as a draft; confirm prices and polish before the client sees it.
The prompt
Our own prompt, inspired by Jason Block and written to work in ChatGPT and Custom agent. Values in lime are placeholders.
Read my client notes in [folder]. For this trip, dates [dates], budget [budget], constraints [constraints], recommend [N] options that fit this client's stated tastes. For each, check current availability and rates for the dates, and give me a short table with the fit reason, an availability signal and a watchout. Add a longer write-up I can edit. Do not treat any price as final.
Inspired by Jason Block: Codex Desktop for Travel Advisors: A Real Client Example. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Quoted rates and availability can be stale; reconfirm before quoting a client.
- The output is a starting point, not client-ready, so always review.
Our take
Jason Block's example generalizes well beyond travel. Any advisor who keeps client history in files, whether a planner, a broker or a consultant, can let an agent match that history against live options instead of starting each request from a blank prompt. The notes do the work a good assistant would: remembering that a client loves a certain hotel group or dislikes long transfers. Treat the output as a draft. Rates and availability change quickly and agents misread booking pages, so reconfirm anything with a number on it directly with the supplier before quoting it to a client. Ask the agent to show where each preference came from in the notes, which makes errors in its reading easy to spot. Keep client files on your own machine or an approved system, and be careful what you paste into any cloud service, since travel notes often include birthdays, passport details and family information. Edit the write-up into your own voice before sending, because clients pay an advisor for judgment, not a pasted report.
Where the time goes back: An afternoon of cross-referencing notes against live availability collapses into a reviewed shortlist you finish in minutes.
FAQ
What does it read?
Can I send it straight to the client?
Source and credit
Inspired by Jason Block. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Codex Desktop for Travel Advisors: A Real Client Example
- Creator
- Jason Block
- Published on
- worldviatravelnetwork.com
- Original date
- Jun 18, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT
- 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.