Magento Commerce: A voice message picked up on the *th ring. It s...
A Magento Commerce customer review by GetHuman user GetHuman-205160 from November 13th, 2017
Background on GetHuman-205160's case
GetHuman: GetHuman-205160 - can you tell our other Magento Commerce customers when your case took place?
GetHuman-205160: Yes I can. It was middle of the night, on November 7th.
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 GetHuman-205160 a list of common Magento Commerce problems)
GetHuman-205160: "Technical support" was why I was trying to call.
GetHuman-205160'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.
GetHuman-205160: A voice message picked up on the *th ring. It said to leave them a message and an "analyst" would call back. I'm NOT holding my breath for the call back. We will see.
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?
GetHuman-205160: 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?
GetHuman-205160: I'd give them a one out of five on communication.
GetHuman: And what about Magento Commerce's ability to quickly and effectively address your problem?
GetHuman-205160: For that I would say two out of five.
GetHuman: And finally- any advice for other Magento Commerce customers?
GetHuman-205160: 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 GetHuman-205160 taken from his Magento Commerce customer service problem that occurred on November 7th, 2017.