• Our booking engine at tickets.railforums.co.uk (powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!

Mobile Ticket Endorsements

Status
Not open for further replies.

sheff1

Established Member
Joined
24 Dec 2009
Messages
5,459
Location
Sheffield
Split From: LNER/TP Ticket Issue

The company that charged you for the replacement ticket needs to understand that they should be honouring the contract. If there is an issuing error, they may withdraw the original ticket and issue a free of charge replacement, or they can endorse the original ticket. They cannot charge the customer.

A bit of an aside which you may want to transfer to a new thread, but how does someone withdraw or endorse the original ticket when it is held on a mobile device ?
 
Last edited by a moderator:
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

trentside

Established Member
Fares Advisor
Joined
14 Aug 2010
Messages
3,337
Location
Messroom
So I assume that if the ticket is scanned again afterwards it will return a message "withdrawn" or giving details of the endorsement ?

It should, yes.

My only experience is with TTK (Ticket Keeper), but other software is available. We have the ability to add endorsements (or comments) on to mobile or e-tickets, which should show up when scanned by other revenue staff. The most common endorsement would be a request to pass on another service due to a delay or cancellation, for the time being I continue to also issue a new itinerary with an endorsement on, as I can't guarantee that the ticket will always be scanned.

When scanning a ticket with TTK it will do a few different things:
  • GREEN - Straightforward point to point ticket, valid on the train service you are working, between two stations served by that journey. It advises to accept the ticket.
  • ORANGE - Check. Advises you to check the ticket, as it requires a change of train or has discount applied (e.g. 16-25, DSB etc)
  • RED - Reject. This will flash up for a wrong time train, previously clipped or used to exit at destination previously. Also for endorsements or a cancellation such as a refunded ticket.
Where a ticket has been previously used to complete a journey and scanned at an exit barrier, it is accurate to the second as to when they exited. For example, it will say "Exit BHM. 14/06/19 12:22:23".

If it's a case where a ticket has been refunded, it is similarly accurate and can tell you exactly when this was requested.
 

robbeech

Established Member
Joined
11 Nov 2015
Messages
4,622
On LNER when you scan a ticket the scanner itself will tell you if it's accepted or not with a beep or a buzz.

Which is good, providing the guard reads the response and analyses the ticket when it is rejected to ensure it makes sense to reject it. It’s fairly common for tickets to be rejected by your system and .............

I can see the red one meaning more BoJ disputes. Surely it should just be OK or check.

This does mean this. If you hold an M ticket flavoured SVR or SOR and break your return journey overnight the ticket changes to ‘used ticket’ overnight and is rejected the following day or days by gatelines and machines including those used by LNER. This requires staff to have actual knowledge about ticketing which I’m sad to say seems to fall down quite a lot. I’ve had a couple of minor disputes with LNER staff about this but they have ended in being allowed to travel on my valid ticket after an unnecessarily lengthy explanation of the rules. It’s very important to note that I’ve also had numerous scans that have been rejected but then allowed manually on closer inspection. Other TOCs responses vary in the same way.
I agree that unless it can provide an absolute guarantee of accuracy* then it should be limited to ACCEPT or CHECK.



* let’s face it this isn’t possible. There are countless tickets valid on trains where a guard would say it’s not valid. There are tickets valid on a technicality. Tickets valid for travel after 1000 that wouldn’t normally be valid on that train but disruption has caused it to be valid may be handled badly by the machine.
A ticket that isn’t ordinarily valid but is sold with an itinerary from a poorly coded website or app thus making it valid would be rejected.
And of course the obvious one, a ticket for an earlier service where a passenger is delayed and misses a connection will be rejected. Many TOCs don’t and indeed can’t scan tickets so there’s no way to endorse them.
 

trentside

Established Member
Fares Advisor
Joined
14 Aug 2010
Messages
3,337
Location
Messroom
Which is good, providing the guard reads the response and analyses the ticket when it is rejected to ensure it makes sense to reject it. It’s fairly common for tickets to be rejected by your system and .............



This does mean this. If you hold an M ticket flavoured SVR or SOR and break your return journey overnight the ticket changes to ‘used ticket’ overnight and is rejected the following day or days by gatelines and machines including those used by LNER. This requires staff to have actual knowledge about ticketing which I’m sad to say seems to fall down quite a lot. I’ve had a couple of minor disputes with LNER staff about this but they have ended in being allowed to travel on my valid ticket after an unnecessarily lengthy explanation of the rules. It’s very important to note that I’ve also had numerous scans that have been rejected but then allowed manually on closer inspection. Other TOCs responses vary in the same way.
I agree that unless it can provide an absolute guarantee of accuracy* then it should be limited to ACCEPT or CHECK.



* let’s face it this isn’t possible. There are countless tickets valid on trains where a guard would say it’s not valid. There are tickets valid on a technicality. Tickets valid for travel after 1000 that wouldn’t normally be valid on that train but disruption has caused it to be valid may be handled badly by the machine.
A ticket that isn’t ordinarily valid but is sold with an itinerary from a poorly coded website or app thus making it valid would be rejected.
And of course the obvious one, a ticket for an earlier service where a passenger is delayed and misses a connection will be rejected. Many TOCs don’t and indeed can’t scan tickets so there’s no way to endorse them.

I absolutely agree with this. I certainly think that m-tickets and the checking systems as they stand have major flaws, further hampered by the useless ticket training provided by so many TOCs. The issue of BOJ requires someone with the right knowledge, and we know that’s hit and miss.

I have more to add, but I’m out and about at the moment, so will add further later.
 

Wallsendmag

Established Member
Joined
11 Dec 2014
Messages
5,132
Location
Wallsend or somewhere in GB
Which is good, providing the guard reads the response and analyses the ticket when it is rejected to ensure it makes sense to reject it. It’s fairly common for tickets to be rejected by your system and .............



This does mean this. If you hold an M ticket flavoured SVR or SOR and break your return journey overnight the ticket changes to ‘used ticket’ overnight and is rejected the following day or days by gatelines and machines including those used by LNER. This requires staff to have actual knowledge about ticketing which I’m sad to say seems to fall down quite a lot. I’ve had a couple of minor disputes with LNER staff about this but they have ended in being allowed to travel on my valid ticket after an unnecessarily lengthy explanation of the rules. It’s very important to note that I’ve also had numerous scans that have been rejected but then allowed manually on closer inspection. Other TOCs responses vary in the same way.
I agree that unless it can provide an absolute guarantee of accuracy* then it should be limited to ACCEPT or CHECK.



* let’s face it this isn’t possible. There are countless tickets valid on trains where a guard would say it’s not valid. There are tickets valid on a technicality. Tickets valid for travel after 1000 that wouldn’t normally be valid on that train but disruption has caused it to be valid may be handled badly by the machine.
A ticket that isn’t ordinarily valid but is sold with an itinerary from a poorly coded website or app thus making it valid would be rejected.
And of course the obvious one, a ticket for an earlier service where a passenger is delayed and misses a connection will be rejected. Many TOCs don’t and indeed can’t scan tickets so there’s no way to endorse them.
m-Tickets have seen their day and are on their way out. The LNER brief specifically mentions that ticket that turn grey are still valid with their normal validity dates.
 
Status
Not open for further replies.

Top