TripAdvisor: I did get a real person, and he listened polite...
Una recensione del cliente TripAdvisor da parte dell'utente GetHuman ~anonymous da novembre 27º, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other TripAdvisor customers when your case took place?
~anonymous: Sure. It was afternoon, on novembre 19º.
GetHuman: Did you reach out to TripAdvisor, and if so, how?
GetHuman: And which of these common TripAdvisor customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common TripAdvisor problems)
~anonymous: "Update Listing" was why I was trying to call.
~anonymous's review of TripAdvisor customer service
GetHuman: So how would you sum up your experience for GetHuman's TripAdvisor 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.
~anonymous: I did get a real person, and he listened politely to my problem (being scammed by a hotel I booked through tripadvisor), but he had no solution, ideas, or recourse and just patched me back through to the hotel in question.
GetHuman: Let's quantify your experience contacting TripAdvisor. On a scale of 1 to 5, how easy is it go get help on a TripAdvisor problem?
~anonymous: 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?
~anonymous: I'd give them a four out of five on communication.
GetHuman: And what about TripAdvisor's ability to quickly and effectively address your problem?
~anonymous: For that I would say three out of five.
GetHuman: And finally- any advice for other TripAdvisor customers?
~anonymous: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per TripAdvisor sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his TripAdvisor customer service problem that occurred on novembre 19º, 2017.