images on the internet • Had someone else check them for appropriateness • Will be justifying their inclusion on each slide • Or probably just ignoring them
line customer support a month. • My coworkers each do 4 hours of support a month. • My boss does 4 hours. • The CEO does too. • It happened by mistake.
get weekends off. • At the time, weekend support load was relatively low in the 10’s of tickets range. • An additional hire didn’t make much sense. • As the company grew, it was discovered that other benefits to this all-hands approach existed.
I try to verify the problem. • I can’t reproduce the issue. • Turns out there was an A/B test that had a problem on a certain browser/OS combination. • The notification about the A/B test was sent in an email. To the wrong group address, so not everyone knew about it.
email • Support can trigger the same email • Sometimes we need to be able to hand a user a password in a support email • We lacked a single-use password mechanism
Unfriendly formatting • Hard to search by customer • Only developers had access, and would spend at least a cumulative 10 hours a week searching logs for support
site tells me that I am entering the wrong username or password. I have to reset my password every single time, even when I’m sure I have my password correct.”
to (nicely) accuse the customer of being forgetful. And it sucks if you get it wrong. • Our support staff figured out how to use Bunyan to tell if a customer was actually doing this.
first/last name in the main support tool. • Look up the chain of events for that user id. • Look at the event chains for the ip addresses associated with the events in the previous chain. • Filter by login failures.