KoltrixDrafting follow-ups with AI without sounding robotic
Before-and-after examples of AI-drafted follow-ups after silence, after a meeting and after a fix, with the edits that remove filler and add a clear next step.
On this page(7 sections)
- The three moves that fix most follow-ups
- Situation 1: No reply after a few days
- First draft
- Edited version
- A prompt that gets closer on the first try
- Situation 2: After a meeting
- First draft
- Edited version
- Situation 3: After a fix ships
- First draft
- Edited version
- Timing guidance
- Editing checklist for any AI follow-up
- Key takeaways
"Just circling back to see if you had a chance to look at my previous email." You've received this sentence hundreds of times, and AI drafting tools have learned to write it beautifully. That's the problem.
Follow-ups are where AI drafts sound most generic, because the model has seen millions of them and most of them were bad. The fix isn't to stop using AI for follow-ups. It's to know what a good follow-up contains, ask for it, and edit the draft with a few specific moves.
Below are three common follow-up situations, each with a typical first AI draft, an edited version, and what changed.
The three moves that fix most follow-ups
Every example below uses some combination of these:
- Delete the throat-clearing. "Hope you're well," "just checking in," "circling back," "wanted to follow up." The reader already knows it's a follow-up.
- Restate the one thing that matters. People don't reread your previous email. Put the key fact or question back in front of them.
- End with one concrete next step. A yes/no question, a specific time, or an action you'll take. Not "let me know your thoughts."
Situation 1: No reply after a few days
You sent a customer a fix for their configuration issue five days ago and asked them to confirm it worked. Silence.
First draft
Hi Taylor,
I hope this email finds you well! I just wanted to circle back on my previous message regarding the configuration issue you reported. I wanted to check in to see if you had a chance to try the suggested solution. Please don't hesitate to reach out if you have any questions or concerns. Looking forward to hearing from you!
Seventy words, and the only real content is "did the fix work?"
Edited version
Hi Taylor,
Did changing the redirect URL to the https version fix the login loop? If it's working, I'll close this out on Friday. If not, send me a screenshot of the error and I'll dig in.
What changed: the question is specific enough to answer in one word. The draft restates the actual fix, so Taylor doesn't need to scroll. And there's a clear default (closing on Friday) that makes not replying a valid answer.
A prompt that gets closer on the first try
Draft a follow-up to Taylor. No greeting filler, no "circling back."
Ask whether changing the redirect URL to https fixed the login loop.
Say I'll close the thread Friday if it's working, and ask for a
screenshot if it isn't. Under 50 words.
The more of the specific content you give the model, the less it fills the space with generic phrases.
Situation 2: After a meeting
You had a call with a prospective customer about a pilot. You agreed on a few points and owe them a summary.
First draft
Hi Sam,
Thank you so much for taking the time to meet with us today. It was great to learn more about your team and your goals. As discussed, we're excited about the opportunity to work together. Please find below a summary of our conversation. We look forward to the next steps and continuing our partnership!
All warmth, no summary. And "partnership" after one call is a stretch.
Edited version
Hi Sam,
Thanks for the time today. Here's what we agreed:
- Pilot with your support team (four people), starting the week of the 14th.
- We'll set up the shared mailbox and labels together on a 30-minute call.
- You'll check with IT about connecting your domain before then.
Does Tuesday or Wednesday next week work for the setup call?
What changed: the summary is actually a summary, in a format Sam can forward to colleagues. Commitments on both sides are visible. The ending is a question with two options, which is much easier to answer than an open-ended "let me know."
Situation 3: After a fix ships
A customer reported a bug three weeks ago. It's now fixed. This is one of the most valuable emails a support team sends, and AI drafts tend to bury it in corporate language.
First draft
Dear Jordan,
We are pleased to inform you that the issue you previously reported has been resolved in our latest release. We appreciate your patience and understanding throughout this process. Your feedback is invaluable to us as we continue to improve our product. Please let us know if you experience any further issues.
Accurate, but it reads like a form letter. Jordan may not even remember which issue this was.
Edited version
Hi Jordan,
Good news: the bug where CSV exports dropped rows with commas in the name is fixed as of this morning. Your past exports won't change, but anything you export from now on will be complete.
Thanks for the example file you sent; it's what let us reproduce it. Could you run one export and confirm it looks right on your end?
What changed: names the specific bug, explains what changes for the customer (and what doesn't), thanks them for something concrete, and asks for a quick verification that closes the loop properly.
Timing guidance
Good wording doesn't help if the follow-up arrives at the wrong moment.
| Situation | When to follow up | How many times |
|---|---|---|
| Waiting on a customer's confirmation | 3–5 business days | Once, then close with a note |
| After a meeting | Same day | Once |
| After a fix ships | As soon as it's live | Once, plus a check if they report problems |
| Prospect who went quiet | About a week | Twice at most, then stop |
| Invoice or payment issue | Per your billing process | Follow the schedule you've told them |
A second follow-up should add something new, such as a deadline, a different option or a useful resource, rather than repeating the first.
Editing checklist for any AI follow-up
- Deleted any opening line that only says "this is a follow-up"
- The key fact or question from the earlier email is restated
- There's exactly one clear next step
- No phrases you wouldn't say out loud to this person
- Shorter than the first draft
Key takeaways
- AI follow-up drafts default to generic filler because that's what most follow-ups look like.
- Give the model the specific content up front: the fact, the question and the next step.
- Edit with three moves: cut throat-clearing, restate what matters, end with one concrete action.
- Time follow-ups to the situation, and make each one add something new.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
