Bing introduced Autosuggest Flight Prices, which predicts the lowest fare over the next 90 days and whether that ticket price will rise or fall.
Here's how the service purports to work:
The user enters "Denver flights" into the Bing search box and Bing detects your origin airport and the lowest fare, all displayed under your query.
It looks like this:
In this New York to Denver example, Bing predicted a $279 fare March 15 to March 22 and that the fare would rise.
When you click on the link, you navigate to Bing Travel, where you have to run another search. Instead of the March 15 to March 22 dates, Bing has prepopulated the fields with March 25 to March 27 departure and return dates.
After running that search, the predicted $279 fare was nowhere to be found. Instead the fares on the first page of results ranged from $367 to $394.
And, when I ran another search using the original dates, March 15 to March 22 that the Autosuggest feature defaulted to, the New York to Denver fares ranged $298 to $322 on the first page of results.
Again, that predicted $279 fare had gone missing.
On the other hand, when inputting "San Francisco flights," Bing answered by predicting a low fare of $298 from March 15 to March 22, and I actually found a $279 fare when running Bing Travel through its paces.
Bing revealed the release of Autosuggest Flight Prices in its Bing Community search blog, saying "Don’t worry about entering the formal city name or airport name. Bing Travel recognizes colloquial names like Chi Town."
However, when I entered "Chi Town flights" there was no fare prediction at all under the search box, and instead the navigation took me to Bing Travel for New York to Cape Town, South Africa, flights.
Hey, it's a small world.
And, maybe Bing has some tweaking to do with autosuggest.