Kobo Books: i am actually employed in telephone technical s...
A Kobo Books customer review by GetHuman user GetHuman-71855 from November 22nd, 2017
Background on GetHuman-71855's case
GetHuman: GetHuman-71855 - can you tell our other Kobo Books customers when your case took place?
GetHuman-71855: Yes I can. It was middle of the night, on November 12th.
GetHuman: Did you reach out to Kobo Books, and if so, how?
GetHuman: And which of these common Kobo Books customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-71855 a list of common Kobo Books problems)
GetHuman-71855: "Make a purchase" was why I was trying to contact.
GetHuman-71855's review of Kobo Books customer service
GetHuman: So how would you sum up your experience for GetHuman's Kobo Books 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-71855: i am actually employed in telephone technical support industry. not to be able to speak to a company representative is deplorable. complete lack of respect for the customer, ad infinitum.
GetHuman: Let's quantify your experience contacting Kobo Books. On a scale of 1 to 5, how easy is it go get help on a Kobo Books problem?
GetHuman-71855: 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-71855: I'd give them a five out of five on communication.
GetHuman: And what about Kobo Books's ability to quickly and effectively address your problem?
GetHuman-71855: For that I would say four out of five.
GetHuman: And finally- any advice for other Kobo Books customers?
GetHuman-71855: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Kobo Books to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-71855 taken from his Kobo Books customer service problem that occurred on November 12th, 2017.