Smarter by Thursday logo

Smarter by Thursday

Archives
Log in
Subscribe
August 18, 2026

Issue 33: Smarter by Thursday

Smarter by Thursday — Issue 33

Issue 33 · week of August 17, 2026

Smarter by Thursday

One practical AI win, every week. No jargon required.

By Dr. Rowan Hayes · Estimated read time: 6 minutes

Most of us have two competing instincts right now: the part that wants a bit more adventure, and the part that is just tired of hassles and bad service. This week we’re going to put AI to work on both: **planning a road trip that doesn’t exhaust you** and **writing a complaint letter that actually gets a response instead of a generic apology.** These are everyday situations where a bit of structured thinking plus a good AI prompt can save you time and, frankly, irritation.

Try at least one before Sunday. That is the whole assignment.

Use Case 1 of 2

Use Case 1: Planning a road trip using AI

On Thursday morning at 7:45am, Maria, 58, is staring at Google Maps with her second cup of coffee going cold. She lives in Columbus and wants to drive to Asheville in October with her husband, David. They’re both still working, so they only have four days total. David hates long, monotonous drives. Maria wants small towns and views, but she gets overwhelmed trying to juggle hotel options, driving times, and “things to see” articles.

She’s already opened eight tabs: one for a fall foliage forecast, three different hotel sites, a blog post from 2017, and a “Top 10 things to do” page that reads like it was written by a marketing intern. What she really wants is a simple plan: where to stop each night, how long each day’s drive will be, and two or three realistic activities that don’t require them to hike like 25-year-olds. She’s starting to think “maybe we just stay home,” not because the trip isn’t possible, but because the planning feels like work.

Here is the exact prompt to use:

Copy and paste this into ChatGPT or Claude:

I want your help planning a realistic 4-day driving road trip. Ask me clarifying questions first, then create a step-by-step plan.

Here are my details: - Starting city: [YOUR STARTING CITY] - Destination city: [YOUR FINAL DESTINATION] - Dates: [YOUR DATES OR MONTH] - Who’s traveling: [AGES, ANY MOBILITY LIMITS, GENERAL PREFERENCES] - Daily driving limit: I prefer no more than [X] hours of driving per day. - Budget level: [low / medium / higher-end but reasonable] - Interests: [e.g., small towns, easy scenic walks, local food, museums, etc.]

After you ask any follow-up questions and I answer them, create:

1) A 4-day itinerary with: - Each day’s start and end point - Approximate driving time for that day - 1 - 3 suggested stops or short detours with brief descriptions

2) Lodging suggestions: - 2 - 3 options per night in different price ranges - Why you chose each one (location, reviews, quiet vs lively, etc.)

3) A “Reality Check” section: - Any days that might feel too long for our age and preferences - Alternate shorter options if we get tired or want to skip something

Write everything in clear, plain language, and avoid hype. If you’re not sure about something (like a restaurant that might have closed), say so rather than guessing.

Why this prompt works:

This prompt gives the AI specific boundaries: starting point, destination, dates, driving limits, budget, and interests. That combination is what allows it to move from vague “trip ideas” to a concrete day-by-day plan. Asking the AI to pose clarifying questions first helps it fill in gaps you may not have noticed, like mobility limits or whether you prefer quiet hotels. Finally, the “Reality Check” section forces it to think about your actual energy level instead of treating you like a hyperactive travel blogger.

One thing to watch out for

AI is confident even when it’s wrong. Hotel names, driving times, and small attractions can be slightly off or out of date. Treat the itinerary as a **draft to verify**, not a finished product: click through to confirm hotels still exist, check current reviews, and sanity-check driving times against a real map. Also, resist the temptation to ask for “every possible stop” along the route - the AI will happily give you a list that looks impressive but would be miserable to actually follow.


Use Case 2 of 2

Use Case 2: Writing a complaint letter that actually gets results

On Monday at 9:10pm, Leonard, 64, is sitting at his kitchen table with a disappointing customer service email pulled up on his iPad. He booked a “premium room with city view” for a weekend reunion. When he arrived, he was given a smaller room facing a brick wall and told that “due to high demand, room types are not guaranteed.” The front desk staff was polite but dismissive.

Leonard isn’t looking for drama. He just wants what he paid for - or a meaningful apology and refund. He already tried writing his own email, but the response he got back was a generic: “We’re sorry for any inconvenience. We hope you’ll stay with us again.” No refund, no acknowledgment that the room type was misrepresented, nothing.

He feels that familiar frustration rising: “If I push harder, they’ll think I’m being difficult. If I let it go, I’m rewarding bad behavior.” What he needs is a letter that is firm but reasonable, clear about what went wrong, and crystal clear about what resolution would satisfy him. That’s where AI can help - not by venting, but by structuring his experience into something a customer service manager can’t brush aside so easily.

Here is the exact prompt to use:

Copy and paste this into ChatGPT or Claude:

I want your help drafting a firm but reasonable complaint letter that has a good chance of getting a meaningful response, not just a generic apology.

First, ask me 6 - 8 specific questions to understand: - What was promised vs what I actually received - Dates, booking details, and who I spoke with - How the problem affected me (time lost, money, stress, impact on others) - What outcome I consider fair (refund, partial refund, credit, etc.) - My tone preference (calm and factual, more forceful but polite, etc.)

Then, using my answers, write a one-page complaint letter with: - A clear subject line that makes it obvious what the issue is - A short opening paragraph stating the problem in plain language - A factual timeline of what happened, with dates and key details - A brief description of the impact on me (without sounding dramatic) - A specific, reasonable request for resolution and a requested timeframe - A closing that keeps the door open for continued relationship if they fix this

Avoid emotional language like “outrageous” or “disgusted” unless I specifically say I want that tone. Do not threaten legal action or “going public” unless I explicitly ask for that; focus on giving them a fair chance to correct the situation.

Why this prompt works:

This prompt forces the AI to collect details before it writes anything, which is what makes complaint letters persuasive: specifics, not just feelings. It also explicitly defines the letter’s structure - subject line, opening, timeline, impact, and requested resolution - so you don’t end up with a vague rant. By specifying tone and ruling out empty threats, you keep the message in that productive middle ground: serious, but still easy for a manager to respond to constructively.

One thing to watch out for

AI will sometimes make your letter more dramatic than necessary, especially if you mention that you’re upset. Before sending, read it aloud and remove anything that sounds like a TV courtroom show. Also, be careful not to let the AI invent details (names, exact policies, or quotes) that you don’t fully remember; exaggerations can backfire if the company checks their records. The letter should be polished, but fully truthful.


Know someone who spends too long on things AI could do in two minutes?

Forward Smarter by Thursday to three people who subscribe and I will send you my free AI Prompt Starter Pack: 20 ready-to-use prompts for everyday life.

Forward by email Open in browser Share on Facebook
Smarter by Thursday · By Dr. Rowan Hayes · drrowanhayes.com
Unsubscribe · View in browser

Don't miss what's next. Subscribe to Smarter by Thursday:
← Newer Issue 33: Smarter by Thursday Older → Issue 33: Smarter by Thursday
Bluesky
Powered by Buttondown, the easiest way to start and grow your newsletter.