Amtrak: Due to the recent train crash in CT and the sub...
A Amtrak customer review by GetHuman user ~Anonymous from November 16th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Amtrak customers when your case took place?
~Anonymous: Yup. It was evening, on November 12th.
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 ~Anonymous a list of common Amtrak problems)
~Anonymous: "Missing Items" was why I was trying to call.
~Anonymous'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.
~Anonymous: Due to the recent train crash in CT and the subsequent "indefinite" cancelation of all trains past NY, I was worried about my train being canceled. I called their posted *-*** number and it was a ** minute wait! I called this number and waited less than a minute. Customer service was personable and excellent and I was on and off in five minutes.
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?
~Anonymous: I'd give them a four 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 three out of five on communication.
GetHuman: And what about Amtrak's ability to quickly and effectively address your problem?
~Anonymous: For that I would say two out of five.
GetHuman: And finally- any advice for other Amtrak customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Amtrak to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Amtrak customer service problem that occurred on November 12th, 2017.