Amtrak: Great service, I would like to suggest that u p...
Amtrak Ulasan pelanggan oleh pengguna GetHuman GetHuman-167863 dari November 15, 2017
Background on GetHuman-167863's case
GetHuman: GetHuman-167863 - can you tell our other Amtrak customers when your case took place?
GetHuman-167863: Yup. It was afternoon, on November 14.
GetHuman: Did you reach out to Amtrak, and if so, how?
GetHuman: And which of these common Amtrak customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-167863 a list of common Amtrak problems)
GetHuman-167863: "Change booking" was why I was trying to call.
GetHuman-167863's review of Amtrak customer service
GetHuman: So how would you sum up your experience for GetHuman's Amtrak 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.
GetHuman-167863: Great service, I would like to suggest that u put another business class car on the train from St Louis to Chicago. I often cannot get in business class for lack of availability. Amtrak can make a lot more money if they would put another business class car on this route
GetHuman: Let's quantify your experience contacting Amtrak. On a scale of 1 to 5, how easy is it go get help on a Amtrak problem?
GetHuman-167863: 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?
GetHuman-167863: I'd give them a five out of five on communication.
GetHuman: And what about Amtrak's ability to quickly and effectively address your problem?
GetHuman-167863: For that I would say five out of five.
GetHuman: And finally- any advice for other Amtrak customers?
GetHuman-167863: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Amtrak mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-167863 taken from his Amtrak customer service problem that occurred on November 14, 2017.