What really would be most efficient for a manual power search would be providing an input file (excel, csv, text, whatever) that would contain a list of search objects (e.g. Method, date, class, origin, destination, etc). This could then kickout a summary or file of results.

Having this done hourly and changes emailed would be the ideal automated solution, but an easy button for the manual search would be a very welcome improvement.

For example right now I have multiple sessions open because I have combinations of segments and dates for a desired destination and return. The new power search appears to take care of the date variable (once all results are returned instead of first) but doesn't help with multiple segments. Multiple segments are important because there are multiple paths between cities, and kvs finds them if all segments are available. But availability and route rules (maximum permitted miles) aren't always enforced. For instance if I want to go from ORD to LIM, I search all the gateway flights to LIM on OW (MiA DFW JFK LAX etc). That is because with EXP, there is additional saver availability not visible and agents can do a request to revenue management, which often works for the puddle jumper flights if the intensional segment is available. So this requires me to make dozens of combinations of international segments and dates to be able to piece together itineraries I can be successfully booking on the phone. Ideally a command line program call with the input file as an argument, but working with the GUI is fine as well. I would find this functionality very valuable. It is there today but terribly manual and cluttering having that many instances open.