E-Rewards: Deactivated my account
A E-Rewards customer review by GetHuman user GetHuman54381 from December 8th, 2017
Background on GetHuman54381's case
GetHuman: GetHuman54381 - can you tell our other E-Rewards customers when your case took place?
GetHuman54381: Yup. It was morning, on November 28th.
GetHuman: Did you reach out to E-Rewards, and if so, how?
GetHuman: And which of these common E-Rewards customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman54381 a list of common E-Rewards problems)
GetHuman54381: "None of those really matches why I wanted to contact E-Rewards that day." was why I was trying to contact.
GetHuman54381's review of E-Rewards customer service
GetHuman: So how would you sum up your experience for GetHuman's E-Rewards 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.
GetHuman54381: Deactivated my account
GetHuman: Can you tell the rest of us a bit more from what happened on 11/28/17?
GetHuman54381: I'm trying to cash in my points for a choice hotel stay. I logged in and my account has been deactivated.
GetHuman: Let's quantify your experience contacting E-Rewards. On a scale of 1 to 5, how easy is it go get help on a E-Rewards problem?
GetHuman54381: I'd give them a three 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?
GetHuman54381: I'd give them a two out of five on communication.
GetHuman: And what about E-Rewards's ability to quickly and effectively address your problem?
GetHuman54381: For that I would say five out of five.
GetHuman: And finally- any advice for other E-Rewards customers?
GetHuman54381: Call them early in the day or late. Don't forget any personal or account information you might need for E-Rewards to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman54381 taken from his E-Rewards customer service problem that occurred on November 28th, 2017.