Rosetta Stone: One tech overseas said the server will be fixed...
A Rosetta Stone customer review by GetHuman user GetHuman-76131 from November 28th, 2017
Background on GetHuman-76131's case
GetHuman: GetHuman-76131 - can you tell our other Rosetta Stone customers when your case took place?
GetHuman-76131: Sure. It was middle of the night, on November 24th.
GetHuman: Did you reach out to Rosetta Stone, and if so, how?
GetHuman: And which of these common Rosetta Stone customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-76131 a list of common Rosetta Stone problems)
GetHuman-76131: "Change order" was why I was trying to call.
GetHuman-76131's review of Rosetta Stone customer service
GetHuman: So how would you sum up your experience for GetHuman's Rosetta Stone 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-76131: One tech overseas said the server will be fixed in ** minutes. I called back and the next tech said ** hours. This is par the course for RS. Good program. Bad connections.
GetHuman: Let's quantify your experience contacting Rosetta Stone. On a scale of 1 to 5, how easy is it go get help on a Rosetta Stone problem?
GetHuman-76131: 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?
GetHuman-76131: I'd give them a one out of five on communication.
GetHuman: And what about Rosetta Stone's ability to quickly and effectively address your problem?
GetHuman-76131: For that I would say two out of five.
GetHuman: And finally- any advice for other Rosetta Stone customers?
GetHuman-76131: Call them early in the day or late. Don't forget any personal or account information you might need for Rosetta Stone to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-76131 taken from his Rosetta Stone customer service problem that occurred on November 24th, 2017.