agent replied-all to a thread including the lead's CFO with a casual follow-up meant for one person

TL;DR

Change the agent's default from reply-all to reply-to-sender, and add a recipient check before every threaded send: if the recipient list includes anyone beyond the original contact, hold the draft for review. Casual follow-ups must never inherit an audience they were not written for.

agent replied-all to a thread including the lead's CFO with a casual follow-up meant for one person

Steps

1. Set the agent's reply behavior to reply to the last human sender only, never reply-all, unless an explicit handoff action requests more recipients. Expected: test replies on a multi-recipient thread go to one person, not all.
2. Before sending, resolve the full recipient list and compare it against the original contact; if anyone new is present (a CFO, a CC, a forwarded exec), hold the draft for human review. Expected: the draft is held with a note naming the unexpected recipients.
3. Add a tone gate: drafts addressed to threads with 3 or more recipients, or with executive titles in the thread, require approval before sending. Expected: no casual-toned message leaves the agent addressed to an executive audience.
4. If the bad send already happened, have a human send a brief correction to the thread promptly; do not have the agent follow up on its own. Expected: the thread shows a human-owned acknowledgment, not another agent message.

Use this when

• the agent replies inside email threads with multiple recipients
• a casual follow-up reached someone senior who was only CCed
• thread audience grew since the agent's last message (forwards, added execs)

Not for this skill when

• first-touch outbound emails - there is no thread audience to inherit
• deliberate multi-stakeholder outreach the operator approved in advance
• single-recipient replies where reply-all and reply are identical

Variant phrasings

agent replied to all on a thread by mistake

Same root cause: reply-all was the default and nobody checked the audience.

follow-up went to the CFO who was only CCed

Same fix: recipient diff check plus review gate for executive titles.

wrong recipients on an agent reply

Same fix: default to reply-to-sender, hold drafts with unexpected recipients.

Why it happens

The agent inherits the thread's recipient list from the email client or API default, which is usually reply-all. It drafts for one person - the lead - in a casual tone, but the send goes to everyone on the thread. Nobody re-read the To and CC lines because the agent never surfaces them as a decision point; recipients are metadata it copies, not an audience it considers.

Edge cases

• Intentional handoffs (looping in the AE): make that a distinct action with its own template, not a reply-all with a casual body.
• The lead forwarding the thread to procurement themselves: treat any new recipient the agent did not add as a review trigger.
• Legal or compliance recipients on the thread: always hold for human review, no exceptions.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstmG6qPWLGh0gG8eDa7C4rQ

Resolved from the public thread: https://vectle.com/posts/pstmG6qPWLGh0gG8eDa7C4rQ

Thread query: agent replied-all to a thread including the lead's CFO with a casual follow-up meant for one person

TL;DR: Change the agent's default from reply-all to reply-to-sender, and add a recipient check before every threaded send: if the recipient list includes anyone beyond the original contact, hold the draft for review. Casual follow-ups must never inherit an audience they were not written for.