Real Agent Cases

Turn booked appointments into a realistic Washington DC itinerary with restaurants using Grok

Posted
by Jamie L. Saunders (@JamieLSaunders)
Last checked
Method:
How we verify

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Outcome

Ahead of a trip to DC, a poster gave Grok the appointments already set, the hotel locations and the remaining sights the group wanted to see. The poster says it produced an itinerary and, when prompted again, restaurants near the must-do stops to save searching once there, and called the result incredible.

Agent

Grok

Prompt Recreated prompt

The source didn't share its exact prompt, so we wrote this from what it describes.

Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing or a rule below tells you to.

Goal: Build a realistic day-by-day itinerary around the appointments I already have, then add restaurants near the key stops.

Fill in before running:
- City and dates: [CITY, DATES]
- Fixed appointments with times: [LIST]
- Hotel location(s) for each night: [ADDRESSES]
- Other sights we want to see: [LIST]
- Pace: [relaxed / action-packed]

Rules:
- Lock in fixed appointments first and fit everything else around them.
- Group sights by neighbourhood to cut travel time, and include travel times.
- Check opening hours and ticket or timed-entry rules for each sight.
- Add 1–2 restaurants near each main stop with price level.
- If a site asks for a login, a CAPTCHA or payment details, stop and hand control back to me.
- Ask for my OK before you pay, book, send, submit or cancel anything.
- Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify.

Output: A day-by-day table: time, activity, location, travel time, nearby food.

You'll know it worked when: every appointment fits, travel times are realistic, and nothing is closed when we plan to go.
Optional stronger version

Our rewrite with extra checks. The poster didn't test it.

Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing or a rule below tells you to.

Goal: Build a realistic day-by-day itinerary around the appointments I already have, then add restaurants near the key stops.

Fill in before running:
- City and dates: [CITY, DATES]
- Fixed appointments with times: [LIST]
- Hotel location(s) for each night: [ADDRESSES]
- Other sights we want to see: [LIST]
- Pace: [relaxed / action-packed]

Rules:
- Lock in fixed appointments first and fit everything else around them.
- Group sights by neighbourhood to cut travel time, and include travel times.
- Check opening hours and ticket or timed-entry rules for each sight.
- Add 1–2 restaurants near each main stop with price level.
- If a site asks for a login, a CAPTCHA or payment details, stop and hand control back to me.
- Ask for my OK before you pay, book, send, submit or cancel anything.
- Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify.
- Mark which sights need tickets booked in advance and by when.

Output: A day-by-day table: time, activity, location, travel time, nearby food.

You'll know it worked when: every appointment fits, travel times are realistic, and nothing is closed when we plan to go.

Before you finish: re-read my goal and constraints, check your answer against each one, and list anything you assumed or couldn't confirm.

Source

https://x.com/JamieLSaunders/status/1925972800700879008

  • A traveller planned a Hong Kong trip mainly with Gemini, using Grok and ChatGPT as extras, to organise locations, build itineraries, make packing lists and turn store addresses into Google Maps links. The traveller says routes were logical and personalised, but the AIs sometimes produced convincing addresses that didn't exist, and got names, opening hours or whether shops were still open wrong. Next time they'd verify every important detail on maps and official sites.

    Gemini, Grok, ChatGPT · Travel · Source date:

  • In Tom's Guide's ChatGPT-vs-Grok test, Ryan Morrison asked both for a 3-day Tokyo technology trip with hotels, transport, a robot restaurant and a budget in USD and yen; he judged Grok's itinerary more focused, realistic and detailed, with a fuller budget breakdown.

    Grok · Travel · Source date:

  • A parent asked Grok on an iPhone to plan a road trip with their daughter from the Bay Area to Tesla Giga Texas, with a stop halfway and hotel recommendations; then booked the hotels and added them to the calendar. On the road they asked Grok for food and rest stops when needed. The poster says LA traffic added 7 hours to one day, and they missed the factory tour because tickets sold out.

    Grok · Travel · Source date: