This article is auto-synced from its in-app version in Tai.
Preview. This agent is in preview — available to companies in the preview program, and still evolving.
A built-in agent that finds which of your customers are in a destination when an incident happens, and pulls their contact details so you can reach them.
When you'd use this
Use the Traveller Locator when something happens somewhere your customers are travelling — an earthquake, flooding, a strike, a security alert — and the first question is "who do we have there?". Name the destination and the date; the agent returns your confirmed bookings with travellers in that location, sorted by who leaves soonest. Ask for detail and it drills into each booking for passenger names, contact email and mobile, the hotel they're in right now, and their flights.
What it can do
The agent works in two passes, so you get a usable answer before the slow part finishes:
Fast destination sweep. A single search over your booked trips returns every confirmed booking with a traveller in the destination on the date you gave — one row per booking, no duplicates, drafts and cancelled itineraries excluded. This pass is quick and stays quick no matter how many bookings match.
Contact detail drill-down. On request, the agent looks up each of those bookings individually and returns lead passenger, co-travellers, contact details, current hotel, and first and last flight with PNR. Bookings are checked in parallel, and the agent tells you how many it covered — if a long list runs out of room, it lists what it missed and you reply
continue.Priority flags. A flags table calls out the bookings that need attention first: no contact information on file, minors travelling without a contact, a gap in accommodation, or a placeholder with no service actually booked.
Every result links straight into the Cockpit customer-care view so you can act on a booking without searching for it again.
Ask for the list as a file and the agent produces one: an Excel or Word download, or a printable HTML report you can share with whoever is running the response.
Steps
In the Workbench sidebar, click Chats.
Select Traveller Locator from the agent picker.
Describe the incident with a destination and, if it isn't today, a date — for example "Flooding in Bangkok today. Show me everyone in destination."
Review the booking list, then reply with a city to narrow it, or
detailto get full contact details for the whole list.
Tips and limits
The agent is read-only — it finds and reports, it never changes a booking.
Only confirmed bookings are included. Drafts, planning itineraries, and cancelled trips are deliberately left out, so the list is who is actually travelling.
The destination sweep runs on booking data that is refreshed roughly daily, so a change made in the last few hours may not be reflected yet. The agent says so in every answer. Contact details in the second pass are read live.
Start narrow when you can. A whole-country search on a busy destination can return hundreds of bookings; a city name, a tighter date, or an agency filter makes the detail pass much faster.
If a search returns more than about 50 bookings, expect the detail pass to take several minutes. The agent reports its coverage and lets you continue where it stopped.
The underlying data access is part of the TripBuilder integration, which is currently Nezasa-managed — Nezasa provisions and operates the connections the agent relies on.
Related