The prompt
Score 10 of 10, Excellent
Use it when The year is ending and you want to thank customers with a short look back, built from real figures and their own activity where you have it.
- {{company}}
- {{year_facts}}
- {{merge_fields}}
- {{next_year}}
- {{signer}}
Full prompt and why it works
Prompt
Write a year-in-review email from {{company}} to our customers, so that they feel thanked for a year with us, see what we actually delivered for them and know what is coming next, in an email short enough to read on a phone. What happened at the company this year (what shipped, improvements, milestones, with dates and figures): """ {{year_facts}} """ Customer-level fields our email platform can fill in, if any: {{merge_fields}} What is confirmed for next year: {{next_year}} Signed by: {{signer}} Produce: 1. Two subject lines and one line of preview text. 2. The email, 200 to 300 words: thanks in the first two lines; the year in four or five short bullets, each one real thing from the facts; a "Your year with us" block that uses the merge fields in brackets, for example [orders this year]; what is next, only what is confirmed; a sign-off from {{signer}}. 3. Fallback lines: for each merge field, what the email says instead when the value is empty or zero, so that a customer with little activity does not get a line such as "You saved 0 hours." 4. A plain-text version of the "Your year with us" block. The tone should be warm and specific, like a note from people who know their customers, not a press release. Avoid hype words such as "incredible" and "amazing". Use only the figures in the facts and the merge fields. Do not round numbers up, combine figures into new totals, or announce plans that are not confirmed. Each customer's numbers appear only in their own email. If a fact has no figure or date, describe it without one rather than estimating, and if there are no merge fields, leave out the personal block and say so at the top.
Variables
- {{company}}
- Your company or product name.
- {{year_facts}}
- What happened this year: releases, improvements, milestones, with dates and figures you have confirmed.
- {{merge_fields}}
- Customer-level fields you can insert, for example orders this year, hours saved or member since, or "none".
- {{next_year}}
- Plans for next year that are confirmed and can be announced, or "nothing to announce yet".
- {{signer}}
- Who signs it, with their role.
Why it works
- If unsure. Every merge field gets a fallback line for empty or zero values, so a customer with little activity never reads "You saved 0 hours."
- What to avoid. Only real figures appear, nothing is rounded up or combined into new totals, and only confirmed plans are announced.
- Length. Four or five bullets and 200 to 300 words keep it readable on a phone.