![]() |
|
![]() |
#1 | ||
DIY Tragic
Join Date: Apr 2018
Location: Sydney, more than not. I hate it.
Posts: 21,362
|
A modestly large local entity which we are engaged with as clients, has inadvertently shared almost 200 client email addresses by selecting CC instead of BCC on an informational email.
Definitely not their usual manner, they are big on discreetness and privacy. We aren’t particularly fussed, there is negligible risk ongoing other than perhaps nuisance emails from other recipients who haven’t locked down their own accounts so well (remember Plaxo and LinkedIn taking over peoples’ email address books). What I’m curious about, is how would the employee of several years who made this mistake, typically be treated by an employer? Would they be given strong hints to leave, or just be called in for a chat with senior managers to see if there was any help needed? |
||
![]() |
![]() ![]() |
![]() |
#2 | |||
HUGH JARSE
![]() Join Date: May 2005
Location: Yap-Hoon
Posts: 21,286
|
Quote:
![]() |
|||
![]() |
![]() ![]() |
![]() |
#3 | ||
FG XR6 Ute & Sedan
![]() Join Date: Oct 2006
Location: Bibra Lake WA
Posts: 22,669
|
Recognise that everyone makes a genuine mistake sometimes and if it was a genuine non-malicious error by an otherwise conscientious hardworking long term employee that doesn't habitually make mistakes say nothing and just wear it. They likely will already know they stuffed up and feel extremely bad about it. But also do your TQM checks to ensure that there is nothing in you processes, systems or practices that increases the risk of such mistakes and see what can be done in terms of your processes, systems and practices to prevent another occurrence. Ultimately it's the employer who is responsible even if only in the context of recruiting or training practices.
__________________
regards Blue |
||
![]() |
![]() ![]() |
![]() |
#4 | ||
Cabover nut
Join Date: Aug 2015
Location: Onsite Eastcoast
Posts: 10,825
|
Promoted to vice president.
![]()
__________________
heritagestonemason.com/Fordlouisvillerestoration In order that the labour of centuries past may not be in vain during the centuries to come...... D. Diderot 1752
|
||
![]() |
![]() ![]() |
4 users like this post: |
![]() |
#5 | ||
T3/Sprint8
![]() Join Date: Jan 2005
Location: Australia
Posts: 16,094
|
Well said aussieblue.
CB as you even said, not their norm and discreet - afraid shit happens with office staff even the best of them. I have had it happen a few times in error by 2 good dependable long serving employees. They know they stuffed up and regret it deeply for they hate error. If it was done by a perennial offending employee you can only give them an official warning unless they are up to the third you can boot them out. Sent from my iPhone using Tapatalk
__________________
Tickfords T3/TS50 '02 Sprint8 manual Sept 24 '16 Daily Macan GTS "Don't believe everything you read on the internet. Abraham Lincoln" |
||
![]() |
![]() ![]() |
![]() |
#6 | ||
Regular Member
Join Date: Feb 2011
Posts: 288
|
If an honest mistake...not much you can do except maybe send out an apology via BCC this time.
We have to do this almost daily...and each time I am worried I will inadvertently add them to CC.
__________________
2013 FPV GT (Sold) 2015 Renault Megane RS265 - 2L Turbo 6Spd Manual 2022 (21.75) Ford Everest Bi-Turbo |
||
![]() |
![]() ![]() |
![]() |
#7 | ||
DIY Tragic
Join Date: Apr 2018
Location: Sydney, more than not. I hate it.
Posts: 21,362
|
There’s been crickets so far, to be honest I would have half expected something like a BCC’d apology as described.
What was hardest for me, was not scanning the address list to see if I recognised any names. It’s human nature to be curious in these situations but more important for me to respect the privacy others enjoyed in the first place. |
||
![]() |
![]() ![]() |
3 users like this post: |
![]() |
#8 | ||
FF.Com.Au Hardcore
Join Date: Feb 2005
Posts: 5,012
|
Pretty harmless in the scheme of things. Nothing worth warning an employee over.
I remember one of our employees, in the early 2000s (ie. when ADSL was still relatively new and 256k was considered broadband) was doing a mass mailout of a newsletter that was in full print quality. Never occurred to them to reduce the file size. She only realised there was a problem when customers started complaining their mailboxes were filling up, and the attachment was so big their mail client was crashing before the download finished, forcing them to restart the download from scratch. A lot of unhappy campers.... |
||
![]() |
![]() ![]() |
This user likes this post: |