Courtyard by Marriott: On a scale of * (bad) to * (good) I rate the Co...
A Courtyard by Marriott customer review by GetHuman user ~Bob R. from November 25th, 2017
Background on ~Bob R.'s case
GetHuman: ~Bob R. - can you tell our other Courtyard by Marriott customers when your case took place?
~Bob R.: Yeah. It was middle of the night, on November 24th.
GetHuman: Did you reach out to Courtyard by Marriott, and if so, how?
GetHuman: And which of these common Courtyard by Marriott customer issues best describes the reason you wanted to talk to them?
(Shows ~Bob R. a list of common Courtyard by Marriott problems)
~Bob R.: "Overcharge/Strange charge" was why I was trying to call.
~Bob R.'s review of Courtyard by Marriott customer service
GetHuman: So how would you sum up your experience for GetHuman's Courtyard by Marriott 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.
~Bob R.: On a scale of * (bad) to * (good) I rate the Courtyard in Basking Ridge, NJ a ** easily and maybe higher. Just outstanding!!!
GetHuman: Let's quantify your experience contacting Courtyard by Marriott. On a scale of 1 to 5, how easy is it go get help on a Courtyard by Marriott problem?
~Bob R.: 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?
~Bob R.: I'd give them a five out of five on communication.
GetHuman: And what about Courtyard by Marriott's ability to quickly and effectively address your problem?
~Bob R.: For that I would say four out of five.
GetHuman: And finally- any advice for other Courtyard by Marriott customers?
~Bob R.: Call them early in the day or late. Don't forget any personal or account information you might need for Courtyard by Marriott to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Bob R. taken from his Courtyard by Marriott customer service problem that occurred on November 24th, 2017.