Facebook: No phone support, no answers or response on hel...
A Facebook customer review by GetHuman user ~Christina Campbell from November 22nd, 2017
Background on ~Christina Campbell's case
GetHuman: ~Christina Campbell - can you tell our other Facebook customers when your case took place?
~Christina Campbell: Sure. It was evening, on November 14th.
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 ~Christina Campbell a list of common Facebook problems)
~Christina Campbell: "Merge Pages" was why I was trying to contact.
~Christina Campbell'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.
~Christina Campbell: No phone support, no answers or response on help page. Ask for sensitive info*password and then post it. Not sure whether others could see the password. I removed it because of doubt.
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?
~Christina Campbell: 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?
~Christina Campbell: 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?
~Christina Campbell: For that I would say four out of five.
GetHuman: And finally- any advice for other Facebook customers?
~Christina Campbell: 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 ~Christina Campbell taken from his Facebook customer service problem that occurred on November 14th, 2017.