Intent shifts inside one search session.
A traveller compares dates, swaps airports and abandons a fare in the space of a few minutes. Signals keeps the attributes your search, booking and service surfaces read current while that session is still open.
- Entities
- traveller · session · route · booking
- Read from
- search · booking flow · contact centre
- Runs in
- your cloud · AWS · GCP · Azure
- Served in
- 6ms p50 in-region
Three problems a nightly table cannot solve.
Results that ignore the last five queries
Dates flexed twice and the airport swapped once, and the ranker still treats it as the first search.
Fare nudges sent to everyone
Urgency messaging read from the cohort, not from this session, so it fires on people who were booking anyway.
Agents who cannot see the abandoned booking
The traveller describes the fare they lost; the console shows last year's trips.
Four surfaces, one set of definitions.
No replatform. One SDK call.
Signals sits beside the booking platform, the search and pricing systems and the warehouse you already run. It adds the live attributes none of them keep current.
Start with one attribute.
Define it, read it in your own product, and see it change while you click around. 14 days, no card, no sales call.