Lrtalk

Used two of my RUC's for DG wife and PM me for SJU to ATL and ATL to LIT yesterday. Both legs of both reservations notated Systemwide Upgrade when the certs were applied. At check in time it allowed wife to check in and told me check in not allowed and to check in at airport. At airport we immediately go 1 and 2 on UG list to ATL. But I go 1 on ATL to LIT while she is 5. He checked the people between us, and all were regular UG's that the RUC should trump. Agent called Atlanta twice trying to fix without success. I call PM line while on plane before leaving SJU, and she says only gate agent in ATL can do anything once checked in. Irony is that the only way to know there is a problem is to guess what.....check in. Too close on connection to talk to GA in ATL, so we just punted and took the one UG seat and called it a day. Bottom line appears to be that these things are a wild card.

Readynow

I won't choose these again next year. Too hard to use and you are never sure it's done right. The last think I want to do at airports is to try and instruct front line employees on how to do there job or point out that I think they made a mistake.

DeltaWings

Had a similar issue recently and DL reopened the RUC for me. PM on a L fare that appeared as #12 on the list and a GA that refused to look at it. I had to push back after they said no, but it was ultimately reopened. Persistence is key.

In your case, you'd only get one returned, but that's still valuable.

FlyAO2

Sadly this is viewed as a "Partial Fail." This should be viewed as a "a complete fail."

Why DL continues to not be able to apply these things correctly is unreal. Completely shameful.

I've had quite a bit of success having the Twitter people verify the correct application of the SWU (I assume RUCs would work the same way).