peconicstation
Service Attendant
- Joined
- Mar 21, 2015
- Messages
- 124
Saturday, April 4th, was not a good day for the northern leg of the NEC, and poor communications (and a few toher things) just made a bad situation worse.
We were taking our usual trip from New London to Boston on train 150, (returning on 167) and all was well until we got to Providence.
At that station we were told that due to a fire along the tracks in Boston we would have to detrain and take the MBTA commuter rail train since
the commuter rail train could bypass the section of the NEC where the fire was. The fire itself was along the tracks in the Forest Hill section of Boston.
The commuter rail train did what it could and got us to Boston just before 1:00 (as opposed to just after 11:00). The train train took the Fairmont line,
something that Amtrak could only due with a diesel engine.
Now for the communications breakdown.
Train 150 had many people travelling for the day (there was also a large convention in town), and with word that the fire was out, we were trying to get a handle on what were the plans for the afternoon. Calling the 800 number, using the Amtrak mobile device, or using Julie prooved fruitless, in fact according to the mobile device train 150 was only delayed 50 minutes into Boston (when we finallly arived on commuter rail, that train set still had not made it, but was expected as the 1:40 southbound regional showed it would depart on-time). No one in the call center knew of these disruptions, until I insisted they check, and after being on hold for about 15 minutes they came back to say, oh yeah there will be delays).
Planning for our return on 167, the 4:40 out of Back Bay, the call center knew NOTHING about the status of the train, nor did the Amtrak ticket clerks at Back Bay (and yes, the Amtrak ticket counter is open again at Back Bay). The departure board only showed that the train was delayed.
Happily the train arrived at about 5:00, and got us back to New London just in time to make our ferry.
In this day and age of communication, how is it that Amtraks call center is so poorly informed of disriptions, and status ??
..........and it gets better when we boarded train 150 at New London, the conductor never checked the tickets of passengers from there and north, so our reservation wound up showing as a forfeit. That same conductor tried scanning my ticket for the return, and said, gee this is a problem.
He realized that I had a ticket, so he let us travel (I said nothing to him about it being his fault).
When I got home, I had an email from Amtrak telling me that my reservation (and payment) was forefited, it took over 30 minutes with the call center
to get that corrected, but I did.
Not a good day.
Kudos to the Commuter Rail crew for accomidating a full Amtrak train, as well as it's own passengers, and they were trying to get information for us.
It is also worth noting that the T had extra staff at Back Bay to deal with confused passengers, and direct them.
Why didn't AMTRAK do the same ????????, and if they did have extra people at South Station, and not at Back Bay, that is 100%
not acceptable.
Ken
We were taking our usual trip from New London to Boston on train 150, (returning on 167) and all was well until we got to Providence.
At that station we were told that due to a fire along the tracks in Boston we would have to detrain and take the MBTA commuter rail train since
the commuter rail train could bypass the section of the NEC where the fire was. The fire itself was along the tracks in the Forest Hill section of Boston.
The commuter rail train did what it could and got us to Boston just before 1:00 (as opposed to just after 11:00). The train train took the Fairmont line,
something that Amtrak could only due with a diesel engine.
Now for the communications breakdown.
Train 150 had many people travelling for the day (there was also a large convention in town), and with word that the fire was out, we were trying to get a handle on what were the plans for the afternoon. Calling the 800 number, using the Amtrak mobile device, or using Julie prooved fruitless, in fact according to the mobile device train 150 was only delayed 50 minutes into Boston (when we finallly arived on commuter rail, that train set still had not made it, but was expected as the 1:40 southbound regional showed it would depart on-time). No one in the call center knew of these disruptions, until I insisted they check, and after being on hold for about 15 minutes they came back to say, oh yeah there will be delays).
Planning for our return on 167, the 4:40 out of Back Bay, the call center knew NOTHING about the status of the train, nor did the Amtrak ticket clerks at Back Bay (and yes, the Amtrak ticket counter is open again at Back Bay). The departure board only showed that the train was delayed.
Happily the train arrived at about 5:00, and got us back to New London just in time to make our ferry.
In this day and age of communication, how is it that Amtraks call center is so poorly informed of disriptions, and status ??
..........and it gets better when we boarded train 150 at New London, the conductor never checked the tickets of passengers from there and north, so our reservation wound up showing as a forfeit. That same conductor tried scanning my ticket for the return, and said, gee this is a problem.
He realized that I had a ticket, so he let us travel (I said nothing to him about it being his fault).
When I got home, I had an email from Amtrak telling me that my reservation (and payment) was forefited, it took over 30 minutes with the call center
to get that corrected, but I did.
Not a good day.
Kudos to the Commuter Rail crew for accomidating a full Amtrak train, as well as it's own passengers, and they were trying to get information for us.
It is also worth noting that the T had extra staff at Back Bay to deal with confused passengers, and direct them.
Why didn't AMTRAK do the same ????????, and if they did have extra people at South Station, and not at Back Bay, that is 100%
not acceptable.
Ken