Look through your sent folder and a pattern emerges: you write the same fifteen messages over and over. The meeting reschedule. The polite decline. The "checking on that invoice." The onboarding welcome. Each one composed from a blank page, each costing five minutes and a little decision fatigue. Templates fix this — if they're built and used well.
Find your recurring fifteen
Don't invent templates speculatively; mine your actual history. Scan the last two months of sent messages and list every situation that appeared three or more times. Typical harvests:
- Scheduling: proposing times, rescheduling, confirming
- Chasing: unpaid invoices, unanswered questions, overdue deliverables
- Declining: meeting invitations, vendor pitches, scope additions
- Announcing: delays, releases, policy changes
- Relationship: welcomes, thank-yous, introductions, hand-offs
The list is the insight. Most professionals discover that under twenty situations cover more than half their outbound writing.
Build the skeleton, not the corpse
A good template is a structure with slots, not a finished letter. Finished-letter templates produce that unmistakable mail-merge deadness — recipients smell it instantly. The template should fix the shape and leave the humanity to fill in:
Invoice chase, first touch Subject: Invoice [#] — [amount], due [date] Hi [name] — flagging that invoice [#] for [amount] was due on [date]. Could you check where it sits in your process? If it's already moving, ignore me entirely. [One personal line.] Thanks!
The bracketed personal line is load-bearing. One genuine sentence — referencing the actual project, the actual last conversation — converts a form letter back into a message.
Templates encode judgment, not just words
The real value of a good template is that the thinking is pre-done: the decline template is firm without apologizing three times; the delay announcement leads with impact and next update, because someone decided it should. This is why templates deserve editing like product copy — and why tone-critical ones benefit from a proper rewriting pass when you create them. Tools like Wrivio lean into exactly this pattern with reusable contexts: define the recurring situation once ("customer delay," "clear and firm decline"), then feed it each rough draft and get the situationally right tone applied consistently, with a diff to approve. Template thinking, without the frozen text.
Store them where you'll actually reach them
A template in a forgotten doc is a template unused. Working options, by team size:
- Solo: text expander snippets or your email client's built-in templates — the reach cost must be near zero.
- Team: a shared, versioned home. Teams that keep operational checklists in a shared tool like MyTeamTask often store message templates alongside the processes that trigger them — the invoice-chase template lives next to the invoicing checklist step that says to send it.
Review quarterly, prune ruthlessly
Templates rot: prices change, names change, the tone that fit last year's brand reads wrong today. A quarterly fifteen-minute review — which ones got used, which produced good responses, which now embarrass — keeps the library alive. And the ultimate test never changes: would you be comfortable if the recipient saw the template? If the personalization is doing so little that the answer is no, the template needs more slots and fewer sentences.
