Amtrak: After listening to the recording, waited perhap...
A Amtrak customer review by GetHuman user GetHuman-331410 from November 19th, 2017
Background on GetHuman-331410's case
GetHuman: GetHuman-331410 - can you tell our other Amtrak customers when your case took place?
GetHuman-331410: Yes I can. It was evening, on November 17th.
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-331410 a list of common Amtrak problems)
GetHuman-331410: "Change booking" was why I was trying to call.
GetHuman-331410'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-331410: After listening to the recording, waited perhaps ** seconds for agent to pick up. Considering earlier wait times have been in excess of * to ** min, this was awesome! *Agent tried to connect me to line for making hotel reservations, but I was hung up on.
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-331410: 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-331410: I'd give them a two out of five on communication.
GetHuman: And what about Amtrak's ability to quickly and effectively address your problem?
GetHuman-331410: For that I would say five out of five.
GetHuman: And finally- any advice for other Amtrak customers?
GetHuman-331410: 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 GetHuman-331410 taken from his Amtrak customer service problem that occurred on November 17th, 2017.