Fairfield Inn and Suites: Blew me off. I have a damaged vehicle parked in...
A Fairfield Inn and Suites customer review by GetHuman user ~BCS1999 from November 27th, 2017
Background on ~BCS1999's case
GetHuman: ~BCS1999 - can you tell our other Fairfield Inn and Suites customers when your case took place?
~BCS1999: Yes. It was afternoon, on November 22nd.
GetHuman: Did you reach out to Fairfield Inn and Suites, and if so, how?
GetHuman: And which of these common Fairfield Inn and Suites customer issues best describes the reason you wanted to talk to them?
(Shows ~BCS1999 a list of common Fairfield Inn and Suites problems)
~BCS1999: "Insurance claim" was why I was trying to call.
~BCS1999's review of Fairfield Inn and Suites customer service
GetHuman: So how would you sum up your experience for GetHuman's Fairfield Inn and Suites 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.
~BCS1999: Blew me off. I have a damaged vehicle parked in their valet parking. Told me to deal with it myself.
GetHuman: Let's quantify your experience contacting Fairfield Inn and Suites. On a scale of 1 to 5, how easy is it go get help on a Fairfield Inn and Suites problem?
~BCS1999: 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?
~BCS1999: I'd give them a two out of five on communication.
GetHuman: And what about Fairfield Inn and Suites's ability to quickly and effectively address your problem?
~BCS1999: For that I would say three out of five.
GetHuman: And finally- any advice for other Fairfield Inn and Suites customers?
~BCS1999: Call them early in the day or late. Don't forget any personal or account information you might need for Fairfield Inn and Suites to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~BCS1999 taken from his Fairfield Inn and Suites customer service problem that occurred on November 22nd, 2017.