We switched to sprint didn't get coverage
A Sprint customer review by GetHuman user GetHuman-john909 from December 1st, 2017
Background on GetHuman-john909's case
GetHuman: GetHuman-john909 - can you tell our other Sprint customers when your case took place?
GetHuman-john909: Yup. It was morning, on November 23rd.
GetHuman: Did you reach out to Sprint, and if so, how?
GetHuman: And which of these common Sprint customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-john909 a list of common Sprint problems)
GetHuman-john909: "Pay bill" was why I was trying to call.
GetHuman-john909's review of Sprint customer service
GetHuman: So how would you sum up your experience for GetHuman's Sprint 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-john909: We switched to sprint didn't get coverage
GetHuman: Can you tell the rest of us a bit more from what happened on 11/23/17?
GetHuman-john909: So we cancelled within the ** days but store manager charged restocking fees just feel this was unfair since we didn't get service at our home
GetHuman: Let's quantify your experience contacting Sprint. On a scale of 1 to 5, how easy is it go get help on a Sprint problem?
GetHuman-john909: 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?
GetHuman-john909: I'd give them a three out of five on communication.
GetHuman: And what about Sprint's ability to quickly and effectively address your problem?
GetHuman-john909: For that I would say one out of five.
GetHuman: And finally- any advice for other Sprint customers?
GetHuman-john909: Call them early in the day or late. Don't forget any personal or account information you might need for Sprint to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-john909 taken from his Sprint customer service problem that occurred on November 23rd, 2017.