Cricket Communications: FINALLY GOT A HUMAN WHEN I WAS NOT ABLE TO ON M...
A Cricket Communications customer review by GetHuman user GetHuman-300866 from October 29th, 2017
Background on GetHuman-300866's case
GetHuman: GetHuman-300866 - can you tell our other Cricket Communications customers when your case took place?
GetHuman-300866: Sure. It was morning, on October 20th.
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 GetHuman-300866 a list of common Cricket Communications problems)
GetHuman-300866: "Setup service" was why I was trying to call.
GetHuman-300866'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.
GetHuman-300866: FINALLY GOT A HUMAN WHEN I WAS NOT ABLE TO ON MY CRICKET PHONE. I HAD TO USE A LAND LINE FOR THIS NUMBER TO WORK.
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?
GetHuman-300866: 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?
GetHuman-300866: I'd give them a one out of five on communication.
GetHuman: And what about Cricket Communications's ability to quickly and effectively address your problem?
GetHuman-300866: For that I would say four out of five.
GetHuman: And finally- any advice for other Cricket Communications customers?
GetHuman-300866: 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 GetHuman-300866 taken from his Cricket Communications customer service problem that occurred on October 20th, 2017.