From a sentence to a search
On the results page, a chat sits next to the filters. On a phone it is a panel at the bottom of the screen that the reader can minimise. The reader writes what they are after. The assistant checks what is available, sets the filters, says what it changed, and the trips on the page update.
Then the reader keeps going: cheaper, a week later, closer to the lift. Every change is shown as a small label that can be removed, and any earlier point in the conversation can be restored. Earlier chats are listed under previous chats, so a reader can pick one up again on a later visit. They are kept in the reader's own browser.
On a hero you can let the AI prompt come first. The reader types the request there and carries on in the chat on your results page, with a switch back to the classic search bar at any time.
- Answers in the language the reader writes in
- The chat and the filters work on the same search, so the reader can switch between them
- Changes shown as labels, each one easy to remove
- Step back to any earlier point in the conversation
It changes the search, not the trips
The assistant never builds a list of its own. It sets the same filters a reader could set by hand, and the widget shows its normal trip cards. That is why nothing else about the widget changes: the same prices, the same link to the travel agency and the same tracking of clicks and bookings.
It also keeps to your set-up. The widget's niche, the travel agencies you have chosen and the filters you show are limits it cannot step over. A question about a different kind of trip is turned down instead of answered from another niche.
Like any AI, it can misread a request. When it does, the reader can remove a label, step back or use the filters, which are always available.
Learn what your readers want
AI search has its own part of your dashboard. It shows how many readers used the AI mode and opened the chat, how many AI searches were run, how many questions were turned down because they fell outside your niche, and how many readers chose the classic search bar instead.
A funnel puts readers who used the chat next to readers who only used filters, from search to click to booking, including the bookings the assistant took part in. That shows whether the chat earns its place on your page.
You can also read the conversations your own readers have had, newest first. Narrow them down to questions that were turned down, that failed, that found no trips, that led to a click on a travel agency or that led nowhere. Read together, they show what your audience asks for that your widget cannot answer yet. Contact details are removed from what is stored, and you see your own readers' conversations only.