Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • Zappos has built an empire that goes against the first person rule. Commented Jan 12, 2011 at 0:46
  • I don't know about Zappos, but it seems true enough for most companies. All I know is that if I'm frustrated enough to call tech support, I feel bad for the person on the other end of the line. Commented Jan 12, 2011 at 1:07
  • Never? As in never, ever? Even if you were a small company made up of salespeople and one or two developers? Not even if your developers were very strong communicators and liked talking with customers? Commented Jul 12, 2013 at 18:27
  • You want your developers to be perceived as knowledgeable--make them the second person the customer talks to. By then the customer will calm down some and behave a bit more reasonably. Now, if it's a customer you have a good relationship with and it's not the first introduction the developer has to the client, then it would be perfectly fine. First contact should be vetted through someone else first though. Commented Jul 13, 2013 at 18:03
  • As somebody who has been first-line support - I think the rule for the "irate caller thinking the first person who answers the phone is wrong" is not correct. Though, I can only speak from my own experience. The occasional irate caller who does think this either realizes their mistake (as long as front-line actually is knowledgeable) or they are simply not looking for a solution, but rather someone to blame - which means nobody can help them. I do still agree overall - developers should be the last contact, once it is determined there is a bug somewhere(or high possibility of one) Commented Oct 23, 2014 at 18:08