Overview
Tripbuilder's Musement Connector enables access to Musement activity supplier that offers a wide variety of tours and attractions worldwide by contracting end tours to local suppliers. The present article describes the two supported UIs for search and book flow and considers each.
UI & UX Flow
TripBuilder enables two different UIs to interact with Musement offers:
PAX binding UI: Follows the standard search and book flow from TripBuilder for activities that, according to the age of each PAX, determine which service category of activity applies and fit accordingly.
Ticket binding UI: New approach where no binding is conducted between the PAX ages and the service categories of an activity representing a ticket. The user must specify the quantity of each ticket type intended to acquire.
Important: Due to data formatting on the metadata provided by Musement and used for matching activity service categories to PAX, the interface "PAX binding UI" is not recommended, as it might result in wrong ticket matching of PAX.
Please note: The feature flag for controlling which UI to present must be enabled in Settings. Currently, the feature flag needs to be enabled by the Nezasa support, please create a ticket with your request.
PAX binding
Musement's previous UI allocated all PAX to the selected service category.
During the booking process, an additional "Activity Questions" section is shown to collect any supplementary information required for the activity providers.
Non-PAX Binding
Musement's new UI allows selecting specific and multiple service categories or ticket types. To do so:
Select the most suitable ticket option
Depending on the activity chosen, a time slot may need to be selected
Add the desired Service Categories
Click Select
Similarly to the old UI, a section for "Additional Questions" is shown during the checkout process.
Note: The questions that appear in this step are defined by Musement and the local Suppliers.
Answering these queries is mandatory for a successful booking. Incorrect or missing responses may lead to issues when carrying out the activity with the local supplier.
TripBuilder has no control over the questions being presented. Further it is not possible to correlate the question's semantics with data that might have been already collected during checkout (for instance, traveller-related information). Therefore, the need to re-enter certain information may rise.
Pick-up Selection
Some activities require the selection of a pickup location. To do so:
Click on the pick-up dropdown
Select the desired location
Then, a ticket option and service categories can be selected, as formerly described.
Language Selection
In some cases, activities may offer the option of more than one idiom. This selection is presented in the new UI as a dropdown. To select the preferred language:
Click on the dropdown aligned with Select the Activity Language (optional)
Click on the intended language
Limitations and Future Work
Two limitations exist for the Musement Connector integration that shall be followed up follow by the product team:
No Planner API support for "Ticket binding". While "PAX binding" is supported by the API, the new way of selecting tickets is currently not supported by TripBuilder's API, as an API extension is required.