Cricket Wireless: All I wanted was the APN settings, ** minutes t...
A Cricket Wireless customer review by GetHuman user GetHuman-71611 from November 22nd, 2017
Background on GetHuman-71611's case
GetHuman: GetHuman-71611 - can you tell our other Cricket Wireless customers when your case took place?
GetHuman-71611: Sure. It was morning, on November 13th.
GetHuman: Did you reach out to Cricket Wireless, and if so, how?
GetHuman: And which of these common Cricket Wireless customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-71611 a list of common Cricket Wireless problems)
GetHuman-71611: "Cancel service" was why I was trying to call.
GetHuman-71611's review of Cricket Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's Cricket 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-71611: All I wanted was the APN settings, ** minutes to talk to someone on the phone, ** to get someone on the chat program (I was **th in line)
GetHuman: Let's quantify your experience contacting Cricket Wireless. On a scale of 1 to 5, how easy is it go get help on a Cricket Wireless problem?
GetHuman-71611: I'd give them a three 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-71611: I'd give them a one out of five on communication.
GetHuman: And what about Cricket Wireless's ability to quickly and effectively address your problem?
GetHuman-71611: For that I would say one out of five.
GetHuman: And finally- any advice for other Cricket Wireless customers?
GetHuman-71611: Call them early in the day or late. Don't forget any personal or account information you might need for Cricket Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-71611 taken from his Cricket Wireless customer service problem that occurred on November 13th, 2017.