Office 365 Support: Great service representative, but this website...
A Office 365 Support customer review by GetHuman user ~consumer1 from November 28th, 2017
Background on ~consumer1's case
GetHuman: ~consumer1 - can you tell our other Office 365 Support customers when your case took place?
~consumer1: Yup. It was middle of the night, on November 22nd.
GetHuman: Did you reach out to Office 365 Support, and if so, how?
GetHuman: And which of these common Office 365 Support customer issues best describes the reason you wanted to talk to them?
(Shows ~consumer1 a list of common Office 365 Support problems)
~consumer1: "None of those really matches why I wanted to call Office 365 Support that day." was why I was trying to call.
~consumer1's review of Office 365 Support customer service
GetHuman: So how would you sum up your experience for GetHuman's Office 365 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.
~consumer1: Great service representative, but this website does not explain that the phone number is for Corporate customers and Network Admins, not personal use customers
GetHuman: Let's quantify your experience contacting Office 365 Support. On a scale of 1 to 5, how easy is it go get help on a Office 365 Support problem?
~consumer1: 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?
~consumer1: I'd give them a five out of five on communication.
GetHuman: And what about Office 365 Support's ability to quickly and effectively address your problem?
~consumer1: For that I would say four out of five.
GetHuman: And finally- any advice for other Office 365 Support customers?
~consumer1: Call them early in the day or late. Don't forget any personal or account information you might need for Office 365 Support to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~consumer1 taken from his Office 365 Support customer service problem that occurred on November 22nd, 2017.