NEZASA TRAVEL PLATFORM V343
We are happy to announce our latest TripBuilder release. Please see these release notes for the most significant changes. Let us know if you have any questions, feedback, or ideas for features or improvements!
By email: [email protected]
Via support portal: https://support.nezasa.com/
Via BucketList: Available in TripBuilder's Cockpit at the Resource Centre
.GENERAL
Enhanced Security Measures for User Sessions
To strengthen the security of TripBuilder and protect your valuable data, we are updating our session management practices in line with leading security standards, including OWASP best practices. We aim to enhance safety while ensuring minimal disruption to your daily activities.
The new session management settings for TripBuilder will initially set the absolute session timeout and the idle timeout to 12 hours. Over the coming weeks, we will gradually adjust these settings to improve security further:
Absolute Session Timeout: This will be reduced to 8 hours, ensuring users are automatically logged off after a typical workday.
Idle Session Timeout: This will be reduced to 30 minutes of inactivity, reducing the risk associated with unattended screens.
These changes will be implemented progressively, and we will closely monitor feedback and usage patterns throughout the transition.
Find more information here.
.DISCOVERY
Planner Copilot | Extend Input Formats to Image Files
We are happy to share that the Planner Copilot now supports image files as part of user input. This enhancement allows users to interact with the AI using a combination of both text and images, providing a more dynamic and versatile experience. As the saying goes, "a picture is worth a thousand words"!
Find more information here.
Planner Copilot | General Improvements
We have introduced two general improvements to the Planner Copilot to enhance consistency and user experience:
When the feature flag “Hotel suggestions - only suggest hotels from own supply” is enabled, all accommodation suggestions will now adhere to the content rules defined for inventory accommodations.
Better interpretation of general prompts containing just a few keywords, such as “Italy”, “French Revolution”, or “Kite Surf”. The Planner Copilot now considers these keywords in context, taking into account the user interaction flow and traveller preferences, and will suggest an itinerary whenever possible.
.PLANNER
Improved Consistency on Activity Dates
Ensuring data consistency throughout the booking process and in travel documentation is crucial. The latest version of TripBuilder introduces several improvements to activity date management:
An issue with the "Change activity start date" feature in the Planner has been resolved. Previously, certain edge cases involving timezone shifts could lead to incorrect date updates. This problem has now been addressed.
The Planner aligns the display of activity durations with Discovery and Travel Documentation. For activities that include overnight stays, TripBuilder will display either the number of nights (if the "Show Number of Overnights" option is enabled) or total calendar days (if this option is disabled). Single-day activities will continue to show their duration in hours and minutes.
The Planner displays the duration of multi-day activities using calendar days rather than 24-hour periods. This change ensures consistency with Discovery and industry standards. Single-day activities will display their duration in hours and minutes, while multi-day activities will be shown as "X nights" or "Y days," depending on the configuration settings.
.CHECKOUT
Improved Messaging for Partial Booking Confirmation Page
We have enhanced the booking confirmation page to provide clearer communication regarding booking failures. The updated messaging explicitly identifies all components that failed to book, ensuring that agents and online consumers fully know which services require follow-up.
Find more information here.
.COCKPIT
Enforcing Restrictions on Net Price Editing for Inventory Components
To enhance the accuracy and integrity of pricing for inventory components, we have implemented a new restriction on net price editing. For inventory components that include at least one amenity with a non-zero net price, the ability to edit the component's net price is now disabled. This measure is designed to prevent pricing errors and ensure the integrity of the overall component pricing and its constituents.
Find more information here.
Changes to “By Status” Filtering in Customer Care
We have updated the Customer Care interface to enhance the organisation and management of itineraries based on their booking status. These improvements make it easier to handle bookings, especially when components fail to confirm.
"In Progress" Filter: A new "In Progress" state filter has been introduced. This filter displays itineraries with the statuses "Booking in Progress" and "Change in Progress".
"Manual Processing" Filter: The existing "Manual Processing" filter has been refined to only show itineraries with the "Manual Processing" status.
These updates improve the handling of bookings by clearly identifying which itineraries might need a "reset" and which might need a "retry," thereby streamlining the resolution process for unconfirmed components.
Find more information here.
Operating Carrier Display: Name and IATA Code
To ensure consistent and accurate display of carrier information throughout TripBuilder, we have introduced changes for cases where the flight carrier and operating carrier are different:
Travel documents and the Customer Care interface now accurately reflect the operating carrier for flights. Instead of displaying the parent company, we show the name and IATA code of the operating airline when applicable.
For example, if a flight is operated by CityJet, in Customer Care Documentation the transportation will display "CityJet" along with its IATA code "WX," rather than the parent carrier.
System Event Copy Functionality
We have improved the functionality for managing system events, making it easier for admin users to copy event details. With this update, you can now copy the details of a system event with a single click of a button. Previously, this process involved expanding the system detail, manually selecting the text, and using a copy command to transfer the content to the clipboard.
Find more information here.
Extension to Booking History with Product Name
We have enhanced the Booking History feature for each itinerary in Customer Care by adding explicit product naming. This update improves the visibility and usability of product identification when analysing a booking flow:
A new "Product Name" column is now displayed by default in the booking history, making it easier to identify products at a glance.
Customer Care users have the flexibility to toggle the "Product Name" column display, allowing them to customise how they view and manage booking history data.
Find more information here.
Cooperative Column and Filter for Travel Agencies Management
We have introduced new features to enhance the identification and management of travel agencies, particularly those part of larger agency groups or cooperatives. The Travel Agencies list now includes a "Cooperative" column, which displays the name of the cooperative each agency is associated with, or "No Cooperative" if not applicable. Additionally, a dropdown filter allows users to easily filter agencies by their cooperative affiliation.
Find more information here.
Redesigned Booking Failure Notification Email
We have updated our booking failure notification email to better support customer service teams in managing itineraries where one or more components have not been confirmed. This initial redesign focuses on accommodations booked through TravelGateX (TGX), clearly distinguishing between timeouts and actual booking failures. This clarity enables customer service teams to follow up more effectively.
If a service falls under the 'booking status unknown' category, it is important to check the Booking History page in Customer Care for further details and, if necessary, contact the supplier offline for additional information.
.APIs
Extension to Itinerary API with Partner IDs
The Itinerary API now includes a new attribute, creationChannelPartnerId, which is used to identify partner systems that create itineraries in TripBuilder.
Please note that Nezasa must create partner IDs before they can be used with the API.
Find more information here.
Enhancements to the Booking API
We have made two significant improvements to the Booking API and its support resources to enhance functionality and documentation clarity:
Introduction of the "lastbooked" Date:
The API now includes the "lastbooked" date, previously referred to as the "booking date." This change aligns the name with the actual data field, which indicates when the most recent booking or change was made. This field helps you keep track of the latest updates to your bookings.
As a follow-up, the next version of TripBuilder will introduce a new attribute, "firstbooked," which will indicate when the initial booking took place.
Updated API Documentation:
The Booking API documentation is now generated and deployed using the OpenAPI standard (version 3.1.1). The documentation includes all endpoints, request/response structures, authentication mechanisms, and error-handling patterns, ensuring consistency in naming conventions and response structures.
The previous documentation format, which used Google Docs, has been deprecated. Please refer to the new documentation for up-to-date API details and examples.
Find more information here.
.FEATURES FOR UPCOMING RELEASES
Nezasa follows the “Now, Next, Later” framework to outline the development trajectory of TripBuilder, enhancing transparency around our progress. We share these insights with our customers in each new release in the TripBuilder - Now, Next, Later article.