Team Beachbody: The online computer system told me that I would...
A Team Beachbody customer review by GetHuman user ~fifadude from November 18th, 2017
Background on ~fifadude's case
GetHuman: ~fifadude - can you tell our other Team Beachbody customers when your case took place?
~fifadude: Yeah. It was late at night, on November 12th.
GetHuman: Did you reach out to Team Beachbody, and if so, how?
GetHuman: And which of these common Team Beachbody customer issues best describes the reason you wanted to talk to them?
(Shows ~fifadude a list of common Team Beachbody problems)
~fifadude: "Complaint" was why I was trying to call.
~fifadude's review of Team Beachbody customer service
GetHuman: So how would you sum up your experience for GetHuman's Team Beachbody 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.
~fifadude: The online computer system told me that I would wait * minutes, well after * minutes it transferred me to a line that was quiet and I said hello for at least * more minute several times then the line disconnected. Poor telephone service.
GetHuman: Let's quantify your experience contacting Team Beachbody. On a scale of 1 to 5, how easy is it go get help on a Team Beachbody problem?
~fifadude: I'd give them a four 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?
~fifadude: I'd give them a three out of five on communication.
GetHuman: And what about Team Beachbody's ability to quickly and effectively address your problem?
~fifadude: For that I would say two out of five.
GetHuman: And finally- any advice for other Team Beachbody customers?
~fifadude: Call them early in the day or late. Don't forget any personal or account information you might need for Team Beachbody to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~fifadude taken from his Team Beachbody customer service problem that occurred on November 12th, 2017.