My supervisor had a paid Amtrak ticket from Phi...
A Amtrak customer review by GetHuman user ~Executive Assistant from November 16th, 2017
Background on ~Executive Assistant's case
GetHuman: ~Executive Assistant - can you tell our other Amtrak customers when your case took place?
~Executive Assistant: Yeah. It was morning, on November 15th.
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 ~Executive Assistant a list of common Amtrak problems)
~Executive Assistant: "Loyalty program" was why I was trying to call.
~Executive Assistant'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.
~Executive Assistant: My supervisor had a paid Amtrak ticket from Philadelphia to NY. Amtrak allowed someone else to use this ticket without his knowledge. My supervisor ended up paying for a whole new ticket. Amtrak refused to return the money.
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?
~Executive Assistant: 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?
~Executive Assistant: 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?
~Executive Assistant: For that I would say two out of five.
GetHuman: And finally- any advice for other Amtrak customers?
~Executive Assistant: 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 ~Executive Assistant taken from his Amtrak customer service problem that occurred on November 15th, 2017.