Frontier Communications: CUSTOMER SERVICE REP. WAS NOT FRIENDLY AND VERY...
A Frontier Communications customer review by GetHuman user ~TOD from November 4th, 2017
Background on ~TOD's case
GetHuman: ~TOD - can you tell our other Frontier Communications customers when your case took place?
~TOD: Sure. It was middle of the night, on November 2nd.
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 ~TOD a list of common Frontier Communications problems)
~TOD: "Change Plan" was why I was trying to call.
~TOD'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.
~TOD: CUSTOMER SERVICE REP. WAS NOT FRIENDLY AND VERY COLD EVEN WHEN I EXPLAINED ABOUT MOTHER CURRENTLY IN HOSPITAL UNABLE TO CALL FOR HERSELF. THANKS AGAIN...
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?
~TOD: 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?
~TOD: I'd give them a one out of five on communication.
GetHuman: And what about Frontier Communications's ability to quickly and effectively address your problem?
~TOD: For that I would say one out of five.
GetHuman: And finally- any advice for other Frontier Communications customers?
~TOD: 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 ~TOD taken from his Frontier Communications customer service problem that occurred on November 2nd, 2017.