It gives you the option to white-label your travel agency or any of your travel agencies to operate on our Back-Office platform under a customized URL and a customized look.
Create your own labeled environment.
Let’s say your travel agency name is “My Travel”.
Instead on operating in https://hsp.gimmonix.com/ as your BackOffice or B2B environment, you will be operating in your own domain, for instance: agent.mytravel.com.
This will allow you to customize your login page, backgrounds, upload own CSS, etc.
You can also have own white-label for any of the travel agencies located under your company hierarchy.
Simple 5 Steps :
Configure two CNAMES (Aliases) in your domain host admin panel. See the Domain Configuration header ahead for more detailed instructions.
Send us the sub-domain name that will be used for your Backoffice / B2B (for example: “agent.mytravel.com” or “backoffice.mytravel.com” or "b2b.mytravel.com").
Make sure that your new domain is reachable by sending it ping command. and also make sure that once you run “nslookup” on your domain (using this site: http://ping.eu/nslookup/ or windows tool) your are getting the following results:
Send us your .pfx file and tell us the password to access the file. See the SSL Setup header ahead for more detailed instructions.
In case you are requesting to white-label one of the travel agencies that are located under your company hierarchy, please send us the Node Id and Name that you've created and assigned for them. After we complete the white-label setup, the possibility to customize the login page of the white-labeled B2B will be available for that node.
*.pfx file secured at least 2048 bit + Password protected. The pfx file should be extracted from the SSL verification for the domain you’re configuring.
Log in to your domain host admin panel.
- Create a new CNAME record.
- Enter an Alias Name. For example: "backoffice.mytravel.com" and "awverify.mytravel.example.com" (Temporary domain for verification).
- Point it to Host Name: "ekkworldtravelink.azurewebsites.net" and "awverify.ekkworldtravelink.azurewebsites.net" accordingly.
- TTL — Select how long the server should cache the information.
Remember that it can take up to 72 hours for DNS changes to go into effect, depending on the record's TTL value when you made the change.
Updated 15 days ago