Lenn,
>> you have to pay in most cases however. So I doubt >> that this is the answer you want to hear.
i have no problems paying for support when the problem is on my part. however, when the problem is like the one discribed in the newsgroups - that is, when the product has a problem or flaw that keeps me from working, than i'd rather see support for free: after all, it's not my fault this thing is not working. (there should a least be a somewhat helpful error message...)
>>Let me ask you this, can you describe what your >>ideal customer experience would be in a perfect
>> world?
well, basically, i wouldn't need to get into contact with
someone@microsoft because the products would just work as expected, wouldn't throw meaningless exceptions with empty error message. compilers wouldn't have flaws. documentation would be 100% correct all the time. (ups, and yes, nobody would try to translate developer products into german...

)
obviously this is simply not possible given the complexity of todays tools. we all know that. so i guess what you're asking for is the 'ideal' customer experience wrt developer support.
the short answer is: i was quite happy with the support i got when i used to be an mvp. there was a single contact who knew me (at least from mail) whom i could turn to whatever problems in whatever product turned up. (granted, most of the time i was catching errors in the c++ compiler, but you know what i mean... )
>> How would you like to get help from Microsoft?
the point here is: when i try to get into contact /w someone from microsoft, it will be because there is a problem with a microsoft product and not because i have a problem using the product. this means, i'm normally not asking for 'help' because i need assistance to do something, but rather i'm asking for a solution the microsoft caused in the first place.
obviously, its quite hard for microsoft to differentiate here: when people complain about the c++ compiler, most of the time the compiler is correct and the complaining folks simply didn't understand the language.
>> Via phone?
nope. most problems that come up over here surely cannot be solved on the phone.
>> Via Web?
web or newsgroups is ok for some stuff that don't need extraordinary amount of source. compiler problems that can be reproduced easily and stuff like that.
>> Via Email?
i think email is certainly the best way to go here, as long as one is dealing with the same support person to get into contact. (obviously, this person would sometimes need to dispatch some problems to someone else. however, email makes it possible to attach complete projects, and follow ups are alot easier than in web based systems.
>> What would you expect from Microsoft in the interaction?
i'm not sure i understand that question... however, if product problems are concerned, it would be nice to know the status of problems one submitted. currently, this is more like a black box process. submit a problem, never hear back. get lucky and the next version fixes the problem... next year.
>> What would make you feel delighted about doing business with Microsoft?
just so there is no misunderstanding here: i like to work with microsofts products. i have no problems whatsoever doing business with microsoft.
i just mislike some details. like, not getting an answer in newsgroups for ages although supposedly one should get an answer. or, not beeing able to find a contact incase something needs to be reported... (like the spamcop stuff).
what i'm doing right now is, i just dump stuff like this into your mailbox, roberts mailbox, or joes mailbox (joes a friend of mine in pss) and hope something will be done about it. this doesn't feel right _and_ this is inefficient.
so what would be really cool: have a single contact to deal with. who could track down the 'correct' guys for a specific problem. who'd know the difference between me having a problem with a product and a problem with a product.
WM_CHEERS
thomas woelfer