Chatten fungerade utmärkt för mig innan övergången till Skyteam. När jag behövde prata med SAS i förra veckan testade jag chatten. Ärendet blev tilldelat en agent direkt, men sedan hände inget på 4 timmar. Jag arkiverade chatten och ringde in. Fick svar direkt….
Eller så är det just nu ett tekniskt hinder för att använda funktionen, så kommer förhoppningsvis tillbaka inom en snar framtidJag skulle helt slippa ringa just nu.
Synd att man har kvar en funktion som inte går att använda.
Riktigt bra funktion som kom 1 sept och har förbättrats lite sedan dess. Jag fick upp lounge på KLM bokning förra veckan, bra där SAS!
Track checked in luggage
Visa bifogad bild 133609 This was a nice new function in the new app.
Seems that time is in GMT as the depature time of the aircraft was 10:50.
I will check when I go back to Umeå tomorrow if it will be updatet when changing flight on ARN as I have a short connection.
Visa bifogad bild 133608
/ TT
Today I had a very short connection on ARN as my flight from GOT was 20 min late.
As the expected text "Loaded on SK2030" was replaced by "Baggage has been screened" I suspected that it was still on ARN - which was correct as my bag did not show up in UME
But thanks to the new app I already knew....
Visa bifogad bild 134107
Perhaps has been reported before(?):
Checked In Luggage status in the app, while a great idea, isn't reliable.
I'm aware of the disclaimer, and probably the app just gets the wrong info from the airport system. I'm not sure how often info is wrong, but if it is often wrong, one could question why implement the feature at all? =)
Example: sitting waiting at BER for flight to ARN. Status in app is "Loaded on SK2678". However, the machine flying SK2678 today hasn't even landed at BER yet, so it would be a feat to have my luggage loaded already!
That said, Checked In Luggage status seems to have been working accurately at ARN and OSL, based on my experience.
Maybe this is a one off error at BER and then alright, no big problem. However, it would perhaps be worth looking into data from different airport to try to determine whether it's accurate or not. If often incorrect/unrealistic, then those airports could be disabled from this functionality in the app?