This story is mostly true, although it's not quite how I remember it. In 1989 I was a product support services intern working at Microsoft's Lincoln Plaza campus. I worked for the 'System Languages' team, or SysLang as we called ourselves. We supported Micorosft C 5.x, QuickC, and their Pascal product and associated tools like the M editor and CodeView. One day (I don't remember if it was November or not) Bill came through on a tour of PSS. I mentioned to another intern, Nadine, that it would be cool if Bill took a call from a customer. When he came by our area with a group of other management types she bounded up to him with a huge smile on her face and asked if he'd like to see how things worked for himself, and take a call from a customer. The people he was with tried to dissuade him of this idea, saying something about schedules and the like, but Bill liked the idea and wanted to do it. At the time, I was a real clean freak, and my cube was very clean and devoid of clutter, so I suggested he sit down at my desk. I explained to him how the Aspect phone system worked and how to look up things in our STARS knowledge base using an OS/2 terminal program connected to a DEC minicomputer. He got settled in, and eventually took a call, greeting the customer like:
"Hello, Product Support Services, this is William, how may I help you?"
Just about everyone who wasn't currently on a call with a customer was gathered around my cube listening. I seem to remember the customer having a problem with the linker. Bill queried the knowledge base, which was normally painfully slow, but this time it was snappy and responsive. The first result looked like it might have addressed the customer's problem, and Bill went with it. I of course only heard one side of the conversation, but it sounded like the customer wasn't satisfied with the answer. Bill was firm yet polite, reassuring the customer that we had seen this problem before and that his solution was correct, and the customer eventually agreed to try the solution mentioned in the STARS article. An hour or so later, my friend Tad got that customer again, and he mentioned that William had helped him with his problem earlier but his solution didn't work. Tad let the customer know that he had in fact talked to Bill Gates, and helped him with his problem. I don't remember how/if it got solved though.
That was quite a big day for me. For years I had saved the yellow pad that had Bill's notes from the call.
Back in the late 70's or early 80's I was leading a group that did compilers and assemblers for the microprocessor group. We had a problem with one of the compilers from Microsoft. I called up technical support and got Paul Allen on the line. Whatever the problem was he got it solved. If you want technical support, it's best to get the technical guy,
I also posted my version of the story to the blog's comments. Man, hard to believe that was 20 years ago. Hopefully some other SysLang veterans read HN and will post something.
The best thing you can ever do for your company is to put every employee in front of customers. One of the things that attracted me to FreshBooks was that they rotate everyone through customer support continuously. As a (former) developer who was tired of consistently building the wrong thing because sales and marketing jealously guarded the customer, this was very refreshing.
This isn't a novel idea. Many companies with customer service orientations have done this. If you're selling Software-as-a-Service, that ought to include you!
Not necessarily a good idea. I could probably handle it now without a problem, but when I was 25 or 30 I would have quit first, and you should have your head examined if you would have put me in that position back then. Given how many high functioning autists tend toward techie type jobs, it may even block your hiring good tech talent (it may even be an ADA violation).
What amazes me about this story is that back in '89 MS had a knowledge base that worked so well that a person not trained for customer service was able to provide the help needed just by looking in the knowledge base. Many companies still don't have a system that good yet.
At my previous company, we had a great (and horrible) knowledge base. We could search all bug reports, knowledge base articles and previous calls to tech support. Even with all the great content, it takes more than a search to solve the issues. It takes knowledge of the product which is assumed in the notes. It also takes the ability to listen to an issue from a customer, figure out from their problem which is the key factor, what to search for, and how to figure out which search result helps this issue.
I have heard Bill Gates was a very hands on manager, especially back the, so I assume he knew the products reasonably well. And I know he is very intelligent, so I assume he would be decent at troubleshooting. But as another noted above, he didn't actually solve the issue for the customer.
The application sucked, was IE6 only, search was horrendous, but the content was good.
It also included compilers and, specifically to the problem the user called in about, a linker. Compilers and linkers are no simple matter to support, particularly in those days.
"He was flipping through the spec! [Calm down, what are you a little girl?]
... and THERE WERE NOTES IN ALL THE MARGINS. ON EVERY PAGE OF THE SPEC. HE HAD READ THE WHOLE GODDAMNED THING AND WRITTEN NOTES IN THE MARGINS.
He Read The Whole Thing! [OMG SQUEEE!]
The questions got harder and more detailed."
There is a nice little koan about technical management in that essay too: "he just wants to make sure .."
"Hello, Product Support Services, this is William, how may I help you?"
Just about everyone who wasn't currently on a call with a customer was gathered around my cube listening. I seem to remember the customer having a problem with the linker. Bill queried the knowledge base, which was normally painfully slow, but this time it was snappy and responsive. The first result looked like it might have addressed the customer's problem, and Bill went with it. I of course only heard one side of the conversation, but it sounded like the customer wasn't satisfied with the answer. Bill was firm yet polite, reassuring the customer that we had seen this problem before and that his solution was correct, and the customer eventually agreed to try the solution mentioned in the STARS article. An hour or so later, my friend Tad got that customer again, and he mentioned that William had helped him with his problem earlier but his solution didn't work. Tad let the customer know that he had in fact talked to Bill Gates, and helped him with his problem. I don't remember how/if it got solved though.
That was quite a big day for me. For years I had saved the yellow pad that had Bill's notes from the call.