Dear Zoosk, Why isn't browsing anonymous anyway?...
Zoosk Ulasan pelanggan oleh pengguna GetHuman GetHuman25954 dari Disember 5, 2017
Background on GetHuman25954's case
GetHuman: GetHuman25954 - can you tell our other Zoosk customers when your case took place?
GetHuman25954: Yup. It was evening, on Disember 4.
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 GetHuman25954 a list of common Zoosk problems)
GetHuman25954: "Overcharge/Strange charge" was why I was trying to call.
GetHuman25954'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.
GetHuman25954: Dear Zoosk, Why isn't browsing anonymous anyway?...
GetHuman: Can you tell the rest of us a bit more from what happened on 12/04/17?
GetHuman25954: Dear Zoosk, Why isn't browsing anonymous anyway? No one should see that anyone is looking through the pictures...right? Thank you for your answer! voxac**
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?
GetHuman25954: I'd give them a three 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?
GetHuman25954: I'd give them a one out of five on communication.
GetHuman: And what about Zoosk's ability to quickly and effectively address your problem?
GetHuman25954: For that I would say one out of five.
GetHuman: And finally- any advice for other Zoosk customers?
GetHuman25954: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Zoosk mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman25954 taken from his Zoosk customer service problem that occurred on Disember 4, 2017.