NEZASA TRAVEL PLATFORM V346
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
.COCKPIT
Increased Character Limit for Transfer Details
The character allowance for the "From" and "To" fields within our Transfer inventory products has now been expanded to accommodate up to 150 characters. This enhancement is particularly beneficial when translating into more expansive languages such as German, Finnish, and Dutch.
Cockpit Copilot | General Improvements
Aligned with previous improvements applied to the Planner Copilot, the Cockpit Copilot has been enhanced with three new features:
The Copilot is now available in all languages supported by the Cockpit UI itself. Already before, the AI was able to respond to your questions in the language you asked.
Copilot users can now use their voice as input, which is especially useful for longer texts. Released as a public beta, this feature processes voice audio using your browser's default speech recognition service:
Chrome/Edge use Google's speech recognition service.
Safari uses Apple's speech recognition service.
Firefox employs a different service depending on the user's locale.
Please note that if speech recognition is disabled in your browser settings, the microphone icon will not appear in the Copilot interface.
The Copilot provides clickable prompt suggestions to assist users in initiating their interactions. This feature is especially beneficial for those who are new to using the AI tool, providing an easy way to get started.
Find more information here.
New Itinerary Retention Data Policy
We are introducing a new retention policy for itineraries in the "In Planning" state to streamline the management of travel plans. The key changes are as follows:
The maximum retention period for itineraries is now set at 90 days.
The default retention period for a new itinerary is 30 days.
This update represents a significant change from the previous settings, where itineraries could be retained for up to 180 or even 360 days. The transition to the new policy is seamless:
Itineraries previously set to retain beyond 90 days have been automatically adjusted to the new maximum of 90 days.
All new instances of TripBuilder will default to a 30-day retention period.
Moreover, the ability to configure these settings has been extended to all administrator users, expanding the feature control beyond just Nezasa users.
Find more information here.
Retry Cancellations on Booking Changes
We have enhanced the handling of booking changes to prevent inconsistencies. Previously, retrying was only possible for components that failed to book. Now, if one or more components fail to cancel during a booking change, the booking will enter a "Booking Change Initiated" status, allowing users to retry the cancellation. The retry will only target components that failed to cancel or were removed since the previous attempt.
A warning message will be displayed in Customer Care under the following circumstances:
One or more new components were booked during the booking change (and were not cancelled again during the same booking change). If you discard the booking change, you must cancel these components manually if they were booked in an external system.
One or more components from the original itinerary were cancelled during the booking change. If you discard the booking change, the original itinerary will contain components that, in Customer Care, will appear to be booked but are actually cancelled.
Additionally, the "Discard Booking Change" confirmation modal will also show the relevant warnings above when the conditions are met. The "Discard Booking Change" action remains available in the "Booking Change Initiated" status.
Feature availability: the new feature is managed by a configuration flag that needs to be enabled by Nezasa. Please get in touch with the Nezasa Support team.
.APIs
Link Extension for Individual Component Vouchers
The Booking API has been enhanced to provide more convenient access to individual component vouchers. In addition to the existing consolidated voucher URL, each component in the API response will now include a new attribute: componentVoucherUrl.
Each new URL provides a direct link to the voucher specifically for that component, if existing. This allows API users to easily access and view individual vouchers without needing to navigate through a consolidated voucher document.
Find more information here.
.INTEGRATIONS
Correction on Optional Service Charges Propagation to Midoco
We fixed an issue where Optional Service Charges were not sent to Midoco when the "Send Optional Service Charge" feature was enabled and an Optional Service Charge was added during a booking change. Now, information about Optional Service Charges is correctly propagated to Midoco.
Find more information here.
.ANALYTICS
TripBuilder Analytics | Timing of API calls
TripBuilder now (since April 16, 2025) stores the request/response timing of API calls to our suppliers in a way that allows for visualisation in TripBuilder Analytics. Browse to the “Supply Connections” dashboard of Advanced Analytics to find how long external suppliers typically need to respond to TripBuilder requests.
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.