Sam's Club: Transferred to banking unit. contact person eit...
A Sam's Club customer review by GetHuman user ~gozaimus from November 22nd, 2017
Background on ~gozaimus's case
GetHuman: ~gozaimus - can you tell our other Sam's Club customers when your case took place?
~gozaimus: Yup. It was middle of the night, on November 19th.
GetHuman: Did you reach out to Sam's Club, and if so, how?
GetHuman: And which of these common Sam's Club customer issues best describes the reason you wanted to talk to them?
(Shows ~gozaimus a list of common Sam's Club problems)
~gozaimus: "Cancel Account" was why I was trying to call.
~gozaimus's review of Sam's Club customer service
GetHuman: So how would you sum up your experience for GetHuman's Sam's Club 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.
~gozaimus: Transferred to banking unit. contact person either had poor English skills or worse listening skill. Had to repeat all information at least twice. : *** ***-**** is the telemarketing number. The next call from them will result in a phone call to the State Attorney General.
GetHuman: Let's quantify your experience contacting Sam's Club. On a scale of 1 to 5, how easy is it go get help on a Sam's Club problem?
~gozaimus: 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?
~gozaimus: I'd give them a three out of five on communication.
GetHuman: And what about Sam's Club's ability to quickly and effectively address your problem?
~gozaimus: For that I would say five out of five.
GetHuman: And finally- any advice for other Sam's Club customers?
~gozaimus: Call them early in the day or late. Don't forget any personal or account information you might need for Sam's Club to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~gozaimus taken from his Sam's Club customer service problem that occurred on November 19th, 2017.