TRIPS Itinerary Automation: Travel Associates

TRIPS Itinerary Automation: Travel Associates

Notes
This article applies to:                                                        
  1. Travel Associates Australia
  2. Travel Associates New Zealand
Info
With the launch of Trips Automation, HELiO will automatically push all fully paid or cancelled bookings and updates to Trips, ensuring that every customer has an up-to-date itinerary and access to their trip in the Travel Associates app at least 2 weeks before their scheduled departure.

What do I need to know?

Automation into Trips for Travel Associates Australia

  1. Every FULLY PAID HELiO booking will be automatically sent to TRIPS within an hour after the booking is in FULLY PAID status.
  2. When in FULLY PAID status, any change to the booking in HELiO will trigger a sync with TRIPS approximately 1 hour after the change, ensuring your customer's itinerary is always up to date.
  3. Once pushed to Trips, the itinerary will be available to the customer via the Travel Associates App and My Account

Automation into Trips for Travel Associates New Zealand

  1. Every FULLY PAID HELiO booking will be automatically pushed to Trips 14 days before departure.
  2. If full payment is made within 14 days of travel, it will automatically be pushed through to Trips.
  3. When in FULLY PAID status and within 14 days of travel, any change to the booking in HELiO will trigger a sync with TRIPS approximately 1 hour after the change, ensuring your customer's itinerary is always up to date.
  4. Once pushed to Trips, the itinerary will be available to the customer via the Travel Associates App and My Account.
Alert
Trips created or updated via automation won't trigger a customer email notification. To provide your customer with an email and link to view their web itinerary, send an email via the Preview & Publish modal in HELiO (which will trigger an update to the Trips itinerary), or by republishing the trip with notification in Trip Publisher.

Automatic Updates Pre-Departure

  1. HELiO must be kept up to date as the source of truth with any changes, especially to flight itineraries.
  2. When in FULLY PAID status (and within 14 days of travel for TA-NZ), any change to the booking in HELiO will trigger a sync with TRIPS approximately 1 hour after the change, ensuring your customer's itinerary is always up to date.
  3. Trips will automatically sync with HELiO to ensure that the digital Trips itinerary reflects what is in HELiO for the customer. This will occur 72 and 24 hours before the departure date.
    1. If the HELiO booking contains a valid PNR from either Sabre or Amadeus, Trips will also ensure that what is in the GDS is reflected in the customer itinerary (i.e., details like e-ticket, special requests, etc. are reflected in Trips).
      1. Please note that Trips can identify PNRs added to HELiO via Search & Book, Grab PNR, and manual MBI IF the entered Source=Sabre or Source=Amadeus and the PNR is valid.
  4. HELiO will overwrite some content in Trips; continue reading for more details.

Customer Access

  1. Customers can access their bookings online through the Travel Associates mobile app and My Account, as well as through the web itinerary link sent in HELiO or Trips emails.

Important Notes

Alert
As HELiO is the source of truth, if you change a HELiO-created component in Trips, these changes will be overwritten with any sync. This includes manually pushing from HELiO to Trips and any automated syncs.

Components created in Trips will not be overwritten, and this includes:
  1. Cover Photos and other images
  2. The Hotel Content Note (with images & full description of the hotel)
  3. Segments that were added manually in Trip Publisher (e.g., not created from the HELiO integration)
  4. Documents uploaded via Trip Publisher
Warning
Booking segments in Trips created from HELiO should not be edited. Any edits made to a segment (excluding accommodation content notes) will be overwritten with the automation syncs.


Some examples of content that WILL be overwritten if edited in TRIPS:
  1. changes to passenger details of a flight segment
  2. changes to dates
  3. edits or additions to content in the DETAILS section of a segment
There are a couple of exceptions to this rule. If these fields are manually updated in Trips, they will not be overwritten:
  1. segment fields that are not present in HELiO, such as the pick-up/drop-off time for transportation, or start/end time for an activity
  2. matching a segment to a vendor profile (i.e., photos and address will remain linked)