How to work with booking import feature?

1) Making a reservation

When making a reservation through Smartpoint, it's important to manually add the mandatory information, or use a SmartButtons script.

The primary way to link the mobile application user (Passenger) and the reservation owner (Booking person) is through their email address. The email used for the passenger's mobile application registration must be the same as the one entered in the reservation.

Additionally, the booking person should be registered as a GOL IBE (GOL) user. They can either register through the mobile app or not. Accounts for booking persons can be manually created in the AdminConsole under the Customers section. If the passenger and the booking person are the same individual, you can disregard this step.

Email entries in the GDS are noted as follows:

>For passengers to see their bookings in the app, use the NP remark.

> For booking persons to see bookings, use the EM remark.

To display the contact info of either the booking person or the passenger in the app, use the DI Remark.

Please note that if the GOL IBE does not find a booking person's email in the EM remark or the addresses in the AdminConsole, the reservation will not import successfully.

For email addresses:

Use "//" instead of "@"

Use ".." instead of "_"

2) Automatic import of reservations

Reservations must be placed on Queue 29, which GOL scans for updates to display in the mobile app. Initially load your reservation once; after that, any changes to the reservation synchronize automatically since GOL monitors these bookings.

New bookings are checked from Queue 29 every 5 minutes.

Verify that reservations are correctly loaded by checking the AdminConsole under the Reservations section. All successfully loaded reservations will have a record there.

3) Manual import of reservations

To manually import a reservation, go to the list of bookings and click on the "+Add new" button. Enter the booking code. This reservation does not need to be on Queue 29. The import will proceed if the content of the email addresses matches the addresses stored in the AdminConsole (Database of registered users).