Crisis visibility for active trips.
Know before they do.
Alert gives your brand real-time visibility and a coordinated response, so travelers keep moving, even when the trip doesn't go to plan.
- Dashboard
- Trips
- Tickets
- Alerts
Your travelers
Updated 10:41
- Tokyo3 travelersClear
- Lisbon2 travelersClear
- Cape Town4 travelersWeather watch
- Mexico City2 travelersClear
3 travelers arriving in Tokyo within 48h
Itineraries matched against live events
Most agencies find out from the traveler.
By the time a traveler calls to say they're affected, the window to help proactively has already closed. Duty of Care shouldn't depend on who happens to call first.
Illustrative scenario
See the threat. Check on your travelers. Keep the trip moving.
Alert turns a global event into traveler-specific action: detect risk, check safety, coordinate the fix, and get the trip back on track.
Alert runs on the OnSpot Duty of Care Framework, a structured process aligned with ISO 31030, the international standard for travel risk management: Detect → Assess → Verify → Reach → Respond → Coordinate → Resolve. Here's what that looks like in practice.
1. Detect
An earthquake near Tokyo is detected and checked against known events, opening a new threat record automatically.
TokyoYokohamaChibaTokyo BaySagami BayEarthquake · 10:42New threat record
Earthquake near Tokyo
- Source
- Seismic network
- Known events
- Checked
2. Assess
Alert cross-references the event against your itineraries, surfacing 6 potentially affected travelers: 3 currently in Tokyo, 3 arriving within 48 hours.
TokyoYokohamaChibaTokyo BaySagami BayEarthquake · 10:42Impact · your travelers
6 potentially affected
- In Tokyo now
- 3
- Arriving within 48h
- 3
Your agency's trips only
3. Verify
OnSpot verifies the event is real and relevant, and recommends a safety check for the 3 travelers currently in the area.
TokyoYokohamaChibaTokyo BaySagami BayEarthquake · 10:42Event confirmed. Safety check recommended for 3 travelers.
Verified by OnSpot · 10:44
Safety check · 3 travelers in the areaRecommended
4. Reach
A safety check goes out automatically, in each traveler's preferred language and through their preferred channel: WhatsApp, TripFlow, SMS, or a call.
Safety check · sent 10:46
WhatsAppFrançais
Un séisme a été signalé près de Tokyo. Êtes-vous en sécurité ?
Je vais bienJ'ai besoin d'aide
TripFlowEnglish
An earthquake was reported near Tokyo. Are you safe?
I'm safeI need help
SMSEspañol
Se ha registrado un terremoto cerca de Tokio. ¿Está a salvo?
Estoy bienNecesito ayuda
A call, for travelers who prefer one
5. Respond
Responses update in real time: within minutes, 2 travelers check in safe and 1 reports needing help.
TokyoYokohamaChibaTokyo BaySagami BayEarthquake · 10:42Safety check · live
- Safe
- 2
- Needs help
- 1
- C. M.WhatsAppSafe
- A. R.TripFlowSafe
- J. L.SMSNeeds help
6. Coordinate
The traveler who needs help reports an evacuated hotel; Alert opens a case and assigns it to a Spotter, who starts coordinating an alternative.
Case · Hotel evacuated
In progressSpotter assigned
Our hotel has been evacuated. Where do we go tonight?
You're safe with us. I'm arranging a room nearby now.
Case opened from Alert · agency notified
Alternative
Hotel near UenoCheckingHotel in GinzaRoom on hold7. Resolve
An alternative room is confirmed within the hour. Your agency sees one dashboard with all 6 travelers' status and a full timeline of the response, from detection to resolution, in one place.
Earthquake near Tokyo
ResolvedYour travelers · 6
- C. M.TokyoSafe
- A. R.TokyoSafe
- J. L.TokyoRoom confirmed
- K. S.Arriving · 48hMonitoring
- M. D.Arriving · 48hMonitoring
- E. B.Arriving · 48hMonitoring
Response timeline
- Event detected
- 6 travelers matched
- Event verified
- Safety check sent
- 2 safe · 1 needs help
- Case opened · Spotter assigned
- Alternative room confirmed
The earthquake didn't end the trip. It just needed someone watching.
Know who needs help now.
Alert isn't just about knowing something happened. It's about making sure the trip keeps going anyway.
Alert identifies affected travelers regardless of where each part of their trip was booked. One DMC's booking or ten, the visibility is the same.
24/7 event monitoring tied to where travelers actually are
Proactive outreach when an event occurs, in the traveler's language and preferred channel
A temporary, incident-specific Crisis Hub via OnSpot Connect, coordinating resolution in real time
A single dashboard view for your agency: your travelers, your timeline
Built on a real standard, not a promise.
GDPR compliant: traveler data handled under GDPR standards throughout.
Aligned with ISO 31030: the international standard for travel risk management, applied through our own OnSpot Duty of Care Framework.
Transparent by design: every action taken is visible in Connect: what happened, who acted, how fast.
The trend this page exists to answer.
Global natural-catastrophe losses reached $320 billion in 2024, above both the 10-year and 30-year inflation-adjusted averages.
Source: Munich Re, January 2025.
Weather-related disasters are five times more frequent, and seven times costlier, than in the 1970s.
Source: World Meteorological Organization.
Questions
What kind of events does Alert monitor?
Weather events, natural disasters, transport disruption, and security or health incidents relevant to where your travelers actually are, matched against real itineraries, not a generic global feed.
Does Alert track my travelers constantly?
No. Alert matches known itineraries against relevant events and reaches out when there's a real reason to. It isn't continuous location tracking.
How does Alert know where travelers are?
From the itinerary shared when a trip is created in OnSpot Connect, plus what a traveler confirms when they respond to a safety check.
What happens if a traveler doesn't respond to a safety check?
It's flagged for direct follow-up rather than left open. A non-response doesn't get treated as "safe" by default.
How is traveler data protected?
Alert operates under GDPR, with every action documented and visible to your agency in Connect.
How is this different from relying on a DMC?
A DMC sees its own booking. Alert sees the whole trip, regardless of how many suppliers or DMCs are actually involved.
How is this different from a generic threat-intelligence feed?
A feed tells you an event happened. Alert tells you which of your travelers it affects, checks on them directly, and can open a resolution case. A feed alone can't do any of that.
Does this replace our internal Duty of Care process?
No, it strengthens it, with a structured methodology, proactive monitoring, and documented response most internal processes don't have on their own.
Does Alert replace Assist?
No. Alert finds and reaches the travelers an event affects. A traveler who needs help then becomes an Assist case, handled by a Spotter.
Which plans include Alert?
Alert is included in every bundle, with general event notifications on Plus and matched, proactive alerts on Premium and Elite. It can also be added to a standalone Assist.
Will OnSpot contact my travelers without my approval?
Not unless you authorize it. Reaching affected travelers quickly is the point of Alert, so we agree with you in advance when travelers should be contacted.
Built on OnSpot Connect; traveler location and status data flow from TripFlow. The Crisis Hub is Connect's incident-specific mode.
See how Alert uses Crisis Hubs