Microsoft - Tech Support: Got instant help, fast connected via LogMeIn Re...
A Microsoft - Tech Support customer review by GetHuman user ~Kushbird from November 27th, 2017
Background on ~Kushbird's case
GetHuman: ~Kushbird - can you tell our other Microsoft - Tech Support customers when your case took place?
~Kushbird: Yes I can. It was morning, on November 24th.
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 ~Kushbird a list of common Microsoft - Tech Support problems)
~Kushbird: "Account issues" was why I was trying to call.
~Kushbird'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.
~Kushbird: Got instant help, fast connected via LogMeIn Rescue and the problem was solved in around half an hour.
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?
~Kushbird: I'd give them a four 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?
~Kushbird: I'd give them a one out of five on communication.
GetHuman: And what about Microsoft - Tech Support's ability to quickly and effectively address your problem?
~Kushbird: For that I would say four out of five.
GetHuman: And finally- any advice for other Microsoft - Tech Support customers?
~Kushbird: 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 ~Kushbird taken from his Microsoft - Tech Support customer service problem that occurred on November 24th, 2017.