Audible.com: I was the having a download issue and the woman...
A Audible.com customer review by GetHuman user GetHuman-222502 from November 20th, 2017
Background on GetHuman-222502's case
GetHuman: GetHuman-222502 - can you tell our other Audible.com customers when your case took place?
GetHuman-222502: Yeah. It was afternoon, on November 18th.
GetHuman: Did you reach out to Audible.com, and if so, how?
GetHuman: And which of these common Audible.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-222502 a list of common Audible.com problems)
GetHuman-222502: "Complaint" was why I was trying to call.
GetHuman-222502's review of Audible.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Audible.com 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-222502: I was the having a download issue and the woman on the other end sorted it in about ** seconds. Very handy system, I'm assuming it may not be so helpful if you have a tricky problem but was perfect for me.
GetHuman: Let's quantify your experience contacting Audible.com. On a scale of 1 to 5, how easy is it go get help on a Audible.com problem?
GetHuman-222502: I'd give them a two 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-222502: I'd give them a three out of five on communication.
GetHuman: And what about Audible.com's ability to quickly and effectively address your problem?
GetHuman-222502: For that I would say four out of five.
GetHuman: And finally- any advice for other Audible.com customers?
GetHuman-222502: Call them early in the day or late. Don't forget any personal or account information you might need for Audible.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-222502 taken from his Audible.com customer service problem that occurred on November 18th, 2017.