Facebook: There was NO wait time because they don't offer...
A Facebook customer review by GetHuman user ~Cee Baker from November 27th, 2017
Background on ~Cee Baker's case
GetHuman: ~Cee Baker - can you tell our other Facebook customers when your case took place?
~Cee Baker: Yes. It was late at night, on November 25th.
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 ~Cee Baker a list of common Facebook problems)
~Cee Baker: "Delete Account" was why I was trying to contact.
~Cee Baker'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.
~Cee Baker: There was NO wait time because they don't offer phone support any longer .. I've tried emailing but have gotten NO reply .. I'm trying to set up a new account and if I don't get some support soon (it is June * @ **:**pm) within * days it will show me you no longer want or need customers!!!!!!
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?
~Cee Baker: 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?
~Cee Baker: I'd give them a four out of five on communication.
GetHuman: And what about Facebook's ability to quickly and effectively address your problem?
~Cee Baker: For that I would say one out of five.
GetHuman: And finally- any advice for other Facebook customers?
~Cee Baker: 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 ~Cee Baker taken from his Facebook customer service problem that occurred on November 25th, 2017.