This article is auto-synced from its in-app version in Tai.
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 — a country, a city, or a place with a radius — and the date; the agent returns your booked and requested trips with travellers there, 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 finds every booked or requested trip with travellers in or near the destination on the date you gave — one row per booking, no duplicates, drafts and cancelled itineraries excluded (a trip whose cancellation is still in progress is shown and flagged). This pass is quick and stays quick no matter how many bookings match. It sorts them into three groups:
In the area — they sleep there that night, or travel into, out of or through it that day.
Visits the area during the day — a multi-day tour passes through, or a day excursion goes there, while the travellers sleep somewhere else. Day excursions are matched by city or country, so a radius search doesn't include them.
Possibly in the area — the itinerary doesn't say where they sleep that night, but the nights before or after are in the area — or the trip only places that night somewhere in a wide region that reaches into the area.
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: a booking cancelled or withdrawn since the sweep's data was refreshed, 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.
Booked and requested trips are included, along with day excursions that aren't confirmed yet, so nobody who might be there is missed. Drafts, planning itineraries, and cancelled trips are left out; trips whose cancellation is still in progress are shown and flagged.
The destination sweep runs on booking data that is refreshed twice a day, so a change made in the last few hours may not be reflected yet. The agent says so in every answer. The second pass reads each booking live, including its current status and contact details.
Start narrow when you can. A whole-country search on a busy destination can return hundreds of bookings; a city, a place with a radius, or an agency filter makes the detail pass much faster.
For a city or a place, the agent searches around its centre point and shows the coordinates it used, so you can correct them if it picked the wrong place.
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