Frontier Communications: This is the third time I've called about the sa...
A Frontier Communications customer review by GetHuman user ~Big Ron from November 28th, 2017
Background on ~Big Ron's case
GetHuman: ~Big Ron - can you tell our other Frontier Communications customers when your case took place?
~Big Ron: Yup. It was afternoon, on November 23rd.
GetHuman: Did you reach out to Frontier Communications, and if so, how?
GetHuman: And which of these common Frontier Communications customer issues best describes the reason you wanted to talk to them?
(Shows ~Big Ron a list of common Frontier Communications problems)
~Big Ron: "Technical Support" was why I was trying to call.
~Big Ron's review of Frontier Communications customer service
GetHuman: So how would you sum up your experience for GetHuman's Frontier Communications 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.
~Big Ron: This is the third time I've called about the same problem. Maybe they will actually do something about it this time.
GetHuman: Let's quantify your experience contacting Frontier Communications. On a scale of 1 to 5, how easy is it go get help on a Frontier Communications problem?
~Big Ron: I'd give them a four 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?
~Big Ron: I'd give them a five out of five on communication.
GetHuman: And what about Frontier Communications's ability to quickly and effectively address your problem?
~Big Ron: For that I would say two out of five.
GetHuman: And finally- any advice for other Frontier Communications customers?
~Big Ron: Call them early in the day or late. Don't forget any personal or account information you might need for Frontier Communications to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Big Ron taken from his Frontier Communications customer service problem that occurred on November 23rd, 2017.