Every month we look at which outputs users save, star, or copy out of ToneCraft. Five email patterns show up again and again — and they are not what you would guess. Here they are, with the structure that makes each one work.

1. The cold outreach follow-up

Most cold emails fail because they are too long and ask for too much. The follow-up that converts is the opposite: short, specific, and low-friction.

Subject: Re: ToneCraft for Acme

Hi Jordan —

Bumping this once. If a 15-minute demo of our tone-aware rewriting tool would help you evaluate us before Q3, reply "yes" and I'll send a calendar link.

Either way, thanks for considering us.

— Maya

One question, one clear next step, no hedging. The single reply-word lowers the effort threshold dramatically.

2. The post-meeting summary

Meeting summaries get skimmed for action items — so burying them at the bottom is a productivity crime. Lead with decisions, then actions, then notes.

Subject: Summary: Pricing discussion (Jun 2)

• Decided: Move to per-seat pricing for the Pro tier.
• Owner / due: You — draft the migration FAQ by Friday.
• Next call: Thursday 10am to review the numbers.

3. The polite decline

Turning people down is a relationship skill. The template users save most: acknowledge the request, state the decline clearly (no "maybe"), and leave the door open on your terms.

Hi Sam — thanks for thinking of me. I don't have capacity to take this on right now, and I'd rather say that honestly than overpromise. If the timeline shifts, I'll reach out first.

4. The meeting request (with a reason)

"Let's grab coffee sometime" fails because it offers no reason to accept. The saved version names the topic and the value to the recipient:

Hi Dana — I'm rebuilding our onboarding emails and your work on lifecycle messaging came up twice in my research. Could I borrow 20 minutes this week to ask how you sequence that first-week series? Happy to share what we learn in return.

5. The apology / course-correction

The apology that lands is short, owns the specific miss, and states the fix. No "if there was any confusion."

Hi Marcus — I owe you an apology. I said the report would be with you by Tuesday and it wasn't. The corrected version is attached, and I've set a recurring Monday reminder so this does not happen again.

Steal the structure, not the words

The reason these templates get saved is the structure: one clear ask, a respectful close, and no filler. Paste any rough draft into ToneCraft, pick the Email preset, and the engine will restructure it along these exact lines — in your voice, not ours.