Magento Commerce: No way to reach Magento Go support so I had to...
A Magento Commerce customer review by GetHuman user ~customerrrr from November 11th, 2017
Background on ~customerrrr's case
GetHuman: ~customerrrr - can you tell our other Magento Commerce customers when your case took place?
~customerrrr: Yeah. It was middle of the night, on November 3rd.
GetHuman: Did you reach out to Magento Commerce, and if so, how?
GetHuman: And which of these common Magento Commerce customer issues best describes the reason you wanted to talk to them?
(Shows ~customerrrr a list of common Magento Commerce problems)
~customerrrr: "Technical support" was why I was trying to call.
~customerrrr's review of Magento Commerce customer service
GetHuman: So how would you sum up your experience for GetHuman's Magento Commerce 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.
~customerrrr: No way to reach Magento Go support so I had to call corporate and they gave me a number. *** *** **** is Magento Go Support
GetHuman: Let's quantify your experience contacting Magento Commerce. On a scale of 1 to 5, how easy is it go get help on a Magento Commerce problem?
~customerrrr: 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?
~customerrrr: I'd give them a three out of five on communication.
GetHuman: And what about Magento Commerce's ability to quickly and effectively address your problem?
~customerrrr: For that I would say one out of five.
GetHuman: And finally- any advice for other Magento Commerce customers?
~customerrrr: Call them early in the day or late. Don't forget any personal or account information you might need for Magento Commerce to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~customerrrr taken from his Magento Commerce customer service problem that occurred on November 3rd, 2017.