Boost Mobile: called several times. prompts went into loops...
A Boost Mobile customer review by GetHuman user ~kharvey from November 26th, 2017
Background on ~kharvey's case
GetHuman: ~kharvey - can you tell our other Boost Mobile customers when your case took place?
~kharvey: Sure. It was morning, on November 17th.
GetHuman: Did you reach out to Boost Mobile, and if so, how?
GetHuman: And which of these common Boost Mobile customer issues best describes the reason you wanted to talk to them?
(Shows ~kharvey a list of common Boost Mobile problems)
~kharvey: "Problem With a PIN" was why I was trying to call.
~kharvey's review of Boost Mobile customer service
GetHuman: So how would you sum up your experience for GetHuman's Boost Mobile 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.
~kharvey: called several times. prompts went into loops asking same questions over and over again. could barely hear my phones kept chopping off words. called from my home phone and the customer service rep kept having computer difficulties so i hung up after being placed on hold * times.
GetHuman: Let's quantify your experience contacting Boost Mobile. On a scale of 1 to 5, how easy is it go get help on a Boost Mobile problem?
~kharvey: I'd give them a two 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?
~kharvey: I'd give them a one out of five on communication.
GetHuman: And what about Boost Mobile's ability to quickly and effectively address your problem?
~kharvey: For that I would say four out of five.
GetHuman: And finally- any advice for other Boost Mobile customers?
~kharvey: Call them early in the day or late. Don't forget any personal or account information you might need for Boost Mobile to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~kharvey taken from his Boost Mobile customer service problem that occurred on November 17th, 2017.