Mariott Rewards: This number does take you to a natural-language...
A Mariott Rewards customer review by GetHuman user ~acz from November 12th, 2017
Background on ~acz's case
GetHuman: ~acz - can you tell our other Mariott Rewards customers when your case took place?
~acz: Yes. It was afternoon, on November 4th.
GetHuman: Did you reach out to Mariott Rewards, and if so, how?
GetHuman: And which of these common Mariott Rewards customer issues best describes the reason you wanted to talk to them?
(Shows ~acz a list of common Mariott Rewards problems)
~acz: "Insurance claim" was why I was trying to call.
~acz's review of Mariott Rewards customer service
GetHuman: So how would you sum up your experience for GetHuman's Mariott 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.
~acz: This number does take you to a natural-language robot who tries to steer your call. If you really need a human, you will have to say "agent" and give the robot some additional information, such as your membership number. But you will be switched to an agent eventually.
GetHuman: Let's quantify your experience contacting Mariott Rewards. On a scale of 1 to 5, how easy is it go get help on a Mariott Rewards problem?
~acz: 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?
~acz: I'd give them a two out of five on communication.
GetHuman: And what about Mariott Rewards's ability to quickly and effectively address your problem?
~acz: For that I would say three out of five.
GetHuman: And finally- any advice for other Mariott Rewards customers?
~acz: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Mariott Rewards to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~acz taken from his Mariott Rewards customer service problem that occurred on November 4th, 2017.