Weight Watchers: I called and did not wait long for assistance...
A Weight Watchers customer review by GetHuman user GetHuman-136000 from November 16th, 2017
Background on GetHuman-136000's case
GetHuman: GetHuman-136000 - can you tell our other Weight Watchers customers when your case took place?
GetHuman-136000: Yes I can. It was morning, on November 12th.
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-136000 a list of common Weight Watchers problems)
GetHuman-136000: "Update Account Info" was why I was trying to call.
GetHuman-136000'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-136000: I called and did not wait long for assistance, Michael was able to solve the problem within minutes and was very courteous and professional
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-136000: 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-136000: I'd give them a three out of five on communication.
GetHuman: And what about Weight Watchers's ability to quickly and effectively address your problem?
GetHuman-136000: For that I would say two out of five.
GetHuman: And finally- any advice for other Weight Watchers customers?
GetHuman-136000: 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-136000 taken from his Weight Watchers customer service problem that occurred on November 12th, 2017.