Overview
Nezasa's TripBuilder provides users with pre-set texts in a range of languages. Customising these labels and texts is generally available only for selected use cases where TripBuilder offers configuration options.
Know more: Please refer to the article Supported TripBuilder Languages for a comprehensive list of all the languages supported in Discovery, Planner, Checkout and Cockpit. |
Configuration Options
- Labels for primary buttons of the main steps in the booking funnel (Discovery, Planner, Checkout) can be mostly configured
- Texts related to terms during the checkout process can be customised by users
- The footer of emails sent by TripBuilder can be configured
FAQ
Q: Can I suggest improvements in specific texts?
A: Absolutely, your feedback is welcome. Subject to the request being general and aligned overall with TripBuilder, we might adapt the product accordingly.
Q: Can "ß" in German texts be replaced by "ss"?
A: Unfortunately, this is unsupported. Nezasa relies on official spellings from https://www.duden.de/ for German.
1. Navigate to Settings
2. Click on Distribution Channels
3. Select your TripBuilder ID
4. Click on the General tab
5. Scroll down to the Footer section
- Short Name (defined at the Distribution Channel level, or default to the tour operator's short name if left blank)
- Legal Name (defined at the Distribution Channel level, or default to the tour operator's legal name if left blank)
- Current Year (especially useful for copyright statements)
Please note: If no value is defined, the statement Copyright ${CURRENT_YEAR} ${LEGAL_NAME}. All rights reserved will be taken as default. This results, as an example Copyright 2024 Nezasa AG. All rights reserved
|
7. Translate the chosen statement into the supported UI languages
8. Click Save on the top right of the screen when done
Please note: Since the configuration is performed at the distribution channel level, each channel may have individual statements. If you want to display the same message across all distribution channels, you'll need to configure it separately for each one. |
Comments
0 comments
Article is closed for comments.