Weight Watchers: I spoke with Kellie in AZ, call center she seem...
A Weight Watchers customer review by GetHuman user GetHuman-143775 from November 13th, 2017
Background on GetHuman-143775's case
GetHuman: GetHuman-143775 - can you tell our other Weight Watchers customers when your case took place?
GetHuman-143775: Yes I can. It was afternoon, on November 7th.
GetHuman: Did you reach out to Weight Watchers, and if so, how?
GetHuman: And which of these common Weight Watchers customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-143775 a list of common Weight Watchers problems)
GetHuman-143775: "Signup For Service" was why I was trying to call.
GetHuman-143775's review of Weight Watchers customer service
GetHuman: So how would you sum up your experience for GetHuman's Weight Watchers 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-143775: I spoke with Kellie in AZ, call center she seemed to do a very professional job I'll know it's accurate if I'm not charged next month.
GetHuman: Let's quantify your experience contacting Weight Watchers. On a scale of 1 to 5, how easy is it go get help on a Weight Watchers problem?
GetHuman-143775: 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-143775: I'd give them a four out of five on communication.
GetHuman: And what about Weight Watchers's ability to quickly and effectively address your problem?
GetHuman-143775: For that I would say three out of five.
GetHuman: And finally- any advice for other Weight Watchers customers?
GetHuman-143775: Call them early in the day or late. Don't forget any personal or account information you might need for Weight Watchers to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-143775 taken from his Weight Watchers customer service problem that occurred on November 7th, 2017.