Craigslist: no one answers the line and all i want to know...
A Craigslist customer review by GetHuman user GetHuman-400969 from November 22nd, 2017
Background on GetHuman-400969's case
GetHuman: GetHuman-400969 - can you tell our other Craigslist customers when your case took place?
GetHuman-400969: Yes. It was middle of the night, on November 18th.
GetHuman: Did you reach out to Craigslist, and if so, how?
GetHuman: And which of these common Craigslist customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-400969 a list of common Craigslist problems)
GetHuman-400969: "Fraud" was why I was trying to contact.
GetHuman-400969's review of Craigslist customer service
GetHuman: So how would you sum up your experience for GetHuman's Craigslist 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-400969: no one answers the line and all i want to know is how the **** to stop these mother f ???? from deleting my posts.now you all should have a way to find out who is doing it and then put a police report in.
GetHuman: Let's quantify your experience contacting Craigslist. On a scale of 1 to 5, how easy is it go get help on a Craigslist problem?
GetHuman-400969: 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?
GetHuman-400969: I'd give them a two out of five on communication.
GetHuman: And what about Craigslist's ability to quickly and effectively address your problem?
GetHuman-400969: For that I would say one out of five.
GetHuman: And finally- any advice for other Craigslist customers?
GetHuman-400969: Call them early in the day or late. Don't forget any personal or account information you might need for Craigslist to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-400969 taken from his Craigslist customer service problem that occurred on November 18th, 2017.