Blue Ridge Communications: Keith was very nice and very efficient
A Blue Ridge Communications customer review by GetHuman user ~Linda100 from November 15th, 2017
Background on ~Linda100's case
GetHuman: ~Linda100 - can you tell our other Blue Ridge Communications customers when your case took place?
~Linda100: Yeah. It was late at night, on November 11th.
GetHuman: Did you reach out to Blue Ridge Communications, and if so, how?
GetHuman: And which of these common Blue Ridge Communications customer issues best describes the reason you wanted to talk to them?
(Shows ~Linda100 a list of common Blue Ridge Communications problems)
~Linda100: "None of those really matches why I wanted to call Blue Ridge Communications that day." was why I was trying to call.
~Linda100's review of Blue Ridge Communications customer service
GetHuman: So how would you sum up your experience for GetHuman's Blue Ridge 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.
~Linda100: Keith was very nice and very efficient
GetHuman: Let's quantify your experience contacting Blue Ridge Communications. On a scale of 1 to 5, how easy is it go get help on a Blue Ridge Communications problem?
~Linda100: 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?
~Linda100: I'd give them a four out of five on communication.
GetHuman: And what about Blue Ridge Communications's ability to quickly and effectively address your problem?
~Linda100: For that I would say three out of five.
GetHuman: And finally- any advice for other Blue Ridge Communications customers?
~Linda100: Call them early in the day or late. Don't forget any personal or account information you might need for Blue Ridge Communications to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Linda100 taken from his Blue Ridge Communications customer service problem that occurred on November 11th, 2017.