Topic

This article describes how Everbridge Travel Protector™ (Travel Risk Management) determines whether a trip is classified as domestic or international. It explains how the system uses Passenger Name Record (PNR) / itinerary payload data, why some itineraries may appear as domestic even when the traveler is going abroad, and what to consider in terms of itinerary and segment capture.

Description

The domestic versus international designation in Everbridge Travel Protector is determined from the contents of the PNR, also referred to as the itinerary payload. The system evaluates the travel segments that are present in the PNR payload that is supplied to the Travel Risk Management system.

When a PNR payload contains only travel segments within the same country, the trip is marked as domestic. When a PNR includes an international leg, the trip is marked as international.

The designation does not use the traveler’s static home address. A PNR that lists only domestic segments will result in a domestic classification even if the traveler’s home address is in another country. Because the designation is derived from the PNR payload, the system will classify the trip according to the segments that are actually present in that payload.

If the international leg is not included in the PNR that is submitted to the Travel Risk Management system, the trip will not be recognized and marked as international. To have the itinerary recognized as international, the PNR submitted must contain the full itinerary, including the international leg or legs.

Everbridge can capture various travel segments as part of itinerary handling. This includes Global Distribution System (GDS)-booked travel segments, such as standard car hire bookings, as well as manually uploaded rail segments, including domestic rail bookings. These segments become part of the travel data that is evaluated for classification.

Travel itineraries can be added into the system through multiple methods, including manually, via out-of-the-box connectors, through API integration, via Travel Protector, or using Outlook 365 integration. These methods provide different ways for organizations to ensure that PNR payloads and segments are delivered into the Travel Risk Management system.

Some specialized segments, such as certain limousine bookings, may have limitations in data capture. These limitations depend on the booking format and the information that is available for those segments. When such limitations exist, they may affect which segments are included in the PNR payload and therefore which segments are available for domestic or international classification.

The described behavior for domestic versus international designation is documented in the Everbridge Suite (EBS): Travel Protector User Guide.