Facebook: Why did FB delete my husbands account? Why? I a...
A Facebook customer review by GetHuman user ~SRockwell from November 27th, 2017
Background on ~SRockwell's case
GetHuman: ~SRockwell - can you tell our other Facebook customers when your case took place?
~SRockwell: Yes I can. It was morning, on November 19th.
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 ~SRockwell a list of common Facebook problems)
~SRockwell: "Ads Account Issue" was why I was trying to contact.
~SRockwell'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.
~SRockwell: Why did FB delete my husbands account? Why? I am at a loss as to why you would do this? At whose request since he passed away more than * years ago it could not have been him, nor would it have been me given his page has brought me much solace these two years. Why did you delete it? Why!?!?!
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?
~SRockwell: 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?
~SRockwell: 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?
~SRockwell: For that I would say one out of five.
GetHuman: And finally- any advice for other Facebook customers?
~SRockwell: 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 ~SRockwell taken from his Facebook customer service problem that occurred on November 19th, 2017.