Cricket Communications: They transferred me to tech support to resolve...
A Cricket Communications customer review by GetHuman user ~planet_J from November 13th, 2017
Background on ~planet_J's case
GetHuman: ~planet_J - can you tell our other Cricket Communications customers when your case took place?
~planet_J: Sure. It was middle of the night, on November 8th.
GetHuman: Did you reach out to Cricket Communications, and if so, how?
GetHuman: And which of these common Cricket Communications customer issues best describes the reason you wanted to talk to them?
(Shows ~planet_J a list of common Cricket Communications problems)
~planet_J: "Lower my bill" was why I was trying to call.
~planet_J's review of Cricket Communications customer service
GetHuman: So how would you sum up your experience for GetHuman's Cricket Communications 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.
~planet_J: They transferred me to tech support to resolve my issue and it took a few minutes but they got it fixed
GetHuman: Let's quantify your experience contacting Cricket Communications. On a scale of 1 to 5, how easy is it go get help on a Cricket Communications problem?
~planet_J: I'd give them a one 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?
~planet_J: I'd give them a two out of five on communication.
GetHuman: And what about Cricket Communications's ability to quickly and effectively address your problem?
~planet_J: For that I would say one out of five.
GetHuman: And finally- any advice for other Cricket Communications customers?
~planet_J: Call them early in the day or late. Don't forget any personal or account information you might need for Cricket Communications to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~planet_J taken from his Cricket Communications customer service problem that occurred on November 8th, 2017.