For me, this is good news!I've yet to receive DSC for any of my flights even from early April and they were normal bookings.
For me, this is good news!I've yet to receive DSC for any of my flights even from early April and they were normal bookings.
As a side bar to original post dylarr, I have traveled MEL-SYD-LAX (QF) then LAX-MIA-SJO (AA) last week and both Miles and SC's (non DSC) showed up within 24hrs after each flight all correct and accounted for.I've yet to receive DSC for any of my flights even from early April and they were normal bookings.
Some of the flights in my trip were codeshare & OW partners. I had a delay too, but all SC's accounted for within a week of travel.flights even from early April and they were normal bookings.
Genuine question. Are the allotment of points and DSCs, and promo points etc done in the Amadeus platform? Maybe @madrooster can answer?What VA can or can't do is kind of irrelevant - they are built on a totally different platform. IMO a better comparision would be to a carrier that also uses Amadeus and how they deal with such promos.
I'd also note QF is not the only one who processes these things in batches that show up later. IHG hotels just finished a 2x promo and those did not show up for a few days or up to a week after stays credited.
No - it’s done in Oracle Siebel Loyalty, the platform used by Qantas to run the QFF program.Genuine question. Are the allotment of points and DSCs, and promo points etc done in the Amadeus platform?
Genuine question. Are the allotment of points and DSCs, and promo points etc done in the Amadeus platform? Maybe @madrooster can answer?
No - it’s done in Oracle Siebel Loyalty, the platform used by Qantas to run the QFF program.
I doubt that there is real time data sharing between Amadeus and Seibel. It no doubt relies on an ETL function, hence the constant talk about batching with QF systems.Thanks. Follow on question please. Do you know if there is anything inherent in Siebel that would account for delays in posting promo points & DSCs?
Seems to me that if the promo is attached to the PNR, and Siebel ‘knows’ the flight has been taken and posts the normal points etc, it should ’know’ the promo additions too? Or - pardon my cynicism, born of long experience with QF, - could there be a delay programmed in .
Could be wrong, but I'm pretty sure it's Salesforce with a side of iFly.Correct it's done in Siebel
Seems to me that if the promo is attached to the PNR, and Siebel ‘knows’ the flight has been taken and posts the normal points etc, it should ’know’ the promo additions too? Or - pardon my cynicism, born of long experience with QF, - could there be a delay programmed in .
well , I reckon the software used is relevant. If it doesn’t have the capacity to do promo stuff then that’s different from it having the capacity but the airline not using it. I don’t know how much capacity an airline would have in re coding or requesting a coded ‘special’ to the functionality of third party software.Let's be real here: the software used is irrelevant as QF can spend the cash to ensure they get desired results for customers from their vendors...but they don't.
well , I reckon the software used is relevant. If it doesn’t have the capacity to do promo stuff then that’s different from it having the capacity but the airline not using it. I don’t know how much capacity an airline would have in re coding or requesting a coded ‘special’ to the functionality of third party software.
As to batching, one wonders why it’s done that way, again, if Siebel already ‘knows’ the entitlement of pax via the PNR.
Fair point, but most hotels are owned and operated by third parties and just use the IHG etc brand. So a bit of a lag is understandable. Accor is an absolute shocker.
Qantas, on the other hand is a premium carrier () and it’s system immediately knows if a flight has been taken on its own metal, as the ( usual) instant posting of regular points shows.
No excuses, except for under investment in its IT, which we all have suffered from.
You could ask the same question about ticketing? Why do some have to wait weeks for re-issue? Something to do with batch processing?Without obsessing about this I wonder why it's done in batches (choice vs functionality) and why the timing between batches tends to change ( at least subsequent to the timing of the first batch).
No, I don't really care, just pricking my Qantas voodoo doll.
I am not sure whether the DSC promo’s T&C’s were updated or whether it was always there. It now says that the DSCs should arrive “from 8 weeks after travel”. Whatever “from” means in that contextI flew on the first day of the flying window and again a few days or so later and haven’t yet got the DSC. The first batch always takes a while. Once the first batch is processed, subsequent trips should be much faster.
AFF Supporters can remove this and all advertisements