View Single Post
  #32   Report Post  
Old February 14th 15, 01:58 PM posted to uk.transport.london
Barry Salter Barry Salter is offline
external usenet poster
 
First recorded activity at LondonBanter: Jul 2003
Posts: 329
Default Oyster charging for journeys that don't happen

On 14/02/2015 8:38 AM, Roland Perry wrote:
In message , at 22:43:23 on Fri, 13
Feb 2015, Barry Salter remarked:
On 13/02/2015 6:23 AM, Roland Perry wrote:


What if the traveller was using Contactless - can the SWT ticket offices
deal with hiccups then?


Contactless issues are a Helpdesk job, unfortunately.


Would that require you to find someone to let you back airside in order
to come back with a touch-out? I'd be reluctant to touch-in, in case it
triggered yet another layer of problems.


Depends on how the gateline's laid out, and how busy it is. You may just
be able to lean over from an adjacent gate and do it yourself.

assuming you were still within the maximum journey time.


Given that the exercise started when SWT cancelled a train, would Delay
Repay allow you to add the time queuing at the ticket office to the
overall journey delay?


SWT still work on the "old" Passenger Charter system, rather than Delay
Repay, so probably...Point's moot anyway, given they don't do Oyster.

Or you just wait 'til the following day and go to the Oyster website
(assuming your card is registered) or phone the Helpdesk and they'll
sort it out for you with significantly less faffing around...


What a performance! Just because SWT was a driver short.


Yup...But TfL will still you that Oyster/Contactless are so much more
"convenient" for passengers than paper tickets...