Microsoft - Tech Support: Refused any tech support. I needed tech suppor...
A Microsoft - Tech Support customer review by GetHuman user ~dk from November 23rd, 2017
Background on ~dk's case
GetHuman: ~dk - can you tell our other Microsoft - Tech Support customers when your case took place?
~dk: Yeah. It was middle of the night, on November 14th.
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 ~dk a list of common Microsoft - Tech Support problems)
~dk: "Technical Support" was why I was trying to call.
~dk'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.
~dk: Refused any tech support. I needed tech support with only one portion of Office ****. One spoke to first: Great. Second: Could not understand English. Hung up on me.
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?
~dk: I'd give them a two 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?
~dk: I'd give them a three out of five on communication.
GetHuman: And what about Microsoft - Tech Support's ability to quickly and effectively address your problem?
~dk: For that I would say one out of five.
GetHuman: And finally- any advice for other Microsoft - Tech Support customers?
~dk: 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 ~dk taken from his Microsoft - Tech Support customer service problem that occurred on November 14th, 2017.