Support replies: answer first, explain second.
1. The answer, in one sentence.
2. The why or the steps, in one or two more.
3. What to do if it still doesn't work.
Put what they asked for at the top, not after the apology.
Which of your saved replies still opens with the apology?
On LinkedIn, swap duties for outcomes.
Examples:
"Managed the support inbox" → "Set up reply templates so the team answered faster"
"Handled onboarding" → "Rebuilt onboarding so new hires got set up in week one"
Have numbers? Add them. If not, say what changed.
Which of your lines reads like a duty?
Not sure how to lay out a newsletter? A simple skeleton for one issue:
Hook: one line on why this matters this week.
The idea: one tip, story or update, in 3 short paragraphs.
Call to action: one link, one ask.
Everything else waits for the next issue.
Which part of your last issue was weakest?
A headline we see all the time, rewritten for a meal-planning app:
Before: "Innovative solutions for modern teams." Button: "Learn more"
After: "Plan a week of dinners in one sitting." Sub: "Pick meals, get one shopping list." Button: "Plan my week"
Which of yours still sounds like the Before line?
You click a blog post about handling customer questions. Two ways it could open:
A: starts with a story.
B: starts with the answer.
Which one keeps you reading? Tell us in the comments, and why.
