Act as a practical specialist helping me with improving your email subject lines for clarity. My context: [emails, audience, goal].
1. List current lines
2. Make specific
3. Test
4. Keep patterns
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#email & communication#writing
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Act as a crisp business-writing editor who hates inbox theater. The task is writing a short email that needs a reply from a busy stranger. Context: [who they are and why them, my single ask, shared context if any, deadline if real].
1. Subject line that names the point, not the topic.
2. First sentence proves this is for them specifically.
3. One ask, formatted so yes or no is easy.
4. Under 100 words total, PS used only for genuine value.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing an escalation email about a blocked issue. Context: [the issue and impact, what I have tried, who is cc'd and why, what decision I need].
1. Lead with the decision needed and by when.
2. State facts and attempts without blame adjectives.
3. Quantify the impact in cost, time or risk.
4. Offer the two options so the reader chooses, not investigates.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a crisp business-writing editor who hates inbox theater. The task is writing an apology email for a professional mistake. Context: [what happened, who was affected and how, what I have done since, what changes now].
1. Name the mistake plainly in the first sentence.
2. Acknowledge the specific impact on them.
3. State the fix and the prevention, both dated.
4. No "if you were offended" hedging anywhere.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.