Both CC and BCC work for logging emails to Recruiterflow, but they behave differently in one critical way: reply tracking. Use this guide to pick the right one for each situation.
Quick answer
Use CC when you want the full conversation - outbound email plus replies - logged to Recruiterflow.
Use BCC when you only need the outbound email logged, or when you want the logging address to stay invisible to the recipient.
CC vs. BCC at a glance
Feature | CC | BCC |
Outbound email is logged | ✅ Yes | ✅ Yes |
Replies are tracked | ✅ Yes (if logging address stays in CC on reply) | ❌ No |
Logging address visible to recipient | ✅ Yes, appears in CC | ❌ No, hidden |
Thread stitching in Recruiterflow | ✅ Yes | ❌ No |
When to use CC
You're scheduling an interview and expect back-and-forth replies you want on record.
You're negotiating an offer and want the full thread logged.
You want your manager or teammates to see the complete conversation in Recruiterflow without chasing the thread in your inbox.
Note: CC reply tracking depends on the recipient keeping the logging address in the CC field when they reply. Most email clients preserve CC recipients automatically, but it's not guaranteed. If the logging address gets dropped from a reply, that reply won't be captured.
When to use BCC
You're sending a one-way email - an offer document, job spec, reference request - and don't need replies tracked.
You don't want the candidate or client to see the logging address in the email.
You're sending to a group where the logging address in CC might look confusing or unprofessional.
The most common mistake
Recruiters often reach for BCC out of habit, it feels cleaner because the recipient doesn't see it. But then they're surprised when replies don't show up in Recruiterflow. If you need reply tracking, you need to use CC, not BCC.
There's no way to retroactively capture replies that were sent to a BCC'd email. The logging address has to be present in the CC field of each message it needs to capture.