I will stick to Amazon. Rakuten Buy.com has a h...
A Rakuten customer review by GetHuman user ~BeSensible from November 23rd, 2017
Background on ~BeSensible's case
GetHuman: ~BeSensible - can you tell our other Rakuten customers when your case took place?
~BeSensible: Yeah. It was late at night, on November 17th.
GetHuman: Did you reach out to Rakuten, and if so, how?
GetHuman: And which of these common Rakuten customer issues best describes the reason you wanted to talk to them?
(Shows ~BeSensible a list of common Rakuten problems)
~BeSensible: "Change order" was why I was trying to call.
~BeSensible's review of Rakuten customer service
GetHuman: So how would you sum up your experience for GetHuman's Rakuten 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.
~BeSensible: I will stick to Amazon. Rakuten Buy.com has a huge disconnect wth customers hiding this phone and not shipping in a timely manner as Amazon. I paid for overnight shipping and the item did not ship even ** hrs later. Customer Svc has no more info than is on the account screen which has not been updated.
GetHuman: Let's quantify your experience contacting Rakuten. On a scale of 1 to 5, how easy is it go get help on a Rakuten problem?
~BeSensible: I'd give them a four 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?
~BeSensible: I'd give them a three out of five on communication.
GetHuman: And what about Rakuten's ability to quickly and effectively address your problem?
~BeSensible: For that I would say one out of five.
GetHuman: And finally- any advice for other Rakuten customers?
~BeSensible: Call them early in the day or late. Don't forget any personal or account information you might need for Rakuten to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~BeSensible taken from his Rakuten customer service problem that occurred on November 17th, 2017.