- A simplified claims process must be in place to make it easy for passengers to submit claims for delay compensation.
Yes, but not in the way it works now: Specify a standard API, force all the TOCs to implement it and let retailers submit the delay repay claims on the passenger's behalf.
Ideally there'd be a way to automatically route the claim to the appropriate TOC too, via some centralised mediator service, so that the passenger doesn't need to worry about "well Avanti was 5 minutes late, but that meant I missed my connection with West Midlands Rail and then that service was late so who do I send my claim to?" thinking. All of this should be handled for the passenger.
This nonsense where we ask the passengers to re-enter every last detail about their tickets, journey, purchase price, name, address, itinerary etc is ridiculous and serves simply to make the process convoluted for customers. Customers are not data-entry monkeys. The retailer already knows 99% of this, why are we wasting passengers' time?
We also immediately eliminate the confusion over whether it's the retailer or TOC that needs contacting for e.g. abandoned journeys after disruption with an approach like this.
The happy path should use the selected itinerary at booking time - but
of course any UI should enable the user to indicate they travelled on a different set of services for more complex cases. TOCs should review these manually following submission via the API.
This would go a way to improving the delay repay experience and enable retailers to handle this pain point in a large proportion of cases. It's already an uneven playing field given TOCs can offer automatic delay repay.