Trainline has launched a wonderful new "AI" assistant feature after you purchase a ticket from their app(/site?).
One of the first things I asked it, after buying a child ticket, was whether I could travel on it as a 28 year old adult. Unsurprisingly, the answer was... yes.
I then went on to ask about time restrictions on my ticket, which TTL have decided to omit from whatever information bank the agent is provided with as it simply informs be about "general" off-peak timings (after 0930).
I also tried to process a refund via the chatbot. It first broke the bot and told me it was now "unavailable" as something went wrong. The second (and subequent) times, it told me that a refund had been processed. It hadn't.
I see this as a minefield for potential future problems for passengers, and really should never have been done. Humans struggle to understand ticketing restrictions a lot of the time, let alone a large language model that isn't particularly specialised, nor has sufficient data to answer real questions.
One of the first things I asked it, after buying a child ticket, was whether I could travel on it as a 28 year old adult. Unsurprisingly, the answer was... yes.
Me: Does that mean I can travel on this ticket as a 28 year old?
"AI": Yes, absolutely! As a 28-year-old, you can definitely travel on this Off-Peak Day Return ticket between Burgess Hill and Wivelsfield. This ticket is valid for adult passengers. Just remember to adhere to the off-peak travel times and the specific date on your ticket (Sun 8 Jun 2025). Your outbound journey is scheduled for 20:43 from Burgess Hill to Wivelsfield, and your return is at 21:33 from Wivelsfield to Burgess Hill. Is there anything else you'd like to know about your journey or ticket?
I then went on to ask about time restrictions on my ticket, which TTL have decided to omit from whatever information bank the agent is provided with as it simply informs be about "general" off-peak timings (after 0930).
I also tried to process a refund via the chatbot. It first broke the bot and told me it was now "unavailable" as something went wrong. The second (and subequent) times, it told me that a refund had been processed. It hadn't.
I see this as a minefield for potential future problems for passengers, and really should never have been done. Humans struggle to understand ticketing restrictions a lot of the time, let alone a large language model that isn't particularly specialised, nor has sufficient data to answer real questions.