Sprint Airave: Response time was excellent (at **:** P.M. on a...
A Sprint Airave customer review by GetHuman user ~anonymous from November 19th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Sprint Airave customers when your case took place?
~anonymous: Yeah. It was middle of the night, on November 12th.
GetHuman: Did you reach out to Sprint Airave, and if so, how?
GetHuman: And which of these common Sprint Airave customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common Sprint Airave problems)
~anonymous: "Technical support" was why I was trying to call.
~anonymous's review of Sprint Airave customer service
GetHuman: So how would you sum up your experience for GetHuman's Sprint Airave 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.
~anonymous: Response time was excellent (at **:** P.M. on a Monday. The agent said that she would be updating the firmware and that she would call back in ** minutes to see if it was successful. So, for now, we are part-way to a solution.
GetHuman: Let's quantify your experience contacting Sprint Airave. On a scale of 1 to 5, how easy is it go get help on a Sprint Airave problem?
~anonymous: I'd give them a four 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?
~anonymous: I'd give them a three out of five on communication.
GetHuman: And what about Sprint Airave's ability to quickly and effectively address your problem?
~anonymous: For that I would say five out of five.
GetHuman: And finally- any advice for other Sprint Airave customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Sprint Airave to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Sprint Airave customer service problem that occurred on November 12th, 2017.