This might actually be the worst thing Trainline has done.
The Pointy Haired Boss character from Dilbert didn't come from nowhere... Honestly generative AI probably has a place but most of the time Richard Stallman gets it right - it's a bull**** generator and that's the last thing you want for giving advice that could have legal consequences.The management decisions behind procuring and releasing this stuff baffles me.
If they did, I've got a feeling that if a case came to court, the court would take a very dim view of that tactic:
"Here's our helpful AI chatbot to give you advice about your ticket!" **
** Any advice given may be complete nonsense, and if you follow it you may be liable for an excess fare, a penalty fare or prosecution.
Disclaimers like this - as I understand it - are only legally valid under consumer law if they are considered fair and reasonable.
WHY on earth would you use a LLM, which is general-purpose, behind a robot working in a specific domain such as GB rail ticketing???
This domain has specific rules, admittedly weird in places, validation requirements for retailing, a knowledgebase and so on. Surely you train the model on that body of data. Then it should spew out the relevant restriction (in human-speak such as 'you can use any train on a Sunday') and totally understand passenger types adult/child/railcard/combinations.
Not necessarily. While you could fine tune it, you could also implement this fairly easily with a general purpose model. In simple terms the LLM should not be reasoning itself but instead summarising some clear information spit out by a conventional piece of software (which I'm assuming Trainline already have) about the ticket (and if that piece of software can't accept a query about, say, age simply refusing to answer rather than coming up with nonsense). See this link for how it's implemented on one popular API
I’m not so sure about this. They could get it doing the basics, which it can’t now, such as explaining railcard restrictions, but otherwise it’s use cases are limited. Maybe it could interpret the public restriction text better in some cases, but I’d say that’s unlikely.In simple terms the LLM should not be reasoning itself but instead summarising some clear information spit out by a conventional piece of software (which I'm assuming Trainline already have) about the ticket
I’m not so sure about this. They could get it doing the basics, which it can’t now, such as explaining railcard restrictions, but otherwise it’s use cases are limited. Maybe it could interpret the public restriction text better in some cases, but I’d say that’s unlikely.
I don’t see how it could parse the existing electronic information, you’d end up with it telling people they can’t depart Reading on London Underground and LNER before 9:30!
It doesn't have to parse the existing electronic information. Trainline will (I assume) already have something that does that. What it would need to do is essentially convert the user's question into a query of that information which would then be passed into this already existing thing, and then interpret the results the existing thing will spit out. I'm highly confident it would work.
Do they have the ability to do this? I haven’t used Trainline recently but last time I used that feature (Years ago) it seemed to refund and reissue my ticket, and it seemed to just do a new search and compare prices rather than what the ticket was actually valid for.It doesn't have to parse the existing electronic information. Trainline will (I assume) already have something that does that. What it would need to do is essentially convert the user's question into a query of that information which would then be passed into this already existing thing, and then interpret the results the existing thing will spit out. I'm highly confident it would work.
Do they have the ability to do this? I haven’t used Trainline recently but last time I used that feature (Years ago) it seemed to refund and reissue my ticket, and it seemed to just do a new search and compare prices rather than what the ticket was actually valid for.
They need to be able to surface valid tickets in the search results of course, but the kind of backwards search from tickets is quite a different flow that you need to implement specifically. Much harder if your journey planning is outsourced too and they don't support itSomeone like @Adam Williams would know better about the kind of things accreddited retailers need but I assume ticket validation is part of it (although it's possible it's sufficient to be able to find valid tickets rather than the other way around). Even if they don't have it they certainly would have the expertise to build it.
“Our customer support team remains on hand. Our priority is helping customers cut through the complexity of rail.”
Nice to see a publication run with a story about it.Seems like there’s already a news outlet that noticed it:
![]()
Trainline’s new AI customer assistant veers off the rails
Among other errors, bot insists an adult can travel with child’s ticketobserver.co.uk