Facebook: My account was blocked for some readon FB refus...
A Facebook customer review by GetHuman user ~Maddod MADDOG from November 27th, 2017
Background on ~Maddod MADDOG's case
GetHuman: ~Maddod MADDOG - can you tell our other Facebook customers when your case took place?
~Maddod MADDOG: Yes I can. It was morning, on November 18th.
GetHuman: Did you reach out to Facebook, and if so, how?
GetHuman: And which of these common Facebook customer issues best describes the reason you wanted to talk to them?
(Shows ~Maddod MADDOG a list of common Facebook problems)
~Maddod MADDOG: "Can't Receive Code to Reset" was why I was trying to contact.
~Maddod MADDOG's review of Facebook customer service
GetHuman: So how would you sum up your experience for GetHuman's Facebook 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.
~Maddod MADDOG: My account was blocked for some readon FB refuse to communicate as to why. Several requests to have my account deketed altogether apparently friend tell me I still there. Going on since late ****. So can you please delete my *****@***.com account
GetHuman: Let's quantify your experience contacting Facebook. On a scale of 1 to 5, how easy is it go get help on a Facebook problem?
~Maddod MADDOG: 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?
~Maddod MADDOG: I'd give them a three out of five on communication.
GetHuman: And what about Facebook's ability to quickly and effectively address your problem?
~Maddod MADDOG: For that I would say two out of five.
GetHuman: And finally- any advice for other Facebook customers?
~Maddod MADDOG: Call them early in the day or late. Don't forget any personal or account information you might need for Facebook to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Maddod MADDOG taken from his Facebook customer service problem that occurred on November 18th, 2017.