Does anyone know why London Midland seem incapable of making the correct automated announcements - particularly on southbound Crewe-Esuton services at Northampton?
Time after time - either at Northampton or shortly after leaving - we are told that the train is bound for Euston (at least that is correct), stopping at Alsager..., and that the first stop is Alsager. Cue mirth from those in the know, lots of questions from those that do not.
I could list countless other instances of incorrect LM on-train announcements. Only today those sitting in the Birmingham portion of a northbound service that divided at Northampton were told the first stop would be Wolverton!
Is the system that difficult to operate? Or is there some problem with the software specific to Northampton?
And given this nearly always happens, why isn't the automated system turned off (at least here) and manual announcements used instead?
Time after time - either at Northampton or shortly after leaving - we are told that the train is bound for Euston (at least that is correct), stopping at Alsager..., and that the first stop is Alsager. Cue mirth from those in the know, lots of questions from those that do not.
I could list countless other instances of incorrect LM on-train announcements. Only today those sitting in the Birmingham portion of a northbound service that divided at Northampton were told the first stop would be Wolverton!
Is the system that difficult to operate? Or is there some problem with the software specific to Northampton?
And given this nearly always happens, why isn't the automated system turned off (at least here) and manual announcements used instead?