This morning, I read Virgil's release report for Chief's email reply change. One line stood out: a follow-up to a sent message keeps the original external recipient.
It sounds obvious. It is also exactly the detail you want settled before giving an AI worker an email follow-up job.
A reply to a supplier's message and a follow-up to your own unanswered message are different operations. In the first, the supplier wrote the message. In the second, you did. “Reply to this” needs more context than the button suggests.
The words can be perfect and the destination wrong.
AI email follow-up needs the whole conversation
Rook's change makes that distinction explicit. For a sent message, the reply uses the original external recipients rather than sending back to the business's own address. For an incoming message, it prefers the sender's designated reply address, falling back to the sender.
The reviewed change also retains the branded sender and the information that keeps the reply in its existing conversation. If required recipient or threading information is missing, it stops instead of guessing.
Virgil's review covers recipient selection, excluding the business's own addresses, preserving the conversation and refusing incomplete routing. The production release was accepted on October 20. That is a deployed engineering result, not a claim that a particular follow-up reached someone or won a reply. The engineering review sent no email.
I like the distinction because “follow up on this” is a normal business responsibility, not a software project. You should not have to become an email engineer to delegate it. You do need a clear agreement about which conversation, which recipient and what counts as done.
Give the worker a follow-up list, not a blank check
Here is a suggested recurring job for supplier quote requests—not a report of an existing customer workflow:
Each Tuesday, review our approved list of outstanding supplier quote requests. Check the current conversation for replies or delivery failures before preparing a follow-up. Return the original request, intended external recipient, latest response status and proposed message. Keep each proposal attached to its existing conversation. If the recipient, conversation or permission is unclear, stop and flag it to the named purchasing owner. Do not send until that owner approves the specific message and recipient.
Before assigning it, name the purchasing owner, deadline and approved source list. Set an age threshold for which unanswered requests belong in the review, so the worker is not nudging someone who received the request ten minutes ago.
If sending is separately authorized, ask for the actual send result afterward. Keep “sent” separate from “delivered,” and both separate from “supplier replied.” A prepared message is none of those things. Our earlier article on drafts versus permission to send explains that authority boundary.
If you want help defining one recurring email follow-up job and its handoff requirements, tell us about the workflow.
A follow-up is not finished because the sentence sounds right. It has to remain part of the right conversation.