We would like to add a mechanism on the PFC by which customers could rate each Microsoft response they receive to issues they file. In the meanwhile, here are some ideas on what I think we should strive for in terms of response quality.


With each response the first thing we want to let the bug submitter know is that we have read and understood their issue. We never want to use a canned response or template. Each issue is different and each response is directly relevant to that issue.


We want to thank each user for their contribution, taking the time to post the issue. It helps us build a product that is more inline with customer’s expectations and the dialog with Microsoft is informative to other customers as well who may have the same issue.


We want to provide a good reason for each resolution. In particular, if we don’t fix an issue (and I don’t think customers expect us to fix every single issue) we should provide a good explanation for why we made the trade-off we made.


Here are some additional things I think Microsoft responders should always do in each reply:

  • Be honest and polite
  • Use a respectful tone
  • Keep in mind that written communication is more open to misinterpretation then in person
  • Sign replies with name, title, team
  • Don’t treat customer issues like a hot potato
  • Don’t reply to customer bugs during bug triage, take time to provide a great response
  • Provide a workaround whenever possible
  • Don’t sound like Marketing J


I’m putting together guidance for the VS product team on providing great responses to customers… your feedback on the subject would be greatly appreciated and will be incorporated.


Also, if you have examples of good and poor responses from MS, please forward to me. I will send kudos for the good ones and try to correct the others.


And another note, if ever you are not satisfied with a response you receive, just reopen the issue and let us know!


Marie Hagman

Visual Studio

Program Manager