Airvoice Wireless: ** rated my *** ** on hold and i forgot i had b...
A Airvoice Wireless customer review by GetHuman user GetHuman-317038 from November 14th, 2017
Background on GetHuman-317038's case
GetHuman: GetHuman-317038 - can you tell our other Airvoice Wireless customers when your case took place?
GetHuman-317038: Yup. It was afternoon, on November 10th.
GetHuman: Did you reach out to Airvoice Wireless, and if so, how?
GetHuman: And which of these common Airvoice Wireless customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-317038 a list of common Airvoice Wireless problems)
GetHuman-317038: "Technical support" was why I was trying to call.
GetHuman-317038's review of Airvoice Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's Airvoice 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-317038: ** rated my *** ** on hold and i forgot i had been on hold until i wanted to make a call and realized i was still on hold
GetHuman: Let's quantify your experience contacting Airvoice Wireless. On a scale of 1 to 5, how easy is it go get help on a Airvoice Wireless problem?
GetHuman-317038: 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-317038: I'd give them a one out of five on communication.
GetHuman: And what about Airvoice Wireless's ability to quickly and effectively address your problem?
GetHuman-317038: For that I would say four out of five.
GetHuman: And finally- any advice for other Airvoice Wireless customers?
GetHuman-317038: Call them early in the day or late. Don't forget any personal or account information you might need for Airvoice Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-317038 taken from his Airvoice Wireless customer service problem that occurred on November 10th, 2017.