Magento Commerce: Person answered quickly, but transferred me to...
A Magento Commerce customer review by GetHuman user GetHuman-198675 from November 12th, 2017
Background on GetHuman-198675's case
GetHuman: GetHuman-198675 - can you tell our other Magento Commerce customers when your case took place?
GetHuman-198675: Yes I can. It was middle of the night, on November 10th.
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-198675 a list of common Magento Commerce problems)
GetHuman-198675: "Change order" was why I was trying to call.
GetHuman-198675'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-198675: Person answered quickly, but transferred me to someone in my area. That person didn't answer after *** times...
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-198675: 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?
GetHuman-198675: I'd give them a four out of five on communication.
GetHuman: And what about Magento Commerce's ability to quickly and effectively address your problem?
GetHuman-198675: For that I would say one out of five.
GetHuman: And finally- any advice for other Magento Commerce customers?
GetHuman-198675: 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-198675 taken from his Magento Commerce customer service problem that occurred on November 10th, 2017.