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.
- Zappos has built an empire that goes against the first person rule.JeffO– JeffO2011-01-12 00:46:00 +00:00Commented 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.Berin Loritsch– Berin Loritsch2011-01-12 01:07:54 +00:00Commented 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?Bryan Oakley– Bryan Oakley2013-07-12 18:27:34 +00:00Commented 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.Berin Loritsch– Berin Loritsch2013-07-13 18:03:14 +00:00Commented 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)DoubleDouble– DoubleDouble2014-10-23 18:08:17 +00:00Commented Oct 23, 2014 at 18:08
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you