Email Approval Gate
How Coppermind handles outbound emails -- every draft is shown for your review before it goes out.
Why This Exists#
Coppermind can draft and send emails on your behalf: follow-ups after meetings, client updates, nurture sequences, introductions. That is powerful, but sending a message you have not reviewed to a client is a risk no CMO should take.
By default, Coppermind shows you every outbound email before sending it. You see the full draft -- recipient, subject line, and body -- and nothing sends until you approve it.
How It Works#
When Coppermind prepares an email (via /cmo-write, /cmo-write, or any workflow that involves sending), you see the complete draft:
To: alice@acme.com
Subject: Follow-up: Q2 campaign timeline
Hi Alice,
Following up on our call this morning...
You then approve or edit:
- "Send it" / "Looks good" / "Approved" -- Coppermind sends the email as shown.
- "Change the subject to..." or "Make it more concise" -- Coppermind revises the draft and shows it again for approval.
- "Don't send" or "Cancel" -- Nothing is sent.
This applies to every outbound email, whether it is a one-off follow-up or part of a batch sequence. No exceptions by default.
Turning Off Approval#
If you trust the AI drafts and want emails to go out automatically (for example, routine follow-ups and status updates), you can turn off the approval gate entirely. This is a global setting on your personal mind -- it applies to all clients at once.
"Turn on auto-send emails"
This sets email_auto_send to true in your personal mind's preferences. To turn it back on:
"Turn off auto-send emails"
This is a global setting, not per-client. When auto-send is on, all outbound emails across all clients skip the approval step. When it is off (the default), all emails require your approval before sending.
When to Use Auto-Send#
| Scenario | Recommendation |
|---|---|
| High-stakes client emails (proposals, strategy updates) | Keep approval on (default) |
| Routine follow-ups and status updates across all clients | Consider auto-send |
| Nurture sequences you have already reviewed | Consider auto-send after reviewing the first few |
| Early in your Coppermind usage | Keep approval on until you trust the drafts |
Checking the Current Setting#
Every time you switch to a client, the response includes _email_policy so you always know whether approval is active. If the policy says require_approval, every email draft is shown before sending. If it says auto_send, emails go out immediately.
You can also ask directly:
"Is auto-send on?"
Key Details#
- Default is always approval required. The setting starts as
falseand requires an explicit opt-in to turn on auto-send. - The setting lives in your personal mind. It is a global CMO preference, not per-client. One toggle controls email behavior across all clients.
- All email channels are covered. Whether sending via Gmail MCP, Google Workspace, or any future email integration, the approval gate applies.
- Batch sends are also gated. If a workflow generates five emails, each one is shown for approval (unless auto-send is on).
- To change the setting, switch to your personal mind and use
mind(preferences={"email_auto_send": true}). Or just say "turn on auto-send emails" and Coppermind handles it.
Ready to try this yourself?
Coppermind is free to start and runs inside Claude. Your first meeting prep will convince you.
Try Coppermind Free