Plentyoffish: I'm still not able to go on the website
A Plentyoffish customer review by GetHuman user ~lonely for you 50 1964 from November 24th, 2017
Background on ~lonely for you 50 1964's case
GetHuman: ~lonely for you 50 1964 - can you tell our other Plentyoffish customers when your case took place?
~lonely for you 50 1964: Yes I can. It was middle of the night, on November 23rd.
GetHuman: Did you reach out to Plentyoffish, and if so, how?
GetHuman: And which of these common Plentyoffish customer issues best describes the reason you wanted to talk to them?
(Shows ~lonely for you 50 1964 a list of common Plentyoffish problems)
~lonely for you 50 1964: "Update account information" was why I was trying to contact.
~lonely for you 50 1964's review of Plentyoffish customer service
GetHuman: So how would you sum up your experience for GetHuman's Plentyoffish 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.
~lonely for you 50 1964: I'm still not able to go on the website
GetHuman: Let's quantify your experience contacting Plentyoffish. On a scale of 1 to 5, how easy is it go get help on a Plentyoffish problem?
~lonely for you 50 1964: 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?
~lonely for you 50 1964: I'd give them a one out of five on communication.
GetHuman: And what about Plentyoffish's ability to quickly and effectively address your problem?
~lonely for you 50 1964: For that I would say one out of five.
GetHuman: And finally- any advice for other Plentyoffish customers?
~lonely for you 50 1964: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Plentyoffish to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~lonely for you 50 1964 taken from his Plentyoffish customer service problem that occurred on November 23rd, 2017.