Sprint Airave: Sprint answered my call within * rings and didn...
A Sprint Airave customer review by GetHuman user ~aggiect01 from November 15th, 2017
Background on ~aggiect01's case
GetHuman: ~aggiect01 - can you tell our other Sprint Airave customers when your case took place?
~aggiect01: Yes I can. It was afternoon, on November 9th.
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 ~aggiect01 a list of common Sprint Airave problems)
~aggiect01: "Service problem" was why I was trying to call.
~aggiect01'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.
~aggiect01: Sprint answered my call within * rings and didn't have to transfer me (like usual) to anyone else. The worker was American and understood my problem and did everything in his power to fix it. I wish every call to Sprint was this professional.
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?
~aggiect01: I'd give them a five 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?
~aggiect01: I'd give them a five out of five on communication.
GetHuman: And what about Sprint Airave's ability to quickly and effectively address your problem?
~aggiect01: For that I would say three out of five.
GetHuman: And finally- any advice for other Sprint Airave customers?
~aggiect01: 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 ~aggiect01 taken from his Sprint Airave customer service problem that occurred on November 9th, 2017.