Probably trying to save on API calls and while also saving a user click -> going straight to change [flight seat cancel]). Theoretically efficient for network and user.

Would be difficult to know how many people used just the default view reservation option, disconnects, distractions etc could add a higher threshold of false positives. The clicks to the change options would be more accurately measurable - this could also be a way to test (maybe inadvertently) how many people just use the reservation view for its own sake, or prefer it**

** just keep hitting 'view reservation' on your different tickets to load their event logs with that data... /joking, kinda