Reply faster, still sound human — SMART GUIDE

A practical guide to handling routine messages in half the time — while still sounding like a person wrote them.

Scroll back through a month of your sent messages and something uncomfortable shows up.

Almost everything you wrote was a version of about four replies. The pricing answer. The scheduling answer. The scope answer. The polite no.

The cost was never typing speed. It was deciding the same things repeatedly.

Every message asks for a small judgment call you've already made dozens of times. That's what makes an inbox tiring — not volume, but repetition of thought.

Write those four properly once, and you've bought back an hour a week for the rest of the year.

Here's how to build them.

Don't write templates. Templates sound like templates, and people can tell within a line.

Write real replies in your own voice, with the specifics left blank. The way you'd actually say it, including the small human bits — the acknowledgement, the bit of warmth, the sentence that sounds like you.

Then leave gaps only for what genuinely changes. The name, the number, the date. If half the message is blanks, you've written a form, not a reply.

Store them two seconds away. Snippets, a pinned note, whatever you'll actually reach for. If finding the reply takes longer than typing it, you've built nothing.

If you want the complete set of workflows rather than assembling them one at a time, take a look here

LEARN MORE

Now the part that separates fast from generic.

● Never send a first draft you didn't write. Drafting help is good at structure and terrible at tone. Take the pass, then rewrite the opening and closing lines in your own words — that's where personality lives.

● Give it your own replies as the example. Feed it two messages you're proud of and it will match your rhythm far better than any instruction about "professional but friendly."

● Cut the throat-clearing. "I hope this email finds you well" is the clearest signal that nobody thought about the recipient. Start with the thing.

● Answer the question in the first two lines. Everything else is context. Most people bury the answer at the bottom and wonder why threads run long.

One tell worth knowing: if a message could have been sent to anyone, it reads like it was. One specific detail — their situation, their timeline, something they actually said — is the difference between fast and forgettable.