AI for Email

A live class taught by Claude, operated by you

Clear the inbox without sounding like a robot

THE FORMAT

You open the room and introduce the class. Claude teaches the entire session aloud through a speaker. You relay audience questions back to Claude by repeating them clearly. You close.

You are the operator, not the co-teacher. Claude runs the content.

Room setup checklist

• A speaker that the whole room can hear, paired to the phone or laptop running Claude. Test it in the actual room beforehand.
• A microphone position near you so Claude can hear the room when you repeat questions.
• One or two volunteers with a real email on their phone that they need to answer. Ask for them when people arrive, not during the class. Tell them to leave out names and anything private.
• A backup email, in case nobody volunteers. Write a short invented one: a neighbour complaining about a fence, or a club member asking for a refund. You will read it aloud in Block Four.
• The running order visible to you, so you can jump blocks if time runs short.

The operator's opening (thirty seconds)

Say who you are. Say what the room is about to see. Say plainly that the teacher tonight is an artificial intelligence, and that the subject is email. Tell them a real email from the room will be used in the middle of the class. Then hand off: "Alright, take it from here."

The operator's close

Thank the room. Announce the next date. Give one place to find more. Remind them of the homework from Block Six.

THE RUNNING ORDER — SEVEN BLOCKS, SEVENTY-FIVE MINUTES

Block One — What it can and cannot do with email — five minutes
Block Two — Why AI emails sound like robots — ten minutes
Block Three — Four jobs for your inbox — ten minutes
Block Four — Live demonstration — fifteen minutes
Block Five — Where it breaks — ten minutes
Block Six — What to do tomorrow morning — ten minutes
Block Seven — Questions and answers — fifteen minutes

The class is free. Its job is to make email less of a chore, and to get people past their hesitations. Block Seven is where that last part happens.

BLOCK ONE — WHAT IT CAN AND CANNOT DO WITH EMAIL

Opening question to the room: "Roughly how many unread emails are in your inbox right now? Be honest. Call out a number."

Expect: a few embarrassed laughs, and someone in the thousands. Thank them. Say that nobody in this room is the only one.

The core teaching:

I am a prediction machine. I have read a huge amount of writing, including a huge number of emails. When you ask me for an email, I write what a good email in that situation tends to sound like.

That makes me good at three things. I can write a first draft. I can rewrite something you already wrote. And I can read a long email and tell you what it says.

Here is what I cannot do. I do not know your people. I do not know what you promised last week. I do not know that your sister hates being called "Dear Sister". Only you know the facts. I only supply the words.

Second question to the room: "Who here has already asked one of these tools to write an email? What did you think of it?"

Typical answer: "It worked but it sounded stiff." Tell them that is exactly what Block Two fixes.

The line to land: I write the words. You supply the facts, and you press send.

BLOCK TWO — WHY AI EMAILS SOUND LIKE ROBOTS

Opening question to the room: "Have you ever got an email and thought, a machine wrote this? What gave it away?"

Expect: "I hope this finds you well." Too long. Too cheerful. Lots of exclamation marks. Nobody says anything specific.

The core teaching:

You are right about all of that, and here is why it happens. If you say "write an email to my neighbour about her bins", I have almost nothing to go on. So I write the average email about bins. The average email is polite, padded and vague. Nobody talks like the average.

The fix is to give me more of you. Four things:

• Who it is going to, and how you know them.
• What you want to happen, and by when.
• How you would say it if they were standing in front of you.
• How long it should be.

Here is a real script to say to me:

"Write to my neighbour, who I get on with. I want her to move her bins off the pavement by Tuesday. Friendly, but direct. Plain words. Three sentences at most."

That gets you something you could send. The first version, with no detail, gets you something you would delete.

One more trick. If you have an email you wrote once and liked, paste it in and say "write like this." I copy the rhythm of real writing much better than I follow a description of it.

The line to land: Average in, average out. Give it you.

BLOCK THREE — FOUR JOBS FOR YOUR INBOX

Opening question to the room: "If a helper could take one chore off your email, which would it be? Writing, replying, reading, or sorting?"

Take a few answers. Whichever they pick, it is one of the four jobs.

The core teaching:

First: draft from rough notes. Type what you mean in scrappy bullet points. "Can't make Thursday. Can do Friday morning. Sorry for the late notice." I turn that into a proper message.

Second: rewrite what you wrote. Paste your own draft and tell me what is wrong with it. "Make it firmer." "Make it warmer." "Cut it in half." You can ask for three versions and pick one.

Third: read it for you. Paste a long email or a whole thread. Ask: "What is being asked of me, and by when?" This is the biggest time saver.

Fourth: reply options. Paste the email you received and ask for three short replies: yes, no, and maybe. Pick one, edit it, send it.

A warning on the third job. When I summarise, I can drop a detail or get a date wrong. So ask me to quote the line where the deadline appears, and then check that line against the original email. Dates and amounts are the two things never to take on trust.

The line to land: Let it read for you, but check the dates and the amounts against the original.

BLOCK FOUR — LIVE DEMONSTRATION

This is the block that sells the class. Fifteen minutes.

The operator takes a real email from a volunteer and reads it aloud, clearly, into the speaker. Claude works it out loud so the room watches it happen.

Good tasks to steer toward:

• A reply someone has been putting off because it is awkward
• A long email nobody wants to read, to be summarised
• A message to a landlord, a neighbour, a school or a club that needs to be firm but polite
• A rough set of bullet points to be turned into a proper message

Tasks to avoid:

• Anything with medical details, bank details or passwords
• Anything involving another person's private business, spoken aloud in a room
• A legal dispute or a formal complaint where the wording could change someone's rights
• Anything that needs a fact Claude cannot verify in the room

The working order:

1. Ask the volunteer the four questions from Block Two: who, what, how, how long. Ask them out loud so the room hears the method. 2. Write the draft. Say the reasoning while you work: "I am keeping this short because you said she is busy." 3. Ask the volunteer: "Is that how you would say it?" It almost never is the first time. 4. Fix it. Make it shorter, change one word they hate, remove one line. 5. Read the final version aloud. The volunteer decides whether to send it.

Get caught on purpose. When you draft, fill in anything you were not told. A first draft will often contain something like "I will call you on Thursday." Stop and say it plainly: "I just promised a phone call on Thursday. You never told me that. I made it up because it made the email sound finished." Point out that if they had sent it without reading, they would have committed themselves to something they never agreed to. The room spots the invention in seconds, and that is the point.

Refuse one thing out loud. If anyone asks for something you cannot verify, do not produce it. Examples: the email address of a particular person, what a company's refund policy says, or whether the sender is legally allowed to do what they did. Say why: a plausible invention would look identical to the real thing, in the same steady voice. Then offer the checkable route. For an address, suggest the contact page on the organisation's own website. For a legal question, say where your help stops and a lawyer's begins, and offer to help write the question they would put to one.

Both of these beat any scripted explanation of the limits. Watching it get caught teaches more than being told it can be wrong.

BLOCK FIVE — WHERE IT BREAKS

Opening question to the room: "What is the worst thing that could happen if an email went out with your name on it and you had not read it?"

Take two or three answers. They will say the right things themselves.

Cover these:

• Invented promises and facts. You saw it in Block Four. I fill gaps with things that sound right. Read every line as if a stranger wrote it.
• Privacy. What you paste goes somewhere. Treat it like a postcard, not a diary. Do not paste anything you would not read aloud in this room. An email also contains other people's names and details, and they did not agree to that. If it is a work email, check your employer's rules first.
• Emotional emails. Condolences, apologies, a goodbye. The words I write for those will be correct and empty. Write the heart of it yourself. I can help you tidy it afterwards.
• Money, law and health. I can help you word an email to a bank, a landlord or a doctor's surgery. I cannot tell you what you are owed, what you are entitled to, or what a symptom means. That is for a lawyer, an accountant or a doctor. If the email could change your rights or your money, have a professional read it before it goes.
• Sending. Some tools can connect to your inbox and send for you. Do not let anything send an email you have not read. A mistake in a draft costs you a minute. A mistake in a sent email costs you much more.
• Long threads. In a very long conversation I lose the thread and start contradicting myself. Start a fresh conversation rather than fighting it.

The line to land: A mistake in a draft costs a minute. A mistake in a sent email costs a lot more.

BLOCK SIX — WHAT TO DO TOMORROW MORNING

Opening question to the room: "Is there one email you have been avoiding for more than a week? Do not say who it is. Just raise your hand."

Expect most of the room. Tell them that is tomorrow's email.

The assignment:

Tomorrow morning, take that one email and do these four things.

1. Write three lines in your own words. What happened. What you want. How you would say it to their face. 2. Give those three lines to the tool, with the four questions: who, what, how, how long. 3. Read the result aloud. Change anything you would never actually say. 4. Send it yourself.

Compare it to what you would have written. That is the whole homework.

A bonus for the keen. Find two emails you wrote and were pleased with. Paste them in and ask: "Describe how I write in a few sentences." Save that description. Next time, paste it in first and say "write like this." You will sound like yourself with much less editing.

The line to land: Start with the one email you are dreading. It is the easiest win in your inbox.

BLOCK SEVEN — QUESTIONS AND ANSWERS

Fifteen minutes minimum. Unstructured. This is not optional.

Why this block exists:

Everything before this is what Claude decided to teach. This block is where the room says what it actually came to find out. The thing a person is afraid of is rarely on anyone's outline. Hesitation gets dealt with here or it does not get dealt with at all.

How it runs:

The operator opens it: "Right, questions. Anything. Nothing is too basic."

The operator repeats each question back clearly so Claude can hear it over the room. Claude answers directly and short. If a question needs five minutes, that is fine, but do not let one person take the whole block.

Rules for Claude in this block:

• Answer the question actually asked, not the one you wish was asked
• Short answers. Two or three sentences unless they ask for more
• If you do not know, say so plainly. That models the whole lesson
• Do not oversell. A free class that oversells loses the room
• If a question is really a fear, name the fear before answering it

Questions to expect, and the honest answer to each:

"Will people know it was written by AI?" Sometimes, yes, especially if you send the first draft untouched. Padded, vague, over-friendly emails give it away. If you give it your voice and edit the result, it reads as you. And if the email matters, it should be yours in the end.

"Is it cheating or dishonest to use it?" For your own correspondence, it is a tool, like a spell checker or a friend who reads it over. At work or at school, ask what the rules are before you start. Some places have them. Do not guess.

"Is it reading my inbox?" Not unless you paste something in, or connect it to your email on purpose. If you do connect it, you are giving it access, so read what it asks permission for. If you are unsure, do not connect it. Pasting one email at a time works fine.

"Could it send something by accident?" Only if you have connected it and allowed it to send. If you have not, it cannot. If you have, keep it to drafts and press send yourself. That is the safest habit.

"Will I forget how to write?" Only if you stop reading what it writes. If you keep editing, you keep your hand in. Think of it as a first draft from someone who does not know you.

"I am not a good writer. Will it make me look foolish?" Fear named: you are worried your writing is not good enough. It is more likely to help than hurt, because plain and clear beats fancy. The risk is not looking foolish. The risk is sending something that does not sound like you.

"Can it write a legal letter or a formal complaint for me?" It can help you word one. It cannot tell you what you are entitled to, and a wrong claim in a formal letter can hurt you. If money or rights are at stake, have a lawyer or an advice service read it before it goes.

"Can you find me someone's email address?" Do not produce one. Refuse out loud and explain why: a plausible invention would look exactly like a real address, delivered in the same steady voice. Point them to the organisation's own website, and offer to help write the message itself.

"Which one should I use?" Pick one and learn it properly. Switching between four means learning none.

"Is it free?" Many have a free version with limits. Paid versions cost money every month. Start free, and pay only if you hit the limit and the help is worth it to you. Check the current price yourself, because prices change.

Then the operator closes: thanks the room, next date, where to find more.

THE ONE RULE

Let it write the words, but you supply the facts and you press send.

Every mistake in this class came from someone trusting a draft they had not read: an invented promise, a wrong date, a tone that was not theirs. If you read every line before it goes, the tool saves you time and costs you nothing.

RECOVERY NOTES — HOW TO JUMP BACK IN

If the audio drops, the session crashes, or Claude loses the thread mid-class, the operator can restart at any block by saying:

"We are teaching AI for Email. Pick up at Block Four, the live demonstration."

Claude does not need the earlier blocks re-explained. Each block above is self-contained.

If Claude starts drifting or repeating, say:

"Reset. Block [number]. Go."

HOW SOMEONE ELSE RUNS THIS CLASS

Simple route: open Claude, paste this entire file into the chat, and say "you are teaching this class, I am the operator, start at Block One." Works immediately, no setup.

Project route: create a Claude Project. Drop this file into the project knowledge. Add one custom instruction: "You teach this class aloud. The user is the operator and relays audience questions." Every conversation in that project then already knows the material and nothing needs re-pasting.

VERSION

Version one. Written October second, twenty twenty-six.

This version has not yet been run aloud. After the first run, note which moments land best. Expect the invented promise in Block Four and the refused email address in Block Seven to outperform the written material, and write them up more fully if they do.