KoltrixThe cc and bcc rules every team should agree on
When to cc a teammate, why bcc backfires, how to leave a thread politely, and what to do when a customer copies half their company. A team FAQ you can adopt.
On this page(10 sections)
- What does cc actually mean on our team?
- When should I cc a teammate on a customer email?
- Should we cc the shared address on replies?
- Why is bcc risky?
- How do I leave a thread politely?
- A customer cc'd ten people from their company. Now what?
- When is reply-all the wrong choice?
- Should internal discussion ever happen on the customer thread?
- Can we write this down in five lines?
- Bottom line
Most email mix-ups inside a team don't come from bad writing. They come from the cc and bcc fields, which everyone uses slightly differently and nobody ever wrote down.
This FAQ covers the questions small teams actually argue about. Read it, change the answers that don't fit your team, and paste the result into your team handbook.
What does cc actually mean on our team?
Cc should mean one thing: "you need to know this, but you don't need to act." The person in the To field owns the next step. Everyone in cc is informed.
When people cc someone because they hope that person will act, threads stall. The cc'd person assumes the To person has it; the To person assumes the cc'd person is the real decision-maker. Nobody moves.
A practical rule: if you need something from someone, put them in To and say so in the first line. "Priya, can you confirm the renewal date by Thursday?" is unambiguous. A silent cc is not.
When should I cc a teammate on a customer email?
Cc a teammate when at least one of these is true:
- They will take over the conversation soon, and you want the customer to see the handoff.
- They made a commitment earlier in the thread and should see it being kept.
- The customer asked for them by name.
- They are the escalation point and you're telling the customer so.
Don't cc teammates as a status update ("FYI, handling this"). That belongs in your internal chat with a link to the thread, not in the customer's inbox. Every extra internal name on a customer email makes your company look bigger and slower than it is.
Should we cc the shared address on replies?
If you reply from the shared address (support@, hello@), there's no need: the conversation already lives there. The problem shows up when someone replies from their personal address and the shared mailbox loses the thread.
Agree on one of two patterns and stick to it:
- Reply from the shared address, always. History stays in one place, and the customer replies back to the team.
- Reply personally, cc the shared address. Acceptable for sales or account conversations where the customer expects a named person, as long as the shared address stays on every message.
Mixing the two is what causes "I never saw that email" a week later.
Why is bcc risky?
Bcc hides recipients from each other. That sounds tidy, but it creates three common accidents:
- The bcc'd person hits reply-all. Now everyone sees that they were silently copied, and the original sender looks like they were hiding something.
- Nobody knows who knows. If your manager was bcc'd on a tense customer email, the customer has no idea, and the next teammate on the thread might not either.
- Replies don't reach the bcc'd person. When the customer replies, the bcc'd person drops off the conversation, which is often not what you intended.
Use bcc for a narrow set of cases:
| Situation | Use bcc? | Why |
|---|---|---|
| Announcement to many external recipients who don't know each other | Yes | Protects their addresses from each other |
| Introducing two people, then stepping out | Yes, yourself to bcc | Lets you leave the thread politely |
| Quietly showing your manager a tense customer email | No | Forward it internally instead |
| Archiving a copy to a shared mailbox | Usually no | Cc it openly or reply from the shared address |
| Notifying a teammate without the customer knowing | No | Use internal chat with a link |
For large announcements, a proper sending tool is better than bcc anyway, because it handles unsubscribes and individual delivery.
How do I leave a thread politely?
The "move me to bcc" pattern is the cleanest way out of an introduction or a thread you no longer need to follow:
Thanks, Sam. Moving Dana to bcc to spare her inbox; you two are in good hands.
Moving someone else to bcc should only happen when the thread is clearly done with them, like after an introduction. Removing a teammate from a live thread without saying so looks like you're cutting them out.
If you want to leave a thread that isn't an introduction, a short line works: "I'll drop off here; Alex owns this from now on." Then actually stop replying.
A customer cc'd ten people from their company. Now what?
When a customer copies their boss, their colleagues and sometimes their procurement team, slow down before you reply.
- Reply-all by default. The customer chose that audience. Dropping people can look like you're avoiding scrutiny.
- Write for the widest reader. Assume the most senior person on the cc line reads only your first two sentences. Put the answer or the status there.
- Don't add your own crowd to match. If they cc'd ten, you don't need to cc five teammates. One owner replying clearly beats a wall of names.
- Move side discussions out. If one person on the cc line asks something narrow, reply to them directly and say so in the thread: "Answering Lee's billing question separately."
When is reply-all the wrong choice?
Reply-all is right when everyone on the thread needs your reply. It's wrong when:
- You're only saying "thanks" or "+1".
- You're answering one person's side question.
- The thread includes a large distribution list and your reply only matters to the sender.
- Someone was added by mistake, and your reply would broadcast the mistake further.
A rough test: would everyone on the line be annoyed or grateful to get this? If you can't say "grateful" for most of them, trim the list.
Should internal discussion ever happen on the customer thread?
No. Once a customer is on a thread, everything in that thread is customer-facing, including the quoted history at the bottom. A teammate's "this customer is a pain, just refund them" quoted at the bottom of your reply is a mistake that's hard to undo.
Keep internal back-and-forth in a separate channel and link to the thread. If you have to forward a customer email internally, start a new internal message and double-check the To field before sending.
Can we write this down in five lines?
Yes. Here's a version you can paste into a handbook:
Our cc/bcc rules
1. To = owns the next step. Cc = informed only. Ask for actions by name in line one.
2. Reply from the shared address, or keep it in cc. Never drop it.
3. Bcc only for mass external notes and for stepping out of introductions.
4. Reply-all when the customer chose the audience; trim when you're answering one person.
5. No internal discussion on customer threads. Use chat with a link.
Revisit it after a month. If people keep breaking one rule, the rule may not fit how you work, so change it rather than repeating it louder.
Bottom line
- Cc informs; To assigns. Name the person you need something from in your first line.
- Keep the shared address on every customer conversation, either as the sender or in cc.
- Treat bcc as a narrow tool: mass announcements and polite exits from introductions.
- When customers cc a crowd, reply-all, lead with the answer, and resist matching their headcount.
- Write your rules down in a few lines, then adjust them based on what actually goes wrong.
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.
