Moving to BCC: an email etiquette you must know

We use email every day and most of the times the BCC is a crafty little feature that we rarely use. Usually, it is for confirmation emails for events to multiple people, or something similar. The only other time I have personally used it was when I had to send assignments for evaluation to some higher authority and a few friends as well. I did not want the authority to know about the friends getting it as well.

Recently I got an email which went as follows:

- Advertisement -

Ryan: Hey Bob, Wanted to introduce you to Saransh who shares similar interests as you. You both should definitely get to know each other.
Bob: Saransh, nice to meet you. Thanks for introducing us Ryan (moving Ryan to BCC). Can we talk over skype Saransh?

After that Bob and I shared some more emails in which Ryan was not CC’d at all. Had it been someone else in place of Bob, Ryan would have been needlessly CC’d on all of them even though he was not interested in them at all.

Because Bob smartly moved Ryan to BCC, Ryan no longer was punished with the plethora of emails we interchanged after this conversation. I found it to be a great way of letting people know that you replied to the mail and are following up with the other person. Since the person who is introducing you is not required in the mail thread anymore, moving to BCC was a great idea to save them from receiving irrelevant emails.

And introductions are not the only scenario in which we should be using BCC. Next time you are attached to an email thread with a lot of people in it, instead of lazily hitting the reply all button and sending an email to everyone, think if moving to BCCwould be useful. It would save a lot of precious time on people’s part if you just copy paste their names from the cc list to the BCC list, mentioning that you are moving them to BCC.

Eventually, you would have saved them from some unwanted emails! Go give it out a try next time you are talking to a group of people over email (Though, be careful not to offend any egos in the process of doing so).

Recent Articles

How to sort a Set in JavaScript

ES6 introduced the set data structure in JavaScript. But sets are not ordered abstract data structures. So there is no .sort() property...

Debugging CSS scroll using one simple style

I have been doing a lot of complicated front-end work off lately and that always brings me back to the class conundrum...

CSS :has a parent selector now

CSS now includes a :has selector that allows us to apply styles on the basis of what is happening inside an element....

How to fix “invalid active developer path” after MacOS update

If you are here, then you are getting an "invalid active developer path" error on running commands in the terminal after a...

Getting the value of an input element as a number without parseInt

Every once in a while, you come across something and you think, how did I not know this earlier? valueAsNumber is that thing...

Related Stories

Leave A Reply

Please enter your comment!
Please enter your name here

Hi there! Want some more knowledge?

Think that the knowledge shared is helpful? You might want to give our mailing list a try. We'll send you 2-4 emails a month, right when new posts come out.

Hi there! Want some more knowledge?

Think that the knowledge shared is helpful? You might want to give our mailing list a try. We'll send you 2-4 emails a month, right when new posts come out.
https://www.wisdomgeek.com/general/email/email-etiquette-moving-to-bcc/
www.wisdomgeek.com
crawl=CC-MAIN-2022-49
240768
application/http; msgtype=response
sha1:HJBE3JMXBXBMCAJMH33GUKGAL4XQWX7U
<urn:uuid:1517c7c9-3194-4160-841e-fe7cd2219e5d>
2022-12-07T13:02:32Z
172.67.161.135
text/html
sha1:LPXKSJQNEIPJV74SVHKTTHHMFJ5ITG2D
<urn:uuid:482930b8-7090-4cdb-acea-ee1351c03c84>
https://www.wisdomgeek.com/general/email/email-etiquette-moving-to-bcc/
response
<urn:uuid:4fd55511-28f0-4c77-918b-7e84779c1c36>
isPartOf: CC-MAIN-2022-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-199
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/