# BCC in E-Mail Template?

**URL:** https://community.zammad.org/t/bcc-in-e-mail-template/9281
**Category:** Feature requests
**Created:** [May 18, 2022, 1:24pm UTC](https://community.zammad.org/t/bcc-in-e-mail-template/9281 "2022-05-18T13:24:27Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![marco86](https://community.zammad.org/letter_avatar_proxy/v4/letter/m/aeb1de/32.png) [@marco86](https://community.zammad.org/u/marco86)
#### Post date: [May 18, 2022, 1:24pm UTC](https://community.zammad.org/t/bcc-in-e-mail-template/9281/1 "2022-05-18T13:24:27Z")

</div>

### Infos:

- Used Zammad version: 5.1
- Used Zammad installation type: package
- Operating system: Ubuntu 20.0.4
- Browser + version: Firefox 100

### Expected behavior:

I just want say, that our agents ask for a bcc option in the E-Mail Template:

 ![grafik](https://community.zammad.org/uploads/default/original/2X/5/5802f9f3cad2479abce746f348d7933f05370aaa.png)

In the Internet I have found several request for this feature request, however, they developer say that th, ere are still too few requests to include this feature.

> [@Add BCC to E-Mail-Template](https://community.zammad.org/t/add-bcc-to-e-mail-template/5239):
>
> Infos: Used Zammad version: 3.4.x Used Zammad installation source: (source, package, …) Operating system: Ubuntu 18.04 Browser + version: all I have already found out, that we can store a static BCC address. Is there a possibility that a BCC address can be built into the e-mail template, which is filled with the address from the Zammad e-mail account used? The background is that we work with 3 support departments and each want to store a copy of the outgoing e-mails in the respective group…

> [@Bcc for outgoing emails](https://community.zammad.org/t/bcc-for-outgoing-emails/3289):
>
> As in normal email communication also with support tickets it is sometimes required to send copies to third parties which should not be seen by the primary recipients. This is currently not possible. We often work around it by sending two mails: One to the primary recipient(s) and an other to the BCC recipient(s). However this bloats tickets and database and makes tickets less clear and readable. As a request this has been denied in [Add BCC field by MarkusHarmsen · Pull Request #1040 · zamma…](https://github.com/zammad/zammad/pull/1040)

> <https://github.com/zammad/zammad/issues/295>
>
> Sometimes we like to inform a person about an answer without knowlege of custome…r. So it would be nice, if we could send it by bcc. Both customer and the person have no access to Zammad.

I think it would be a compromise, if you can show/hide the bcc option in the administrative area.

Greetings, Marco

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [May 18, 2022, 2:10pm UTC](https://community.zammad.org/t/bcc-in-e-mail-template/9281/2 "2022-05-18T14:10:24Z")

</div>

We have said this several times by now:  
We’re not planning to allow BCC messages.

This goes against everything Zammad tries to accomplish.

---

<div class="post-metadata">

### Author: ![fthommen](https://community.zammad.org/user_avatar/community.zammad.org/fthommen/32/51_2.png) [@fthommen](https://community.zammad.org/u/fthommen)
#### Post date: [June 30, 2022, 4:01pm UTC](https://community.zammad.org/t/bcc-in-e-mail-template/9281/3 "2022-06-30T16:01:32Z")

</div>

But as you can see from the repeated requests, there _does_ seem to be quite some demand for such a feature 😄. I don’t really understand, what the “everything Zammad tries to accomplish” it is, that would not allow BCC to be implemented.

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [June 30, 2022, 4:05pm UTC](https://community.zammad.org/t/bcc-in-e-mail-template/9281/4 "2022-06-30T16:05:20Z")

</div>

3 posts, 6 hearts in total.  
Yeah I can totally see the 80% user base + demand.

---

<div class="post-metadata">

### Author: ![fthommen](https://community.zammad.org/user_avatar/community.zammad.org/fthommen/32/51_2.png) [@fthommen](https://community.zammad.org/u/fthommen)
#### Post date: [July 1, 2022, 9:58am UTC](https://community.zammad.org/t/bcc-in-e-mail-template/9281/5 "2022-07-01T09:58:38Z")

</div>

Hmm. You expect 80% of the user base to come to this forum and post requests or click on some heart-fomed icons? That sounds overly optimistic to me 😄

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [July 1, 2022, 10:12am UTC](https://community.zammad.org/t/bcc-in-e-mail-template/9281/6 "2022-07-01T10:12:14Z")

</div>

No what, all my sarcasm put aside, I’m trying to say that this is not a functionality that’s made for our 80% user base. I understand that there’s functions missing for some of you. Some are more important than others but what’s important is: It is impossible to introduce them all. At least not in a short time period - this forces us to prioritize and keep focus on the important functions.

In general: The more that need a function, the better for us. Don’t forget, we have to maintain code we introduce. Maintaining and developing costs money in the end.

I have explained why BCC isn’t a thing for Zammad several times on this board. I am sorry, I am too lazy to do so again.

---

<div class="post-metadata">

### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system)
#### Post date: [July 9, 2023, 5:24am UTC](https://community.zammad.org/t/bcc-in-e-mail-template/9281/7 "2023-07-09T05:24:52Z")

</div>

This topic was automatically closed after 416 days. New replies are no longer allowed.
