Microsoft Office: Did not help,other than tell me I had to buy a...
A Microsoft Office customer review by GetHuman user ~Miles Lechtman from November 26th, 2017
Background on ~Miles Lechtman's case
GetHuman: ~Miles Lechtman - can you tell our other Microsoft Office customers when your case took place?
~Miles Lechtman: Yes. It was afternoon, on November 18th.
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 ~Miles Lechtman a list of common Microsoft Office problems)
~Miles Lechtman: "Cancel order" was why I was trying to call.
~Miles Lechtman'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.
~Miles Lechtman: Did not help,other than tell me I had to buy a new Microsoft Product. If my grandson did not need it for school I wood not buy it***
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?
~Miles Lechtman: 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?
~Miles Lechtman: 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?
~Miles Lechtman: For that I would say five out of five.
GetHuman: And finally- any advice for other Microsoft Office customers?
~Miles Lechtman: 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 ~Miles Lechtman taken from his Microsoft Office customer service problem that occurred on November 18th, 2017.