Digital River: went through straight away and the person (took...
A Digital River customer review by GetHuman user GetHuman-138661 from November 23rd, 2017
Background on GetHuman-138661's case
GetHuman: GetHuman-138661 - can you tell our other Digital River customers when your case took place?
GetHuman-138661: Sure. It was morning, on November 19th.
GetHuman: Did you reach out to Digital River, and if so, how?
GetHuman: And which of these common Digital River customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-138661 a list of common Digital River problems)
GetHuman-138661: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-138661's review of Digital River customer service
GetHuman: So how would you sum up your experience for GetHuman's Digital River 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-138661: went through straight away and the person (took a couple of automated prompts as I was outside business hours) was helpful and fixed my issues immediately
GetHuman: Let's quantify your experience contacting Digital River. On a scale of 1 to 5, how easy is it go get help on a Digital River problem?
GetHuman-138661: I'd give them a five 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-138661: I'd give them a five out of five on communication.
GetHuman: And what about Digital River's ability to quickly and effectively address your problem?
GetHuman-138661: For that I would say five out of five.
GetHuman: And finally- any advice for other Digital River customers?
GetHuman-138661: Call them early in the day or late. Don't forget any personal or account information you might need for Digital River to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-138661 taken from his Digital River customer service problem that occurred on November 19th, 2017.