Manual Flight Booking Process Description


This article describes two processes for manual flight booking through the Griffin Marine travel interface.


Introduction

In the Personnel Manager, we have various travel interfaces for flight bookings. This article describes the manual flight booking process through the Griffin Marine travel interface. This interface is recommended for manual flight booking regardless of the travel agency that you have.

The interface is not integrating with any external systems, the data input is completely manual on the user end.

Process description

Option 1

Only the Crew Travel has access to the Personnel Manager.

  • The module for manual flight booking by Crew Travel is Crew Change.
    Travels Module can only be used by Crew Travel to see the overview of all the bookings.
    Access to this functionality can be limited.

Process:

  1. Crew Travel submits ManualBook requests in the Adonis > Crew Change Module.

     

  2. Adonis can create an automatic notification to be sent to the flight agent from Adonis with all the info required for the travel.

  3. Crew Travel communicates to the flight agent externally and confirms the flight options.

  4. Once the option is selected by Crew Travel the ticket info can be added to Adonis.

     

  5. If the flight details change, Crew Travel can cancel the flight request from Adonis.

     

  6. Adonis can create an automatic notification to be sent to the flight agent on the cancellation.

  7. The refund discussions should be outside of Adonis.

Option 2

Both the Crew Travel and flight agent have access to the Personnel Manager.

  • The module for Crew Travel is Crew Change.
    Travels Module can only used by Crew Travel to see the overview of all the blookings.
    Access to this functionality can be limited.

  • The module for flight agents is Travels.
    Access to this functionality can be limited.

Process:

  1. Crew Travel submits a Booking request in Adonis > Crew Change Module.

     

  2. Adonis can create an automatic notification to be sent to the flight agent informing them that there is a new flight request.

  3. The flight agent logs in to Adonis > Travels Module, reviews the flight request, adds additional information, and approves it (issues ticket info).


    Upon approval, it is necessary to add the segments.

     

  4. Adonis can create an automatic notification to be sent to Crew Travel that the flight has been issued/approved with the following info: ticket details, and segments.

  5. Crew Travel can check the issues ticket info in the Crew Change Module.

     

  6. If the flight details change, Crew Travel can cancel the booking or request a change from the Crew Change Module.

     

  7. Adonis can create an automatic notification to the flight agent on the cancellation/ change.

  8. If the cancellation is requested, the flight agent should confirm it in the Travels module. The refund discussions should be outside of Adonis through e-mails.

     

  9. If the change is requested the flight agent should confirm it in the Travels module.