Alltel Wireless: Constant billing problems. They credited me fo...
A Alltel Wireless customer review by GetHuman user GetHuman-179954 from November 6th, 2017
Background on GetHuman-179954's case
GetHuman: GetHuman-179954 - can you tell our other Alltel Wireless customers when your case took place?
GetHuman-179954: Yes. It was afternoon, on November 5th.
GetHuman: Did you reach out to Alltel Wireless, and if so, how?
GetHuman: And which of these common Alltel Wireless customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-179954 a list of common Alltel Wireless problems)
GetHuman-179954: "Lower my bill" was why I was trying to call.
GetHuman-179954's review of Alltel Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's Alltel Wireless 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-179954: Constant billing problems. They credited me for their error, then billed my cc again. I would not trust this company with my credit card information.
GetHuman: Let's quantify your experience contacting Alltel Wireless. On a scale of 1 to 5, how easy is it go get help on a Alltel Wireless problem?
GetHuman-179954: I'd give them a two 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-179954: I'd give them a three out of five on communication.
GetHuman: And what about Alltel Wireless's ability to quickly and effectively address your problem?
GetHuman-179954: For that I would say one out of five.
GetHuman: And finally- any advice for other Alltel Wireless customers?
GetHuman-179954: Call them early in the day or late. Don't forget any personal or account information you might need for Alltel Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-179954 taken from his Alltel Wireless customer service problem that occurred on November 5th, 2017.