Get started with the TripBuilder consumer IBE in combination with marketplace supply and reservation request. This article walks you through the most important steps.


  1. Overview
  2. Booking Process with Reservation Request
  3. How to Get Started

 

1. Overview

Nezasa's TripBuilder IBE with marketplace supply provides an all-in-one solution to sell personalized itineraries through your own website to your consumers.

Most of our customers opt for our default solution, which comes with online payment. Read More

However, if you prefer to give your consumers the planning tool without online payment, that is possible too. We call this the TripBuilder IBE with a reservation request checkout

2. Booking Process with Reservation Request

The booking process, in this case, looks as follows:

Step 1 - Reservation Request

The consumer accesses your company's website with the embedded TripBuilder IBE, plans the trip, and goes into the checkout.

The checkout will include gathering the PAX details and triggering a reservation request. After this point, the consumer, as well as you, will receive an email notification.

From this point onwards, the consumer will no longer use the TripBuilder IBE on your website.

Step 2 - Check Booking Request

As a tour operator, you will need to check the reservation request and perform the booking with your tour operator user in the TripBuilder. If the itinerary contains components from the Nezasa marketplace, you'll be asked to pay by credit card. This is by using your corporate credit card, not the consumer's credit card.

  1. Open the booking in the Cockpit Customer Care 
  2. Verify if the itinerary is consistent. At this point, you are still free to adjust the itinerary. No third-party supply has been booked yet.

Tip 1: In Customer Care, you can search by consumer name or by the itinerary ID which was mentioned in the email notification.

Tip 2: Check out the Notes feature in the detailed view of this itinerary. That's the place where internal remarks related to the booking can be stored.


Step 3 - Get Consumer Pre-Payment

Because your IBE does not include the online payment feature inside of TripBuilder, you'll need to get the payment from the consumer outside of the platform: be it by invoice, cash, if the consumer is in your office, or with another online payment solution (Stripe, Payrrex, Paypal, Twint, etc.).

Step 4 - Perform a B2B Booking

Perform the booking with your tour operator user in TripBuilder. If the itinerary contains components from the Nezasa marketplace, you'll be asked to pay by credit card. This is by using your corporate credit card, not the consumer's credit card.

  1. You should be logged in with your user account
  2. Open the booking in TripBuilder (e.g., use the link for collaborators in the sidebar of Customer care)
    60d2f17701ca8.png
  3. Go through the checkout process and trigger the booking.

Step 5 - Inform the Consumer

Once all is done, send the consumer the travel documentation and vouchers.

3. How to Get Started

The TripBuilder on-boarding process is documented in the table below in the form of checklists. The Nezasa support team will also guide you through the steps. The process is similar to the one including the online payment, except that the additional terms and conditions can be skipped and, thus, are not listed on this page.

Checklist - Agreements & Terms

The following contractual steps are required to get started.

Step 1

Product Plan

Subscribe to the product plan “Standard” or higher. 

Step 2

Order the Consumer IBE & Accept Service Terms

Please trigger the consumer IBE setup process with Nezasa’s support team and accept Nezasa’s service conditions for consumer bookings.

When doing so, please inform us whether you opt-out of the online payment feature or if you would like to have the reservation request checkout configured.

Checklist - IBE Configuration

This checklist goes through the available configuration options for your IBE.

Step 1

Base Setup by Nezasa

Get confirmation that Nezasa has enabled the consumer IBE for you.

Step 2

White-label Domain

By default, the IBE runs on a dedicated domain. While Nezasa provides such a subdomain (*.tripbuilder.app), it is highly recommended to use a subdomain of your primary domain because of the “third-party cookie policy” of modern browsers. 

Example: your main domain is “www.company.com” and you choose to use “ibe.company.com” for the consumer IBE of Nezasa.

Read more

Step 3

Embed IBE into your Website

Set up a path and page on your website where the IBE will be integrated.

Read more

Step 4

Configure your IBE

There are plenty of configuration options available. Here are the most important ones:

  • Terms & Conditions
    Configure the IBE checkout so that the user has to accept the Terms & Conditions. This may also involve topics like EU-GDPR or EU-PRRL checks.

  • Cancellation Policy
    As a tour operator, you’ll enforce package cancellation policies that need to be defined and applied. You can either pack them into your Terms & Conditions or use the system's “cancellation policy” feature. 

  • Payment Terms
    Define what down payment you’ll ask from your consumers.

    Remember: if a booking contains marketplace components, the system might apply a higher down payment. 

  • Markups
    Define what markups you will add to your net price for the different product categories. Read more

Step 5

Testing

It is essential to test all your settings and maybe even do a test booking. Here are some important remarks when it comes to testing:

  1. Test as "consumer"
    The final tests should take place in the same way as a real customer of yours would use the website. This is absolutely crucial! Doing the tests directly on TripBuilder portal while being logged in with your admin user might lead to different results as your user has special permissions which leads to more features being available or more information being shown.

  2. Test Booking
    Perform a real booking with an actual credit card. When doing so, do not use marketplace supply because it will trigger bookings in supplier systems. Use ad-hoc components instead and make sure the value of the itinerary is small. 
    Thanks to this booking test, you'll also be able to test the refund feature in the Payyo backend UI.

Comments

0 comments

Please sign in to leave a comment.