The one-page letter that actually works

Today's Tip: The Complaint Letter That Works

The complaint letters that get fixed aren't the angry ones… they're the specific ones.

Let me explain…

Marvin Keller spent 40 years as a small-business accountant in Louisville, Kentucky. He knows how to write a tough letter. Last month he and his wife Jeanette flew out to see their grandkids in Denver. The airline lost both suitcases for four days.

Marvin wrote the airline. He was mad, and he said so. Two paragraphs, strong words, a demand for compensation. He got back a form email thanking him for his feedback and offering a token voucher.

Then he tried something different. He opened Claude and typed the whole mess in… the flight number, the dates, the exact items in each bag, what they spent to replace essentials, what the airline's own written policy says about delayed baggage, and the tone he wanted — firm but professional, not angry. Claude drafted a one-page letter he could barely improve on.

Marvin sent it. Within 48 hours, a representative from the airline called him directly. They paid for everything the couple had replaced, refunded part of the ticket, and credited him for a future trip.

Same complaint. Different letter. Different result.

Here's the prompt that does it…

Marvin told me the letter Claude drafted sounded exactly like something he could have written on his best day. Only it took him 15 minutes instead of two hours… and it worked.

Notice what he did. He didn't ask Claude to "write a strong complaint letter." That's a vague prompt and you'd get a vague letter back. He gave it the facts, the policy, the amounts, and the tone. He loaded the gun.

That's what Claude is best at — taking the raw material you give it and shaping it into something that reads clean and lands hard.

I know what you're thinking… "Won't the company notice I used AI?" They might. They don't care. A company's complaint desk sees hundreds of letters a week, and they've never turned down a valid claim because the writer used a word processor to check the spelling. This is the same thing.

What they care about is whether you've given them a reason to settle quickly. The clearer your facts, the easier that decision becomes.

If you have a complaint sitting in a drawer because you don't know how to write it, pull it out this week. Open Claude. Give it the facts. See what comes back.

The worst that happens is you still have a complaint. The best that happens is a check in the mail.

★ Quick Wins

Skill Builder: Writing Specific Prompts

The single biggest skill in getting good answers out of AI isn't a secret trick… it's specificity. Vague in, vague out. Specific in, specific out.

Here's what I mean. Compare two prompts.

Prompt A: "Help me plan a trip to Nashville." Prompt B: "Help me plan a four-day trip to Nashville in late March for me and my sister, both 64. We love live music and good breakfast spots. We don't drink. We want to walk as much as possible. Budget is modest. Give me a day-by-day plan with addresses and the best time of day for each stop."

Prompt A gets you a tourist brochure. Prompt B gets you something you could print out and follow. The difference is five minutes of your time at the keyboard — and it works in Claude, in Gemini, in Grok, and in every tool that comes after them.

The trick is to think of your prompt the way a good secretary would brief a boss. The boss needs: who the answer is for, what the goal is, what the constraints are, and what the final output should look like. Give the AI the same brief, and you get a different grade of answer.

Try it this week. Pick any question you'd normally type into the AI — a meal plan, a letter, a research question — and start with "Before you answer, repeat back what you heard." Watch what happens.

You'll find the AI is good at pointing out what you didn't tell it. And once it does, you'll start adding those details before you even hit send. That's the whole skill in a nutshell.