If you have ever looked at a road trip and thought, “This sounded simpler when we first discussed it,” or written a complaint that disappeared into a company’s customer-service system, this issue is for you. We are looking at two practical uses of AI: planning a road trip that suits real human energy levels, and writing a complaint letter that is calm, specific, and difficult to ignore.

AI is not a substitute for checking road conditions, confirming reservations, or knowing your consumer rights. But it can help you organize scattered information and turn a vague intention into a usable plan. 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

At 8:15 on Monday morning, Margaret Lewis, 62, was sitting at her kitchen table in Columbus, Ohio, with three browser tabs open and a yellow legal pad covered in arrows. She and her sister wanted to drive to Asheville, North Carolina, then continue to Charleston, South Carolina, for five nights. Margaret knew the broad route, but she did not know where to stop, whether six hours of driving in one day was sensible, or how to balance scenic detours with her sister’s bad knee. One website suggested an expensive hotel; another recommended attractions that added hours to the journey. Margaret did not need a dazzling vacation brochure. She needed a realistic plan with bathroom breaks, comfortable lodging, manageable driving days, and enough flexibility that one slow morning would not ruin the trip.

That is exactly the sort of organizing work AI can handle well. A sensible road-trip plan should include realistic daily mileage, regular breaks, weather and road-condition checks, and a backup option if a reservation or route fails. AAA similarly recommends mapping the itinerary, leaving time for stops, carrying an emergency kit, and avoiding overly ambitious driving days.

Here is the exact prompt to use:

Copy and paste this into ChatGPT or Claude:

> I am planning a road trip and want a realistic, comfortable itinerary rather than an exhausting list of attractions. > > Trip details: > - Starting city: Columbus, Ohio > - Destination: Asheville, North Carolina, then Charleston, South Carolina > - Total length: 5 nights, traveling in September > - Travelers: two adults, ages 62 and 64 > - Driving preference: no more than 4.5 hours of driving on any day, excluding stops > - Health and comfort needs: one traveler has a bad knee, so include frequent restroom and short-walk breaks; avoid steep hikes and activities requiring long periods of standing > - Interests: scenic drives, gardens, historic neighborhoods, independent restaurants, and small museums > - Budget: moderate; avoid luxury hotels > - Lodging preference: clean, quiet hotels with parking, elevators, and strong recent guest reviews > - Food needs: one traveler avoids very spicy food > > Create a day-by-day itinerary. For each day, include the approximate driving time, suggested break locations, two or three possible activities, a practical lunch or dinner idea, and a backup plan for rain or fatigue. Separate essential stops from optional detours. Flag anything that may require advance reservations. > > Do not invent exact hotel availability, opening hours, ticket prices, or road conditions. If current information is needed, tell me exactly what I should verify. At the end, provide a packing and preparation checklist, including vehicle checks, medications, emergency supplies, printed information, and a short list of questions to ask before booking lodging.

Why this prompt works: It gives the AI the information that changes the answer: dates, ages, driving limits, mobility needs, budget, interests, and lodging requirements. It also tells the system what not to pretend to know. The request for “essential,” “optional,” and “backup” plans turns a wish list into a decision-making tool. Most importantly, it asks for a practical itinerary rather than the longest possible list of attractions. AI is much more useful when you define what a successful day feels like.

Use Case 2 of 2

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

At 6:40 on Wednesday evening, David Chen, 57, was standing beside his washing machine with a folder of receipts in one hand and his phone in the other. A repair company had replaced a part three weeks earlier and charged him $486. The machine was now leaking again. David had already made two phone calls. The first representative promised someone would call back. The second said the warranty “might not cover it,” but could not explain why. David was angry, but he knew that a letter filled with anger might make it easier for the company to dismiss him. What he needed was a short record of what happened, what he had already done, what he wanted, and when he expected an answer.

A good complaint letter is not a speech about how badly you were treated. It is a compact case file. Consumer guidance recommends identifying the product or service, describing the problem clearly, stating the remedy you want and a response deadline, and including copies of relevant documents rather than sending original paperwork. Formal complaints can also create a useful paper trail before you escalate to a consumer-protection office or another appropriate agency.

Here is the exact prompt to use:

Copy and paste this into ChatGPT or Claude:

> Help me write a firm, professional complaint letter to a company. Use plain English, a calm tone, and no insults or exaggerated claims. Keep it under 350 words. > > Company name: [COMPANY NAME] > Company address or email: [ADDRESS OR EMAIL] > My name: [YOUR NAME] > My address and contact information: [YOUR CONTACT INFORMATION] > Product or service: [DESCRIBE IT] > Purchase or service date: [DATE] > Order, invoice, account, or model number: [NUMBER] > Amount paid: [AMOUNT] > What went wrong: [DESCRIBE THE PROBLEM IN CHRONOLOGICAL ORDER, INCLUDING DATES] > What I have already done: [LIST CALLS, EMAILS, REPAIR VISITS, AND NAMES OR JOB TITLES IF KNOWN] > Documents I can attach: [RECEIPT, WARRANTY, PHOTOS, WORK ORDER, EMAILS, ETC.] > What I want the company to do: [REFUND, REPAIR, REPLACEMENT, CANCELLATION, OR OTHER SPECIFIC REMEDY] > Response deadline: [DATE OR NUMBER OF BUSINESS DAYS] > > Write the letter with: > 1. A clear subject line. > 2. A first paragraph identifying the purchase or service and the central problem. > 3. A brief timeline with the important dates. > 4. A specific request and reasonable deadline. > 5. A sentence saying that copies of supporting documents are attached. > 6. A closing that explains I will consider further escalation if the matter is not resolved, without making a legal threat. > > Do not invent facts, laws, warranty terms, conversations, or deadlines. If any information is missing, put [NEEDS INFORMATION] in the draft instead of guessing.

Why this prompt works: It forces the letter to answer the questions a company needs answered: What was bought, when did the problem occur, what evidence exists, and what resolution is being requested? The chronological structure makes the facts easier to follow, while the word limit prevents the central request from being buried. Telling AI not to invent facts is essential. So is asking for a specific remedy and deadline; “Please fix this” is much weaker than “Please refund $486 or arrange a no-cost repair by May 20.”