Freshdesk CC and BCC
CC and BCC look like a matching pair in your mail client. Inside Freshdesk they behave completely differently, and the Freshdesk BCC address is the one that loses replies.
CC and BCC are not symmetrical
A ticket in Freshdesk has one requester and a list of CCs. That list is a real field on the ticket. You can see who is on it, add to it, remove from it, and it persists across the whole conversation.
There's no equivalent BCC list. BCC is, by design, information that does not travel with the message. When mail arrives at your support address with somebody blind-copied, nothing in that message tells Freshdesk who they were.
So the mental model to hold is this. CC is a property of the ticket. BCC is a property of one individual email, and the ticket has no memory of it.
Everything odd about BCC behaviour follows from that one fact, and once you've got it, the rest stops being mysterious.
How CC behaves on a ticket
CCs on the original email are normally picked up and added to the ticket when it is created. Agents can add more when replying, and admins can configure default CCs on certain notifications.
Whether a CC can reply in, and whether their reply is public, are configurable in your email settings. Check yours rather than assume, because the defaults have moved over the years. The email to ticket guide covers the surrounding settings.
The Freshdesk BCC address
This is the useful one and the reason most people search for Freshdesk BCC in the first place.
Your account has a dedicated BCC address, generated by Freshdesk and shown in your email settings. It exists so that mail you send from your own mail client can be captured into the helpdesk without the recipient seeing a support address on the thread.
The classic use case is sales or account management. Somebody emails a customer directly from Outlook, blind-copies the helpdesk address, and a ticket appears with the conversation already in it. The customer sees a normal one-to-one email. Your team gets a record.
Two cautions. Find the address in your own admin settings rather than guessing at its format, because it's account-specific. And be deliberate about who has it, since anything blind-copied to it becomes a ticket, including things that probably should not be in a customer-facing system.
There is also an outbound archiving use, where every message the helpdesk sends is blind-copied to an address you control for compliance. If your legal team has asked for a mail archive, that's the mechanism to ask about.
Why BCC replies vanish
Here's the failure people report, and it's not a bug.
A blind-copied recipient replies, the reply never appears on the ticket, and nobody can work out where it went.
The reply went somewhere. It just didn't go where you expected, and there are three usual explanations.
They replied to the customer, not the helpdesk. A BCC recipient sees the original message but isn't on the visible recipient list. Hitting reply sends to the original sender. Your helpdesk never sees it.
They replied to the helpdesk but aren't on the ticket. An unknown address replying into a ticket thread may be dropped, may create a new ticket, or may land as a contact you did not expect, depending on your settings for handling unrecognised senders. This is the one worth actually testing in your own account.
Spam and filtering. Mail from an address the ticket doesn't know is exactly the shape of a message that filters treat harshly.
The fix is the same in all three cases. If somebody needs to participate in a ticket, put them on the CC list, where the system knows who they are. BCC is for capture, not for collaboration.
Rules that keep threads intact
Four habits that prevent most of this.
And if the same conversation has already fragmented into two tickets because a reply landed in the wrong place, merging them puts the history back into one thread.
Frequently asked questions
How does CC behaviour differ from BCC?
Freshdesk email CC behaviour keeps the CC'd person on the thread and their replies land on the ticket. A Freshdesk BCC email address adds the message quietly, and to Freshdesk add CC to ticket afterwards you edit the ticket rather than the email.
What is the Freshdesk BCC address?
A dedicated address generated for your account, shown in your email settings. Blind-copying it on mail you send from your own client captures the conversation as a ticket without exposing a support address to the recipient.
Can I BCC someone on a Freshdesk agent reply?
The reply editor exposes CC, and BCC availability depends on your configuration. Even where it exists, a blind-copied recipient is not added to the ticket, so their reply will not thread back reliably.
Why did a BCC reply never reach the ticket?
Usually because the recipient replied to the original sender rather than the helpdesk, or because their address is unknown to the ticket and your settings drop or re-route unrecognised senders.
How many people can I CC on a Freshdesk ticket?
There's a cap, generous for normal use and easy to hit if a distribution list is involved. Check the current limit in the Freshworks documentation before you design a workflow around large CC lists.
Do CC recipients see private notes?
No. Private notes are internal and never sent to the requester or the CC list. That is the safe way to loop in a colleague on a customer thread.
When one thread becomes two
Misrouted replies are a reliable source of duplicate tickets. Ticket Merger matches them on requester, subject and ticket fields inside a time window, then merges them.
Start free trial14-day free trial. No credit card required.