Microsoft - Tech Support: Tried to do an RMA, the CSR barely understood m...
A Microsoft - Tech Support customer review by GetHuman user ~Jake from November 22nd, 2017
Background on ~Jake's case
GetHuman: ~Jake - can you tell our other Microsoft - Tech Support customers when your case took place?
~Jake: Yes. It was afternoon, on November 18th.
GetHuman: Did you reach out to Microsoft - Tech Support, and if so, how?
GetHuman: And which of these common Microsoft - Tech Support customer issues best describes the reason you wanted to talk to them?
(Shows ~Jake a list of common Microsoft - Tech Support problems)
~Jake: "Refund or Suspicious Charges" was why I was trying to call.
~Jake's review of Microsoft - Tech Support customer service
GetHuman: So how would you sum up your experience for GetHuman's Microsoft - Tech Support customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~Jake: Tried to do an RMA, the CSR barely understood me. Forgot to tell me how to get the shipping label for the RMA, until I reminded him.
GetHuman: Let's quantify your experience contacting Microsoft - Tech Support. On a scale of 1 to 5, how easy is it go get help on a Microsoft - Tech Support problem?
~Jake: I'd give them a three out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~Jake: I'd give them a four out of five on communication.
GetHuman: And what about Microsoft - Tech Support's ability to quickly and effectively address your problem?
~Jake: For that I would say one out of five.
GetHuman: And finally- any advice for other Microsoft - Tech Support customers?
~Jake: Call them early in the day or late. Don't forget any personal or account information you might need for Microsoft - Tech Support to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Jake taken from his Microsoft - Tech Support customer service problem that occurred on November 18th, 2017.