Originally Posted by
ByeByeDelta
I recall reading that deep down in Arrow, all reservations have been built as eTickets for quite a while. It makes sense now that the front-end for eTickets is enabled, all qualifying reservations not printed to paper can be used as an eTicket.
Report:
I was about the 5th in the queue for the checker at NYP. Had the QR code ready on my iPhone via the iPhone AMTK app. Took the checker 5 seconds to realize i didn't have a paper ticket, and then sort of flustered said uhhhh, looked at the phone, and then waived me on my way. I have to give her credit... it only took about 15 second (10 seconds or so longer than paper)... not bad for the first day.
And the train details aren't real clear on the phone presentation... checker has to look at the very top for origin confirmation, and then the very bottom for train number to confirm... and this is assuming that the user hasn't scrolled up, removing the train information... I would have thought they would put the train number at the header with the date/origin/destination.
On the train, the conductor was happy to see the code. She said she was actually having more issues with "travel document" scans (e.g. the doc now printed by qwiktrak). Apparently some of the printers need recalibrating to printer a proper bar code. My phone scanned in half a second and she was on her way.
Overall an A day for go live. Nicely done Amtrak.
Suggestions:
- reconfigure the phone app to make it easier on the checkers
- qwiktrak printer testing to make sure print outs are within tolerance limits for scanners