Kodak: Chatted for over ** minutes. Was told even thou...
A Kodak customer review by GetHuman user ~anonymous from November 17th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Kodak customers when your case took place?
~anonymous: Yes I can. It was middle of the night, on November 16th.
GetHuman: Did you reach out to Kodak, and if so, how?
GetHuman: And which of these common Kodak customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common Kodak problems)
~anonymous: "Return an Order" was why I was trying to contact.
~anonymous's review of Kodak customer service
GetHuman: So how would you sum up your experience for GetHuman's Kodak 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.
~anonymous: Chatted for over ** minutes. Was told even though camcorder is still under warranty, (** day), a refund cannot be issued. I will have to pay to ship it somewhere to be repaired. No other option, with proof of purchase. Refused * times to give me a valid phone number to call regarding my warranty. Disgusting service.
GetHuman: Let's quantify your experience contacting Kodak. On a scale of 1 to 5, how easy is it go get help on a Kodak problem?
~anonymous: I'd give them a one 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?
~anonymous: I'd give them a one out of five on communication.
GetHuman: And what about Kodak's ability to quickly and effectively address your problem?
~anonymous: For that I would say four out of five.
GetHuman: And finally- any advice for other Kodak customers?
~anonymous: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Kodak to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Kodak customer service problem that occurred on November 16th, 2017.