Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

There are two screens that users will access to report and confirm services: Operations Messages and Operations Confirm Reservations.  The Operations messaging screen is designed to allow users to report manifests to their suppliers.  Reporting to suppliers is a manual process and should be handled on a daily basis to ensure all suppliers have the appropriate passenger manifest.  It is also a vital process to ensure the space on all components, such as tours, transfers and rooms are confirmed.  

Below is a high level workflow between the messages and confirm reservations screen.

Communication Timing Overview

There are two ways in which messages are triggered to be reported to the vendors suppliers: 

FIT Messages

For FIT bookings, the communication timing is set under the supplier service in Product.  In supplier services, the "comm timing" or communication timing can be set to either report passenger names, travel dates and room types under the following parameters:

  1. Deposit Received

  2. Payment in Full

  3. Report Immediately

  4. Other

  5. Release Date

For more information on the communication timing, review the services article.  

Tour Messages

For Products (set departures) and groups, the communication timing is added under a "product event."  Product events are designed        to provide users with the ability to set the communication timing based on the contract for that particular product or group.  Multiple            product events can be created for different service types.  Similar to the communication timing available in the supplier services, users        can select from the following options to set the communication timing:

  • Days prior to departure.

    • The number of days prior to the departure dates.

  • Days prior to the service

    • The number of days prior to the start of the service.

    • Because product events drive the reporting to suppliers on products/custom products which may have multiple components with varying start dates, users can choose to report to the supplier within a certain number of days to the start date of that particular service.  

  • Deposit received.

  • Payment in full.

  • Report immediately. 

Scenario

There is a wedding group that is traveling to Hotel X in 15 months.  The tour operator and the hotel draft a contract.  In that contract, the hotel advises that all rooms need to be reported within 60 days prior to the departure date.

Users can set-up two product events to send a preliminary manifest the hotel 75 days prior to the departure date and then a final rooming list 60 days prior to the departure date.  

Note:  Allocating the communication timing to either services, products or groups is a necessary step in order to run messages (communication to your vendors) under the Operation Messages screen.  

Message types

There are five different message types users can choose.  To ensure the correct manifests are being reported to the hotel, users must select the appropriate message type before proceeding: 

  • FIT Messages

    • Process FIT messages for any FIT bookings.  These bookings are created from the "vacation builder" option in reservations.

    • The communication on FIT bookings is set under the supplier's service.  

  • Tour Messages

    • Process Tour messages are used to process messages for custom groups or for products 

    • The communication timing for these messages are set under the product events.  

  • Single Res Messages

    • Users can process a message for an individual booking.  

    • Processing a message under the "single res message" option will ignore the communication timing and/or product event rules set and will process a message for all supplier services that exist on the booking.  

Note:  Bookings under an "option" status will not be reported.  

  • Air Messages

  • Tour Request Messages 

    • Tour requests provide users with more filtering options.

    • Under tour request messages, users have the opportunity to report services to suppliers without reporting passenger names.

    • An example of this would be reporting the total number of passengers to a restaurant that is included in a tour.

    • Using the tour request message option will allow users to report the number without reporting the names.  

    • Additional template setup is required.  Please contact Softrip for more information.  

Search Options:

When searching for services that are due to be reported, each message comes with different values that can be used to narrow the results.  The search options will change based on type of message that is selected from the drop-down.

Each short video below displays the options that are available to users.  

FIT Messages:

OpsMessages.mp4

Tour Messages:

OpsMessagesTours(1).mp4

Single Res Message:

OpsSingleResMessage.mp4

Once a message is run, users will have the opportunity to select the relevant suppliers that have services that are due to be reported.

Results

Once the supplier is selected, the rooming list/passenger manifest will appear in the middle of the screen.  There are two different tab views available to users: Message and Reservations. 

Message View:

The message view allows users to view all information relating to the services that exist on the bookings that are due to be reported to the supplier.  This view also allows users to customize the header and footer of the message that will be sent to the supplier, send the manifest to the supplier, mark the services within each reservation as reported and view any memos that have been created against any of the reservations that appear on the manifest.  Lastly, the messages view will dynamically pull all contact information as it relates to the supplier.

Note:  The contact information is pulled directly from the Supplier information in Product.  View the suppliers manual for more details.  

Rooming list/Manifest Information:

The rooming list or "manifest" displays a list of bookings that have been created under that supplier.  Relevant details pertaining to the booking and the supplier services will be sent when users send the email from the messages screen.  Below is a summary of information that displays on the rooming list/manifest:

  • Service description 

  • Passenger names

  • Arrival and departure dates

  • Number of nights 

  • Promotions (if applicable)

  • Special requests (if applicable) 

  • Reservation number

  • Allotment status  

Supplier Contact Information

Users can review the supplier contact information by expanding the header at the top of the screen.  This information is pulled directly from the contact information that is added to the supplier under Product Suppliers.

OpsMessagesContactInfo.mp4

The information displayed includes the following:

  • ID

  • Name

  • Email

  • Phone

  • Fax

  • Contact Type

    • The contact type is a drop-down.

    • Users will have an opportunity to change the contact information that the rooming list/manifest will be delivered to by updating the contact type.

  • Subject

  • CC

  • Communication method (Comm method)

  • Additional attachments

OpsMessagesSupInformation.mp4

Reservations View:

The messages view does not allow users to make modifications to the message; however, there are a few columns that can be updated when users are under the "reservations" tab.  These columns include the following:

  • Follow-Up

  • Comments

  • Confirmation Info

  • Cost Code

  • Pickup

  • Dropoff

Any updates that are made within the columns on this screen will appear in red until the updates are saved.  These updates will also appear on the manifest once users access the messages tab again.  

Users can also take advantage of jumping to either the booking, the inventory or the supplier information by selecting the blue hyperlinks on the reservations view.  

OpsReservationsTab.mp4

Processing Messages

When users are ready to send the manifest to the supplier, select "send email" at the bottom of the screen.  This will send the manifest directly to the email that is associated to the point of contact of the supplier.

Note:  To verify the contact information, expand the arrow at the top of the screen.  For more information, review the supplier contact information above.  

After selecting send email, users will immediately be prompted with the option to "post the message."  Posting a message will mark the message as "reported" to the supplier.  In most cases, an Operator should select “Post Now” to ensure that each service messaged to the supplier is marked as "reported" in the Softrip application system.  

Once a service is marked as reported within the reservation, the reservation will not display in the messages screen once messages are run again.

Note:  Users do have the opportunity to control/update this using the confirm reservations screen.  

A user may want to send a message to the supplier but not post it if they are simply communicating a note to a supplier but do not need it confirmed.  By sending the message, but not posting, the service will not be marked as "reported."

Example 

A service may have already been confirmed, but the user wants to remind the Supplier that a passenger is Vegetarian.  This request is noted on the manifest, so by using the messages screen, users can send the manifest to the hotel again without marking it as reported for a second time.  

Users also have the option to mark the services as reported by selecting "post message."  By selecting "post message," users will be able to mark the services as reported without actually sending a message to a supplier.  Users would typically use this option if they are manually reporting to a supplier outside of the system either by phone or third party interface.

Note: Once a service is marked as "reported" users will be able to verify this in reservations.

This can be verified either in the cart or under the "edit item" option.

If users see "M1" either in the cart or under the edit item option, the service has been reported once.

If users see "M2," etc, then the service has been reported twice.  The second value will increase with the number of times that the service has been reported.  

OpsSendingMessages.mp4

  • No labels