Microsoft 365: This was not the absolute correct number for wh...
A Microsoft 365 customer review by GetHuman user ~Demdog from November 16th, 2017
Background on ~Demdog's case
GetHuman: ~Demdog - can you tell our other Microsoft 365 customers when your case took place?
~Demdog: Yup. It was morning, on November 11th.
GetHuman: Did you reach out to Microsoft 365, and if so, how?
GetHuman: And which of these common Microsoft 365 customer issues best describes the reason you wanted to talk to them?
(Shows ~Demdog a list of common Microsoft 365 problems)
~Demdog: "None of those really matches why I wanted to call Microsoft 365 that day." was why I was trying to call.
~Demdog's review of Microsoft 365 customer service
GetHuman: So how would you sum up your experience for GetHuman's Microsoft 365 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.
~Demdog: This was not the absolute correct number for what I needed help for but the customer service tech got me to the right dept to get help. Had to go thru * people to get the *rd who helped me solve my problem
GetHuman: Let's quantify your experience contacting Microsoft 365. On a scale of 1 to 5, how easy is it go get help on a Microsoft 365 problem?
~Demdog: 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?
~Demdog: I'd give them a three out of five on communication.
GetHuman: And what about Microsoft 365's ability to quickly and effectively address your problem?
~Demdog: For that I would say two out of five.
GetHuman: And finally- any advice for other Microsoft 365 customers?
~Demdog: Call them early in the day or late. Don't forget any personal or account information you might need for Microsoft 365 to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Demdog taken from his Microsoft 365 customer service problem that occurred on November 11th, 2017.