Smarter by Thursday logo

Smarter by Thursday

Archives
Log in
Subscribe
June 19, 2026

Issue 25: Smarter by Thursday

Smarter by Thursday — Issue 25

Issue 25 · week of June 15, 2026

Smarter by Thursday

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

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

This week we’re looking at two very practical uses of AI: **planning a road trip** and **writing a complaint letter that actually gets results**. Both are situations where most of us either waste time, get overwhelmed, or just give up and live with a second-rate outcome. AI can’t drive the car or yell at customer service for you, but it can dramatically shorten the “figuring it out” part and help you sound clear, firm, and reasonable instead of exhausted and annoyed.

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 a Wednesday night in late June, Linda, 62, sat at her kitchen table with a legal pad, three travel blogs open on her iPad, and a growing headache. Her plan: drive from Columbus, Ohio to Glacier National Park with her husband over 9 - 10 days. Her reality: five hours in, she had a messy list of towns, a rough idea of miles, and no real sense of which stops were worth it versus just “somewhere to sleep off the interstate.”

She wasn’t trying to be extravagant. She just wanted: no 11-hour driving days, one or two genuinely lovely stops along the way (not just chain hotels by a highway exit), and enough structure that her husband would stop asking, “So where are we staying that night?” every twenty minutes. She’d tried Googling “Columbus to Glacier road trip itinerary” and got a firehose of blog posts, ads, and random forum threads. Somewhere in there might be a perfect plan, but she did not want to spend her entire Wednesday night auditioning strangers’ trips.

So she opened an AI chat and treated it the way she would treat a decent travel agent: she told it who she was, what she cared about, and what she didn’t want. Ten minutes later she had a day‑by‑day draft itinerary, with realistic driving days, specific towns, and backup ideas if the weather turned bad. It wasn’t magic, and she still checked things herself, but it got her 70 - 80% of the way there in a fraction of the time a dozen random web searches would have taken.

Here is the exact prompt to use:

Copy and paste this into ChatGPT or Claude:

Copy and paste this into your AI of choice, then edit the details in brackets to fit your life.

> I want you to act as a **personal road trip planner**. Ask me 5 - 7 clarifying questions first, then create a detailed itinerary. > > Here is the basic outline of my trip: > - Starting point: [city, state] > - Ending point: [city, state] > - Trip dates or total days available: [e.g., 9 days, flexible by 1 day] > - Who is traveling: [e.g., two adults in our 60s, reasonably active but not hikers] > - Daily driving limit: [e.g., no more than 6 hours of driving per day] > - Budget level: [e.g., mid-range: nicer motels or 3-star hotels, not luxury] > - Interests: [e.g., small towns, scenic drives, local food, light walking, no museums that take all day] > - Things to avoid: [e.g., big cities, high crime areas, dirt roads, very remote areas with no cell signal, tourist traps] > > After you ask your clarifying questions and I answer them, please: > 1. Propose a **day-by-day itinerary** that includes: departure and arrival town each day, approximate driving time and miles, 2 - 3 suggested stops or sights along the way, and one or two recommended areas/neighborhoods to look for lodging (not specific hotels). > 2. Make sure the driving times are realistic (build in time for restrooms, gas, and meals) and keep each day within my driving limit. > 3. Suggest **at least one “stretch” day** where we have a shorter drive and can enjoy a particularly nice town or attraction for a half-day. > 4. Point out any **sections where weather, traffic, or closures** are commonly an issue during [month of travel], and suggest a backup route or backup activity for those days. > 5. At the end, give me a short checklist of what I should double-check or book myself (lodging, park reservations, etc.) so I don’t rely blindly on AI. > > Start by asking your clarifying questions now.

Why this prompt works:

This prompt works because it gives the AI **constraints** (daily driving limit, interests, budget, things to avoid) and **clear tasks** (day‑by‑day plan, realistic drive times, backup options), instead of a vague “Plan my trip.” You’re also telling it to **ask questions first**, which is a hallmark of a better planning experience; the more context you give, the less generic the results. Finally, it explicitly asks for a checklist of what you should verify yourself, which keeps you in control.

One thing to watch out for

AI will confidently recommend restaurants that closed three years ago, scenic roads that are under construction, or under-estimate how tiring a 6-hour “drive time” day actually feels once you add meals and stops. Always treat the itinerary as a **starting draft**, not gospel: cross-check drive times on a map, look up at least a few of the suggested stops and towns, and check official sites (especially for national parks, ferries, and mountain passes) for closures or reservation systems. If something sounds off, it probably is - ask follow‑up questions or do a quick manual search.


Use Case 2 of 2

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

On a Monday afternoon, about two weeks after a family wedding, Mark, 54, finally sat down to write the email he’d been putting off. He and his wife had splurged on a “premium” hotel for three nights. The stay was a mess: the room they booked wasn’t available the first night, the air conditioning died on night two, and their bill still showed a mystery “resort fee” and a bar tab from someone else’s room. The front desk staff were cheerful but utterly ineffective.

He’d already spent 40 minutes on hold with the hotel’s central customer service and gotten nowhere. The rep was polite but vague: “We’ll look into it.” He knew he should write something more formal - maybe to the general manager or the company’s customer care email - but every time he opened a blank document, it turned into either a long emotional rant or three stiff, lawyerly sentences that didn’t sound like him at all. What he really wanted was: a partial refund, the incorrect charges removed, and something in writing that acknowledged the mess.

So he opened an AI chat and treated it like a writing coach. He described what happened in plain language and asked it to help shape that into a clear, firm, polite complaint that sounded like a reasonable adult, not a push-over or a lunatic. He ended up with a letter he would actually send: specific dates, specific problems, specific ask. It did not guarantee success - nothing does - but it moved him from “annoyed and stuck” to “done and sent” in under twenty minutes.

Here is the exact prompt to use:

Copy and paste this into ChatGPT or Claude:

First, you’ll feed the AI your story. Then you’ll ask it to rewrite. Copy this and fill in the brackets.

> I want you to act as a **polite but firm customer advocate** and help me write a complaint letter that is likely to get a fair resolution. > > I will paste a rough description of what happened below. Please read it and then: > - Ask me up to 5 clarifying questions about dates, amounts, names, and what outcome I want. > - Then draft a concise, professional complaint letter I can send by email. > - The tone should be: calm, factual, firm, and respectful. Not emotional, not dramatic, not legalistic. > - The letter should be 3 - 6 short paragraphs, with clear structure: 1) who I am and what this is about, 2) what went wrong (with dates and amounts), 3) how this affected me, 4) what specific resolution I am requesting, and 5) a polite closing that sets an expectation for a reply. > - Use simple, plain English. I am in my [age range] and do not want trendy slang or corporate jargon. > - At the end, include a short bullet list of the key facts (dates, confirmation numbers, dollar amounts) so I can verify them before sending. > > Here is my rough description (it may be messy; you can ask follow-up questions): > > [Paste your story here in your own words - don’t worry about structure. Include: company name, dates, what you paid, what went wrong, who you spoke to, and what you’ve already tried.]

After the AI asks its questions and you answer them, add this as a follow‑up prompt:

> Using my answers and your understanding of the situation, please now draft the complaint email as described before. Then suggest 2 - 3 short subject lines that will increase the chance someone opens and reads it (for example, “Request for billing correction - Reservation [number]”).

Why this prompt works:

This works because you’re not asking the AI to “write a complaint” in a vacuum; you’re asking it to **interview you first**, then shape your real story into a structured letter. You’re defining the **tone**, **length**, and **sections**, which keeps it from drifting into dramatic or robotic language. The request for bullet-point facts at the end forces the AI to surface dates, amounts, and confirmation numbers so you can double-check accuracy.

One thing to watch out for

AI sometimes invents details to make a letter sound more polished - phrases like “as a loyal customer of 20 years” or “as per our conversation on [date]” when you never said those things. Read every line and delete anything that isn’t true. Also remember: this is not legal advice. For serious disputes (large sums of money, safety issues, anything that could end up in court), consider this a **first draft** and have a human professional review it before sending.


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 25: Smarter by Thursday Older → Issue 25: Smarter by Thursday
Bluesky
Powered by Buttondown, the easiest way to start and grow your newsletter.