Boost Mobile: dial the *** *** **** number did not receive th...
A Boost Mobile customer review by GetHuman user ~theresa thomas from November 25th, 2017
Background on ~theresa thomas 's case
GetHuman: ~theresa thomas - can you tell our other Boost Mobile customers when your case took place?
~theresa thomas : Yup. It was evening, on November 16th.
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 ~theresa thomas a list of common Boost Mobile problems)
~theresa thomas : "Overcharge/Strange charge" was why I was trying to call.
~theresa thomas '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.
~theresa thomas : dial the *** *** **** number did not receive the service I needed kept sending me to prompts wanted to talk to live service rep. Did not direct me to a live service representative
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?
~theresa thomas : I'd give them a five 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?
~theresa thomas : I'd give them a two out of five on communication.
GetHuman: And what about Boost Mobile's ability to quickly and effectively address your problem?
~theresa thomas : For that I would say one out of five.
GetHuman: And finally- any advice for other Boost Mobile customers?
~theresa thomas : 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 ~theresa thomas taken from his Boost Mobile customer service problem that occurred on November 16th, 2017.