How to use the Android App as an Operator
The Wetu Itinerary App, named TravelKey, allows your client to travel with all the required travel documentation on their mobile device. The Wetu Itinerary App caters for the market that travels with their mobile by replacing the paper documentation and providing additional functionality and information. The app is available for free!
This functionality is only available with the Enterprise package.
Getting the Itinerary App Code
When you build a Personal Itinerary in the Wetu Itinerary Builder, one of the automatic outputs is the Mobile Code.
This app code will not generate if your Personal Itinerary does not have dates.
This 6 digit code is not automatically included in any of our other outputs and you need to specifically supply it to your client for them to get access to their itinerary via the app.
Downloading the App
From a mobile device, navigate to the Google Play Store and search for "TravelKey". Alternatively, it can be downloaded by clicking here
Note: when searching on a tablet, please ensure that you are searching for cellphone apps, as it is not listed under tablet apps.
Navigating through the App
Once the app has been downloaded to a cell phone or tablet, simply navigate to the app, open it up and enter the 6 digit code found on the last step of the Itinerary Builder. The traveller will also be prompted to enter a name and email address, this information is used for personalised notifications and for the chat function (more on these later).
Once this has been done, the Personal Itinerary will then download and open.
Within the app, the traveller will have access to the below options via the menu depending on the information that has been entered in the Itinerary Builder. Below we will explain what information will display as well as where in the Itinerary Builder that information needs to be entered to display on the app.
This is the first screen the client will see and can return to it via this navigation. This screen includes general information of the itinerary.
The logo on the top of this screen is based on the branding selected for the itinerary; co-branding and rebranding are supported. This screen also displays the Itinerary Name, Client Name, Destinations included in the itinerary, as well as the Summary entered on the final step of the Itinerary Builder.
Here you will find the majority of the information pertaining to the trip. For each day or collection of days, the traveller will be able to find details regarding their accommodation, transport, activities, daily information, inclusions, exclusions, weather and more.
The information within each day, or collection of days, is based on the information entered in the Accommodation step, the Route Builder (or Travel Detail) as well as the Planner step.
Each of the Destinations included in the itinerary will be outlined here.
This information is collected automatically based on the accommodation that was entered in the Accommodation step.
In addition to information about the Destinations included in the itinerary, the traveller will have access to information for Countries as well. This section includes details on electricity, cuisine, climate, transport, dress code and more.
This information is selected and displayed automatically, based on the Destinations included in the itinerary.
If the trip includes any self-drive sections, this section will include the static map and turn by turn directions.
These directions are based on what was entered in the Route Builder step of the Itinerary Builder.
The traveller can access and download any document to their device.
The documents that display in this section are based on what documents were uploaded to the itinerary on the final step of the Itinerary Builder.
The main contact for the itinerary will display at the top, either the consultant or company details. These are then followed by the contact details of the accommodation's included in the itinerary and finally any additional contact details that were entered in the Review step.
Within the Settings option, the traveller will have the ability to click on/off their local push notifications. These notifications are scheduled to go off automatically at 19:00 local time (based on the device). The notifications are simply to prompt the traveller to return to the app to check their next day's activities.
Push notification example 1: Your adventure starts in [destination], [weather] expected.
Push notification example 2: Tomorrow you will be checking into [accommodation name]. Find out more about your time in [destination] here.
Note: At this stage, these notifications are not customisable.
Within the Settings option, the traveller can also change the itinerary that is loaded on TravelKey, simply by selecting "Change Itinerary" and entering a new 6 digit App code.
Tap to Refresh:
This allows the traveller to quickly update the itinerary. If any changes have been made in the Itinerary Builder, the traveller will have to 'Tap to Refresh' for those changes to reflect. At this stage, there is no push notification to advise the traveller automatically if a change has been made.
TravelKey has been designed to have functionality that works even if the traveller is not connected to mobile data or Wi-Fi. The traveller will need to download and access their itinerary at least once, while connected to the internet, to allow the initial content to load. Once offline, the following is affected:
- All image galleries are no longer available (accommodation, activity, country, destination, day tour, etc)
- Documents will not download
- Chat functionality will be disabled
All the other information is text based and as this all loads when the itinerary is loaded initially, it will be available offline.
TravelKey in Different Languages
Although TravelKey supports all 12 languages that are available in the Itinerary Builder, in order for the itinerary to appear in any other language, the correct language needs to be selected on the device itself.
You can select the language by accessing Phone Settings and navigating to Langauge and Input. Here you can select the language to match what is selected in the Itinerary Builder and when then the app is loaded, the framework will translate into the correct language.
You can find similar information and instructions that you can provide directly to the traveller, here.