3 ms·
I did this recently for a neighbor whose account was hacked. I was able to sit down with her in person and go through the steps and fill out the form with her,
by throwawayfb1234 5y ago
I did this recently for a neighbor whose account was hacked. I was able to sit down with her in person and go through the steps and fill out the form with her, and it was resolved in a day. It felt nice to be able to help someone so directly given how indirect my work usually is. It makes me think that a job in customer support would probably be pleasant if you could consistently fix people's problems (which probably does not describe most customer support jobs). I'd do it again with someone in person, but I don't really feel comfortable doing it over the internet... you really are supposed to be vouching for this person.
The impression I got from training is: "DO NOT EVER TRY TO FIX PROBLEMS ON YOUR OWN. DO NOT EVER ACCESS A SYSTEM ON BEHALF OF FRIENDS OR FAMILY. YOU WILL BE FIRED. And if you ever get anxious and consider breaking those rules, you don't have to because there's an internal system to help you resolve these issues."
(I started posting this in my own name, but I don't like telling people "no" and I'm worried this invites requests...)
- MrDunham 5y agoSmart to use a throwaway. And I personally know someone who violated the “don’t access systems” rule. They were very well liked and they were very quickly fired. I was wondering what the purpose of the oops team was beyond making employees’ lives a little easier. Makes sense that they would set it up as a way to avoid having devs trying to fix friend’s/family member’s problems and risk private info/PII running amok