Boost Mobile: Trying to link * phones together for family pla...
Background on GetHuman-bobbima's case
GetHuman: GetHuman-bobbima - can you tell our other Boost Mobile customers when your case took place?
GetHuman-bobbima: Sure. It was morning, on December 2nd.
GetHuman: Did you reach out to Boost Mobile, and if so, how?
GetHuman-bobbima: I used the 888-266-7848 number I found for on the GetHuman Boost Mobile customer phone number page I was on: Boost Mobile Customer Service Phone Number
GetHuman: And which of these common Boost Mobile customer issues best describes the reason you wanted to talk to them?
Shows GetHuman-bobbima a list of common Boost Mobile problems
GetHuman-bobbima: "Lost phone" was why I was trying to call.
GetHuman-bobbima'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-bobbima: Trying to link * phones together for family plan, been calling for * weeks, still not resolved
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-bobbima: 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?
GetHuman-bobbima: I'd give them a three out of five on communication.
GetHuman: And what about Boost Mobile's ability to quickly and effectively address your problem?
GetHuman-bobbima: For that I would say two out of five.
GetHuman: And finally- any advice for other Boost Mobile customers?
GetHuman-bobbima: 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 GetHuman-bobbima taken from his Boost Mobile customer service problem that occurred on December 2nd, 2017.