Boost Mobile: I thought the person I talked to was pretty nic...
Boost Mobile Ulasan pelanggan oleh pengguna GetHuman GetHuman-314537 dari November 22, 2017
Background on GetHuman-314537's case
GetHuman: GetHuman-314537 - can you tell our other Boost Mobile customers when your case took place?
GetHuman-314537: Yeah. It was late at night, on November 14.
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 GetHuman-314537 a list of common Boost Mobile problems)
GetHuman-314537: "Service problem" was why I was trying to call.
GetHuman-314537'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.
GetHuman-314537: I thought the person I talked to was pretty nice. He even helped me figure out a way to keep my service on if I'm out of the country for a long time.
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?
GetHuman-314537: 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?
GetHuman-314537: I'd give them a five out of five on communication.
GetHuman: And what about Boost Mobile's ability to quickly and effectively address your problem?
GetHuman-314537: For that I would say three out of five.
GetHuman: And finally- any advice for other Boost Mobile customers?
GetHuman-314537: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Boost Mobile mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-314537 taken from his Boost Mobile customer service problem that occurred on November 14, 2017.