Microsoft Office: I have been waiting for ** minutes now just to...
A Microsoft Office customer review by GetHuman user ~Anonymous from November 19th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Microsoft Office customers when your case took place?
~Anonymous: Yes. It was morning, on November 17th.
GetHuman: Did you reach out to Microsoft Office, and if so, how?
GetHuman: And which of these common Microsoft Office customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common Microsoft Office problems)
~Anonymous: "Hacked account" was why I was trying to call.
~Anonymous's review of Microsoft Office customer service
GetHuman: So how would you sum up your experience for GetHuman's Microsoft Office 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.
~Anonymous: I have been waiting for ** minutes now just to be connected to someone who can help me with my situation with my Office product, and I still have not been connected. Very, very bad service.
GetHuman: Let's quantify your experience contacting Microsoft Office. On a scale of 1 to 5, how easy is it go get help on a Microsoft Office problem?
~Anonymous: 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?
~Anonymous: I'd give them a four out of five on communication.
GetHuman: And what about Microsoft Office's ability to quickly and effectively address your problem?
~Anonymous: For that I would say five out of five.
GetHuman: And finally- any advice for other Microsoft Office customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Microsoft Office to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Microsoft Office customer service problem that occurred on November 17th, 2017.