Office 365 Support: My call was dropped three times. I was redirec...
A Office 365 Support customer review by GetHuman user ~Bill from November 25th, 2017
Background on ~Bill's case
GetHuman: ~Bill - can you tell our other Office 365 Support customers when your case took place?
~Bill: Sure. It was late at night, on November 21st.
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 ~Bill a list of common Office 365 Support problems)
~Bill: "None of those really matches why I wanted to call Office 365 Support that day." was why I was trying to call.
~Bill'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.
~Bill: My call was dropped three times. I was redirected twice. My question was never answered. All of the technicians spoke too fast and with a heave accent.
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?
~Bill: 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?
~Bill: I'd give them a one out of five on communication.
GetHuman: And what about Office 365 Support's ability to quickly and effectively address your problem?
~Bill: For that I would say five out of five.
GetHuman: And finally- any advice for other Office 365 Support customers?
~Bill: 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 ~Bill taken from his Office 365 Support customer service problem that occurred on November 21st, 2017.