Announcement

Collapse
No announcement yet.

SQ changed my original seats in my booking

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • SQ changed my original seats in my booking

    I believe Savage25 had posted on TOF regarding the call to SQ for being bumped out from the original seat.

    So, it happened to me this morning just before I was going to get my booking ticketed, A visit to "My Booking" and then the PNR on the SQ website revealed that my seats on SQ 25 and SQ 235 had been changed from what had been confirmed last month.

    My 20H on SQ 25 was changed to 22C and my 14K on SQ 235 to 19A.

    I decided to call the SQ reservation center in SIN to make the inquiry and the conversation went like this:

    UMD: Good Morning XXX, I am confused why my confirmed seats have been changed on 2 sectors.
    SQ: Oh...can you advise your booking code please?
    UMD: (Booking Code communicated). Why did my seats allocation which have been confirmed since last month on SQ 25 and SQ 235 changed?
    SQ: Let me check, sir..........
    SQ: You have reserved 22C on SQ25?
    UMD: No, I had 20H upperdeck confirmed. I had the printout from the website from 3 weeks ago and it was clearly on 20H.
    SQ: Ok sir, let me check...........Yes, sir I change it now to 20H.
    UMD: And on SQ 235, why was my seat changed from 14K to 19A?
    SQ: You prefer windows seat, sir?
    UMD: Yes, but I do not want 19A. What has happened to my 14K?
    SQ: We do have 11A and it is also window and on the front section? Do you want it, sir? (nice comeback, I think )
    UMD: (So impressed with her comeback especially I recalled that last month 11A was taken) Yes, that will be fine.
    SQ: I have changed it now to 11A sir. Anything else, sir?
    UMD: No, thank you.
    SQ: You are welcome, sir.

    Now, it did work out finally. But, what would have happened if I did not bother to check my booking this morning and only to find out about this on the day I check in my flight? I am sure I would be very dissapointed. (Although the chance of this happening is slim since I do check SQ website almost daily ). But I would be dissapointed for sure if my call to SQ center this morning could not get me back on my few preferred seatings.

    I hope I am not being a PITA about this (because some higher up TPP could get the seat or (in the case of 14K on 77W) there may be a parent traveling with a baby that needs the seat. But, what is the point of having the benefit to select our preferred seat if this can be changed without being notified? I know this rarely happens but I think SQ should have a system that can send notification to its QPP and TPP about this.
    Last edited by UMD; 4 May 2007, 04:48 PM. Reason: To get the fact right. Thanks to Savage25 for the reminder.

  • #2
    That was me posting on TOF around 18 April. I'd lost my 11A seat assignment on SQ325, but got it back. Official reply from SQ below:

    Dear Mr Savage25

    Upon receipt of your email of 19 April, I have asked the respective departments to look into this matter again. Our further investigations show that the seat assignments had become disarray due to a system error when some further changes to the flight were made in April. We have brought this to the attention of our IT vendor and we will seek to resolve this so as to avoid a recurrence of such nature.

    My sincere apologies for the inconveniences caused, Mr Savage25.


    Yours sincerely

    xxxxx xxxxx
    Manager Customer Services

    Comment


    • #3
      Thanks Savage25. I knew I had read it somewhere.

      Comment


      • #4
        Originally posted by UMD View Post
        I know this rarely happens but I think SQ should have a system that can send notification to its QPP and TPP about this.
        ... or given it's all IT driven anyway, notification to all registered KF members would be good as well!

        Comment


        • #5
          Agree with you, jhm.

          Comment


          • #6
            The system also booted me out of 14A on both my SQ326/325 for July, and it happened on April 17th - but i got it back straight away after a few calls. Excuse? - 'puter glitch.

            Comment

            Working...
            X