London Transport (uk.transport.london) Discussion of all forms of transport in London.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1   Report Post  
Old February 13th 15, 09:43 PM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Jul 2003
Posts: 329
Default Oyster charging for journeys that don't happen

On 13/02/2015 6:23 AM, Roland Perry wrote:

"If you touch in on a yellow card reader to make a journey and
then decide you don't want to make it or you can't because of
service disruption and touch out again to exit your Oyster card
will be charged. We apply charges to discourage fare evasion.
However, you may be able to get a refund if this happens."

The burden here is far too much on the innocent traveller.

The alternative is for the gateline assistant to let everyone out
*without* touching out, and then go to the Ticket Office to get the
touch *in* cancelled...except that's not an option at Waterloo because
SWT don't "do" Oyster at Ticket Offices, and even if they did, you'd
have missed half a dozen trains by the time you got to the front of the
queue. (Possibly a slight exaggeration).

A Ticket Office is unable to resolve a "double touch" where an OSI is
involved, as they can only cancel the last *exit* touch. So if you were
travelling Piccadilly Circus - Waterloo (LU) - Waterloo (NR) -
Wimbledon and such a situation occurred, the exit touch at Waterloo (NR)
would have to be cancelled, and then you'd have to go back down to the
Underground station and touch *out* again to close the journey
properly...assuming you were still within the maximum journey time.

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...

Cheers,

Barry

  #2   Report Post  
Old February 14th 15, 07:38 AM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Aug 2003
Posts: 10,125
Default Oyster charging for journeys that don't happen

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

"If you touch in on a yellow card reader to make a journey and
then decide you don't want to make it or you can't because of
service disruption and touch out again to exit your Oyster card
will be charged. We apply charges to discourage fare evasion.
However, you may be able to get a refund if this happens."

The burden here is far too much on the innocent traveller.

The alternative is for the gateline assistant to let everyone out
*without* touching out, and then go to the Ticket Office to get the
touch *in* cancelled...except that's not an option at Waterloo because
SWT don't "do" Oyster at Ticket Offices,


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

and even if they did, you'd have missed half a dozen trains by the time
you got to the front of the queue. (Possibly a slight exaggeration).

A Ticket Office is unable to resolve a "double touch" where an OSI is
involved, as they can only cancel the last *exit* touch. So if you were
travelling Piccadilly Circus - Waterloo (LU) - Waterloo (NR) -
Wimbledon and such a situation occurred, the exit touch at Waterloo
(NR) would have to be cancelled, and then you'd have to go back down to
the Underground station and touch *out* again to close the journey
properly...


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.

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?

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.
--
Roland Perry
  #3   Report Post  
Old February 14th 15, 01:58 PM posted to uk.transport.london
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...
  #4   Report Post  
Old February 17th 15, 12:19 PM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Oct 2006
Posts: 1,392
Default Oyster charging for journeys that don't happen

On Sat, Feb 14, 2015 at 02:58:40PM +0000, Barry Salter wrote:
On 14/02/2015 8:38 AM, Roland Perry wrote:
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...


To be fair they *are* more convenient if you assume that there are no
systematic errors. And this is a common assumption amongst employees of
companies that have complex customer-facing systems - it's far too easy
to think that it's the user's fault for doing something wrong when the
real problem is that the system is too complex for the user to have a
hope in hell of getting everything right.

--
David Cantrell | Minister for Arbitrary Justice

Good advice is always certain to be ignored,
but that's no reason not to give it -- Agatha Christie
  #5   Report Post  
Old February 14th 15, 09:05 PM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Jun 2009
Posts: 164
Default Oyster charging for journeys that don't happen

On 13/02/2015 22:43, Barry Salter wrote:

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...


Has the Oyster telephone Helpline improved recently? I ask because my
only experiences of using it (a couple of years ago) involved hanging on
the phone for at between 20 and 30 minutes each time. Had I not been
using my included minutes on the phone this would have completely
negated the value that I eventually got restored to my Oyster card.


--
Clive Page


  #7   Report Post  
Old February 17th 15, 12:20 PM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Oct 2006
Posts: 1,392
Default Oyster charging for journeys that don't happen

On Sat, Feb 14, 2015 at 10:05:19PM +0000, Clive Page wrote:
On 13/02/2015 22:43, Barry Salter wrote:
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...

Has the Oyster telephone Helpline improved recently?


Top tip:

--
David Cantrell | top google result for "internet beard fetish club"

I don't do .INI, .BAT, or .SYS files. I don't assign apps to files.
I don't configure peripherals or networks before using them. I have
a computer to do all that. I have a Macintosh, not a hobby.
-- Fritz Anderson
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Oyster error - how does this happen tim...... London Transport 46 November 6th 13 06:19 PM
They said it would never happen... Paul Scott London Transport 3 November 20th 09 01:04 PM
Why would this happen? Boltar London Transport 4 December 5th 07 10:56 AM
Oh dear.....I'm sure it wont happen. Malcolm & Nika London Transport 21 December 11th 04 11:37 AM
What will happen to KX Thameslink? Heliomass London Transport 46 April 13th 04 11:38 AM


All times are GMT. The time now is 10:09 PM.

Powered by vBulletin®
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 London Banter.
The comments are property of their posters.
 

About Us

"It's about London Transport"

 

Copyright © 2017