I've been fascinated by the website glitches re: FareLock mentioned in this thread. It has helped to know a lot ahead of when I plan to purchase the newly FareLocked trip for one way, SFO to MXP connecting in ORD, and the majority is in PP class. I'm booking about 200-225 days out and can't believe I can go on a Saturday, lower if it was mid-week, for only 90,700 miles. My CC statement closes on Monday so I'll see more miles applied plus I'm purchasing sale miles+bonus. I've been cautious about miles speculation with choosing a 14-day FareLock. The only way that I could purchase the FareLock was with a call to customer service. I connected to Shirlynn, or at least that's what her name sounded like. My theory is you're connected faster to a CSR if you opt-in on the survey, which I did. She helped me lock it for 90,700 miles. She said that she added my FF number. I logged in using the chrome web browser and noticed that the trip didn't have my FF number. I added it and I selected seats at the same time because the UA phone app wouldn't let me select seats without a response of "Try again later". It shouldn't be this much work.

In the end, I gave the CSR a "5" rating for all of the questions because in the middle of my call, my home experienced a power outage and she was so understanding. I panicked because I couldn't hear her on the phone but she was still there so it was just a coincidence that she went silent at the same time as the lights went out... It happened at 7:30 AM without having had coffee.

In summary, I haven't seen any carrier's website function without inconsistencies or errors so badly occurring so much as it has become so apparent lately. I'll spare you all the differences I see on other sites for other carriers. IMHO, the development of the carrier's phone apps complicates the functionality of the web browser version, and vice versa.