Rosetta Stone: Got straight through to Robyn. At first seemed...
A Rosetta Stone customer review by GetHuman user GetHuman-429884 from November 22nd, 2017
Background on GetHuman-429884's case
GetHuman: GetHuman-429884 - can you tell our other Rosetta Stone customers when your case took place?
GetHuman-429884: Yes. It was middle of the night, on November 18th.
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-429884 a list of common Rosetta Stone problems)
GetHuman-429884: "Cancel order" was why I was trying to call.
GetHuman-429884'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-429884: Got straight through to Robyn. At first seemed to be reading from a script, but was really efficient and after warming up, very pleasant to talk to
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-429884: 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-429884: I'd give them a two out of five on communication.
GetHuman: And what about Rosetta Stone's ability to quickly and effectively address your problem?
GetHuman-429884: For that I would say three out of five.
GetHuman: And finally- any advice for other Rosetta Stone customers?
GetHuman-429884: 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-429884 taken from his Rosetta Stone customer service problem that occurred on November 18th, 2017.