How to Write Farewell and Congratulations Emails Using AI

Why Generic Goodbye Messages Fall Flat

People can tell. That’s the whole finding, and it’s measurable: in Snappy’s 2026 Workforce Study of 1,500 US employees, personalization ranked as the number one thing that made recognition feel genuine — 73%, ahead of the thoughtfulness of the gesture at 57% and public acknowledgement at 36%. Only 32% said their company consistently gets appreciation right.

Translate that to your inbox. A message that could have been sent to anyone reads as effort you didn’t want to spend. One line of specificity flips it entirely.

The second version isn’t longer or more emotional. It’s just checkable. Someone reading it knows it was written about them, because nobody else could have received it. That’s the same reason AI drafts often land badly in difficult emails without sounding like a robot — the model fills the space with plausible warmth because you gave it nothing else to work with.

Most professionals overcorrect by writing longer. Wrong lever. A four-line message with one real detail beats a fifteen-line message made of adjectives, and the same principle runs through an onboarding welcome message at the other end of someone’s time with you.

The One True Detail Method

The One True Detail Method is simple: you supply one specific, verifiable fact about the person, and the AI builds the message around it instead of around adjectives. It’s the approach we teach at PromptPeakAI for any message where sincerity is the point, and it works because it moves the hard part — remembering something real — to the only participant who can actually do it. You.

Where does the detail come from? Not from the AI — it has never met your colleague. Spend ninety seconds before you open any tool and scan for one of these:

• A specific thing they fixed, caught, shipped, or rescued, ideally with a rough date.
• A habit: the first to reply on a Sunday, the one who always asked the awkward question in reviews.
• A moment you were personally on the receiving end of — they covered for you, trained you, unblocked you.
• A phrase they say so often it’s become a team joke.

One is enough. Two is plenty. This is the same discipline behind giving AI enough context anywhere else — the model’s output quality is capped by the specificity of what you hand it, and no amount of clever phrasing in the prompt substitutes for a fact. If you’ve used our approach for a thank-you email after an interview, this will feel familiar: same engine, warmer occasion.

Writing Farewell and Congratulations Emails Using AI

Here’s the full walkthrough on a leaver, because that’s the harder of the two. Four steps, roughly five minutes the first time. The congratulations version, in the next section, is the same machine with two settings changed.

Before you write anything, confirm the departure has been announced. Sending a farewell note to a wide list before the person’s manager has told the team is the one mistake in this whole process that AI cannot help you undo. If you’re the manager and the announcement hasn’t gone out yet, that’s a separate job — see internal announcement email first, then come back here.

Open a blank note, not the AI. Write the detail in plain, ugly words — “caught the invoice thing in March, saved us in the audit” is perfect. Do not polish it. Polishing is the machine’s job; remembering is yours.

Paste this into ChatGPT, Claude, Gemini, or Copilot. The bracketed slots are the only things you change.

Write a short farewell email to a colleague who is leaving.

Context:
- My relationship to them: [peer on the same team / their manager / someone in another department who worked with them occasionally]
- Their name: [first name]
- How long we worked together: [e.g. three years]
- The one specific thing I want to mention: [the detail, in your own rough words — a project, a save, a habit, a moment]
- Where they are going, if I should mention it: [new role / not mentioning it]

Rules:
- Under 120 words.
- Build the message around the specific thing above. Do not add achievements I did not give you.
- Warm and plain. No corporate phrases like "future endeavours", "truly missed", or "all the best in your next chapter".
- Write it as one person to one person. No sign-off block — I will add my own.

The negative constraints at the bottom do most of the heavy lifting. Left to itself, the model reaches for exactly the phrases you just banned, because they dominate the farewell emails it learned from.

Read the draft as though you were the recipient. If a sentence would be equally true about a different colleague, delete it. Then run one refinement pass:

Go through the draft and delete every sentence that could be sent to a different colleague without changing a word.

Keep only the lines that are specifically about this person. If that leaves the message very short, leave it short — do not pad it back out.

One email or several?

This trips people up more than the writing does. The answer is usually both, and the split is less work than it sounds because the detail work only happens once.

• A short note to the wide list — two or three lines, no inside references, safe for anyone to read. This is the one that goes to the department.
• Individual messages to the three or four people you actually worked with closely — each with its own true detail. These are the ones that get kept.
• Nothing at all to people you never worked with. A farewell email to a stranger is filler in their inbox, not a courtesy.

Run the prompt once per close colleague, changing only the detail slot. Four personal messages take about eight minutes total, and they are the entire reason anyone remembers you were decent to work with.

If you’re using Gmail on a personal account, you may also see Gemini’s writing tools sitting right in the compose window. Google’s support documentation lists which of those features are free versus plan-gated — Help Me Write and Suggested Replies rolled out to personal accounts in English, US first, so availability depends on your account and region.

Two related jobs often arrive in the same week as a departure: the employee offboarding checklist if you’re the manager, and sometimes a request for a reference letter a few weeks later. Different documents, same underlying discipline — specifics over adjectives.

Congratulations Emails for a Promotion

Congratulations messages fail differently. Farewell notes go generic; congratulations notes go inflated. The model reaches for “so well deserved” and “you’re going to smash it”, which is fine in a Slack thread and slightly hollow in an email the person will actually keep.

The fix is the same one true detail, pointed at evidence rather than memory: name the thing that made the promotion obvious.

Write a short congratulations email to a colleague.

Context:
- The occasion: [promotion to a new title / a formal award / a work anniversary / a new role at another company]
- My relationship to them: [peer / their manager / their former manager / someone senior to them]
- Their name: [first name]
- The specific thing that made this obviously deserved: [the evidence, in your own rough words]

Rules:
- Under 90 words.
- Lead with the congratulations, then the specific evidence, then one forward-looking line.
- Do not predict how they will perform in the new role. Do not say "well deserved" or "you deserve it" without the evidence attached.
- Plain and warm. Assume they will read it once and remember whether it felt real.

Promotions are the common case, but the rest of the calendar runs on the same prompt with one slot changed:

• Work anniversaries — the evidence is longevity itself, so name what changed on their watch rather than counting the years.
• A formal award or recognition — say what you saw them do, not what the award citation already said. They’ve read the citation.
• A new qualification — acknowledge the invisible part, which is a year of evenings, not the certificate.
• Weddings, babies, personal milestones — drop the evidence line entirely. Warmth and brevity only, and never comment on plans or timelines that aren’t yours to discuss.

That last one has a hard edge to it. Professional milestones invite specifics; personal ones invite restraint. A congratulations note about someone’s private life should be shorter than one about their promotion, not longer.

If Outlook is your inbox, Copilot’s drafting controls sit in the new-message toolbar. One caveat that catches people out: Microsoft’s support documentation restricts Copilot in Outlook to work or school accounts and Microsoft accounts on outlook.com, hotmail.com, live.com, or msn.com — a Microsoft account tied to a third-party address like Gmail can use Outlook but won’t see those Copilot controls.

Matching Tone to the Relationship

The same detail needs three different wrappers depending on who’s sending it. Get this wrong and a perfectly accurate message still reads oddly — too familiar from a director, too stiff from the person who sat opposite you for four years.

If the draft came out at the wrong register, don’t rewrite it by hand. Re-aim it:

The draft is pitched wrong for the recipient.

This is going to: [my direct manager / a peer I worked with daily / someone in another department I barely know].

Rewrite it at that register. Keep the specific detail exactly as it is — only change the warmth, the formality, and the length.

Getting the register right matters most when there’s history in the room. If the departure is awkward — a redundancy, a resignation you know the backstory of — the tone work in preparing a difficult conversation applies here too.

What to Never Paste Into AI

This is the part most guides skip entirely, and it’s the part that can actually cost you. To personalize a message you have to describe a real person’s real circumstances to a chatbot — and some of those circumstances aren’t yours to share.

A quieter version of the same rule: don’t name someone’s new employer in a message going to a wide internal list unless they’ve said it publicly themselves. That one is etiquette rather than data protection, but it burns people just as often.

When AI Gets These Emails Wrong

Four failures cover nearly everything that goes wrong here. Each has a fix that takes one message, not a rewrite.

The invented-achievement one deserves a flag of its own. A model that confidently credits your colleague with leading a project they never touched will produce a message that reads beautifully and embarrasses everyone who knows better. Read every draft against what you actually know before it leaves your outbox.

List every factual claim in this draft as a bullet point — every achievement, project, date, and contribution you attributed to this person.

Do not rewrite anything. I want to check each claim against what I actually know before I send it.

If the output keeps drifting back to stock phrasing after two attempts, the problem is usually upstream in how the request is framed rather than in the editing — the techniques in refining AI output handle that pattern generally.

When to Skip AI Entirely

Honestly, sometimes you should just write it yourself. The method above earns its keep on the messages you’re stuck on — not on every message.

One question people ask quietly: will the recipient know? If you supplied the detail and cut the filler, no — because the only genuinely detectable part of an AI draft is the generic part, and you removed it. If you sent it raw, quite possibly yes, and increasingly so as people get better at spotting the house style.

The messages worth sending are the ones that keep a relationship alive past the leaving date, which is its own small skill — staying in touch after they leave covers what happens next. If you’d rather start from something pre-built, the free AI work templates include starting points you can adapt. Either way, the detail is still yours to remember.