Boost Mobile: ive been tyring to get in touch with them for...
A Boost Mobile customer review by GetHuman user ~mad customer100 from November 21st, 2017
Background on ~mad customer100's case
GetHuman: ~mad customer100 - can you tell our other Boost Mobile customers when your case took place?
~mad customer100: Yeah. It was evening, on November 19th.
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 ~mad customer100 a list of common Boost Mobile problems)
~mad customer100: "Service problem" was why I was trying to call.
~mad customer100'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.
~mad customer100: ive been tyring to get in touch with them for * days and still nothing mean while i havent had a phone to use sence please help your customers better or youmwill loose them
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?
~mad customer100: 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?
~mad customer100: 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?
~mad customer100: For that I would say three out of five.
GetHuman: And finally- any advice for other Boost Mobile customers?
~mad customer100: 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 ~mad customer100 taken from his Boost Mobile customer service problem that occurred on November 19th, 2017.