Boost Mobile: i really hate the wait and still didnt get the...
A Boost Mobile customer review by GetHuman user ~unsatisfied customer from November 15th, 2017
Background on ~unsatisfied customer's case
GetHuman: ~unsatisfied customer - can you tell our other Boost Mobile customers when your case took place?
~unsatisfied customer: Sure. It was afternoon, on November 6th.
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 ~unsatisfied customer a list of common Boost Mobile problems)
~unsatisfied customer: "Cancel service" was why I was trying to call.
~unsatisfied customer'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.
~unsatisfied customer: i really hate the wait and still didnt get the information I requested. But yet you still want me to pay the bill.
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?
~unsatisfied customer: 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?
~unsatisfied customer: 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?
~unsatisfied customer: For that I would say two out of five.
GetHuman: And finally- any advice for other Boost Mobile customers?
~unsatisfied customer: 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 ~unsatisfied customer taken from his Boost Mobile customer service problem that occurred on November 6th, 2017.