Zoosk: I have called and called trying to find someone...
A Zoosk customer review by GetHuman user ~do not remember from November 18th, 2017
Background on ~do not remember's case
GetHuman: ~do not remember - can you tell our other Zoosk customers when your case took place?
~do not remember: Yes I can. It was morning, on November 11th.
GetHuman: Did you reach out to Zoosk, and if so, how?
GetHuman: And which of these common Zoosk customer issues best describes the reason you wanted to talk to them?
(Shows ~do not remember a list of common Zoosk problems)
~do not remember: "Update account information" was why I was trying to call.
~do not remember's review of Zoosk customer service
GetHuman: So how would you sum up your experience for GetHuman's Zoosk 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.
~do not remember: I have called and called trying to find someone to help mme. I went from Facebook Zoosk to AOL. now I can not get into my Zoosk account. Will not except my sign in. They said they would send me password to my emailb but nerver did. Can you help me?
GetHuman: Let's quantify your experience contacting Zoosk. On a scale of 1 to 5, how easy is it go get help on a Zoosk problem?
~do not remember: 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?
~do not remember: I'd give them a four out of five on communication.
GetHuman: And what about Zoosk's ability to quickly and effectively address your problem?
~do not remember: For that I would say three out of five.
GetHuman: And finally- any advice for other Zoosk customers?
~do not remember: Call them early in the day or late. Don't forget any personal or account information you might need for Zoosk to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~do not remember taken from his Zoosk customer service problem that occurred on November 11th, 2017.