Allegiance Communications: still on hold after ** minutes
A Allegiance Communications customer review by GetHuman user GetHuman-160594 from November 19th, 2017
Background on GetHuman-160594's case
GetHuman: GetHuman-160594 - can you tell our other Allegiance Communications customers when your case took place?
GetHuman-160594: Yes. It was morning, on November 17th.
GetHuman: Did you reach out to Allegiance Communications, and if so, how?
GetHuman: And which of these common Allegiance Communications customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-160594 a list of common Allegiance Communications problems)
GetHuman-160594: "Complaint" was why I was trying to call.
GetHuman-160594's review of Allegiance Communications customer service
GetHuman: So how would you sum up your experience for GetHuman's Allegiance 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.
GetHuman-160594: still on hold after ** minutes
GetHuman: Let's quantify your experience contacting Allegiance Communications. On a scale of 1 to 5, how easy is it go get help on a Allegiance Communications problem?
GetHuman-160594: 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?
GetHuman-160594: I'd give them a three out of five on communication.
GetHuman: And what about Allegiance Communications's ability to quickly and effectively address your problem?
GetHuman-160594: For that I would say one out of five.
GetHuman: And finally- any advice for other Allegiance Communications customers?
GetHuman-160594: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Allegiance Communications to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-160594 taken from his Allegiance Communications customer service problem that occurred on November 17th, 2017.