Extended StayAmerica: ** minute wait, then left messages on * separat...
A Extended StayAmerica customer review by GetHuman user ~Michele from November 26th, 2017
Background on ~Michele's case
GetHuman: ~Michele - can you tell our other Extended StayAmerica customers when your case took place?
~Michele: Yes. It was morning, on November 25th.
GetHuman: Did you reach out to Extended StayAmerica, and if so, how?
GetHuman: And which of these common Extended StayAmerica customer issues best describes the reason you wanted to talk to them?
(Shows ~Michele a list of common Extended StayAmerica problems)
~Michele: "Change booking" was why I was trying to call.
~Michele's review of Extended StayAmerica customer service
GetHuman: So how would you sum up your experience for GetHuman's Extended StayAmerica 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.
~Michele: ** minute wait, then left messages on * separate calls, with no call back from management. Dirty, smelly property with no towels or supplies, and managers who do not care.
GetHuman: Let's quantify your experience contacting Extended StayAmerica. On a scale of 1 to 5, how easy is it go get help on a Extended StayAmerica problem?
~Michele: I'd give them a one 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?
~Michele: I'd give them a one out of five on communication.
GetHuman: And what about Extended StayAmerica's ability to quickly and effectively address your problem?
~Michele: For that I would say four out of five.
GetHuman: And finally- any advice for other Extended StayAmerica customers?
~Michele: Call them early in the day or late. Don't forget any personal or account information you might need for Extended StayAmerica to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Michele taken from his Extended StayAmerica customer service problem that occurred on November 25th, 2017.