Rakuten: they advertiesed a product at a price and then...
A Rakuten customer review by GetHuman user GetHuman-257364 from November 15th, 2017
Background on GetHuman-257364's case
GetHuman: GetHuman-257364 - can you tell our other Rakuten customers when your case took place?
GetHuman-257364: Yes. It was middle of the night, on November 8th.
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 GetHuman-257364 a list of common Rakuten problems)
GetHuman-257364: "Warranty claim" was why I was trying to call.
GetHuman-257364'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.
GetHuman-257364: they advertiesed a product at a price and then the actual price was ***% higher. I called them, they indicated that the law assures me that I can buy the item at the advertised price, then they put me in a never ending loop and proved to be liars.
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?
GetHuman-257364: 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-257364: I'd give them a four out of five on communication.
GetHuman: And what about Rakuten's ability to quickly and effectively address your problem?
GetHuman-257364: For that I would say three out of five.
GetHuman: And finally- any advice for other Rakuten customers?
GetHuman-257364: 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 GetHuman-257364 taken from his Rakuten customer service problem that occurred on November 8th, 2017.