Team Beachbody: Good support but there are different department...
A Team Beachbody customer review by GetHuman user GetHuman-231869 from November 26th, 2017
Background on GetHuman-231869's case
GetHuman: GetHuman-231869 - can you tell our other Team Beachbody customers when your case took place?
GetHuman-231869: Yes. It was evening, on November 20th.
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 GetHuman-231869 a list of common Team Beachbody problems)
GetHuman-231869: "Become a member" was why I was trying to call.
GetHuman-231869'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.
GetHuman-231869: Good support but there are different departments in this company and they don't have knowledge of the other areas (ie- sales vs. rewards for programs completed.)
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?
GetHuman-231869: 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-231869: I'd give them a one out of five on communication.
GetHuman: And what about Team Beachbody's ability to quickly and effectively address your problem?
GetHuman-231869: For that I would say four out of five.
GetHuman: And finally- any advice for other Team Beachbody customers?
GetHuman-231869: 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 GetHuman-231869 taken from his Team Beachbody customer service problem that occurred on November 20th, 2017.