|
|
|
Profile Lookup Message
The Profile Lookup Message functionality is available with the following license codes:
This message format will be used to request a profile lookup either from OPERA or from the PTS. Within the OPERA module, all profile searches shall initially be checked locally, and if the user does not find a matching profile, a PTS lookup takes place. The profile lookup message permits OPERA to receive information from an established PTS account in order to populate a profile in OPERA. From the initial lookup request, either a single or multiple matching profile response could be returned, and upon OPERA user selection, the PTS profile will either update the existing OPERA profile or create a new one.
The OPERA profile search screens include a Lookup button, which will initiate a lookup into the PTS. PTS needs to store the OPERA profile ID and property code to identify the right profile when changes are done to it in OPERA. The PTS can store a collection of addresses and communication methods in the profile.
A guest established a PTS account on a prior visit to the property and did not previously stay. The guest is making a reservation to stay in the hotel for the first time and therefore the profile does not exist in OPERA.
Profile lookup can be invoked at any time— before, during, or after check in.
The entry point for profile lookup is the Profile Search screen.
Lookup can also be invoked by a card swipe or through entering the player ID from selected areas within the OPERA application.
The profile lookup operation consists of two message transactions. First a message is sent that includes the search criteria to match on that has been entered into the Lookup screen. This may include at a minimum the person’s first and last name, or an external player ID. The response to this message is a list of matching profile summary records. The summary records will include the name and address of the profile, plus a required player ID that is used in the next step. If no matches are found, an appropriate message is returned.
From the summary list, a profile is then selected. A second message is sent out to fetch the required profile using the player ID returned in the summary list. The response message with the player details may include multiple addresses, phone numbers, and other details for an individual player.
In case many profiles are matching a lookup request, OPERA will present 10 profiles at a time up to a maximum of 100 profiles. If the lookup request yields too many matching profiles, an appropriate message will be displayed to the OPERA user that the lookup has to be refined.
During look-up the selected PTS profile will be merged into an existing OPERA profile if a match is found. The rules for determining whether a profile matches the selected external profile are configurable within Opera. If no match is found, the selected PTS profile is added to the Opera database.
Once the lookup is successfully completed that resulted in the creation of a new profile, a full profile message is sent back to PTS with the OPERA profile ID. PTS will store the OPERA profile ID/property code for later reference and as matching criteria when exchanging further profile changes with OPERA.
OPERA will have a provision to define which lookup search criteria are mandatory.
To initiate the Lookup functionality, select the Lookup button from the Profile Search screen. In installations where there are multiple external systems from which to lookup, the following form appears:
In this case, the Gaming system, a Loyalty program, and an External Activities scheduler are all available. Select the Gaming button to bring up the following form:
At a minimum, the guest’s last and first name are required. Additional search criteria may be sent to narrow the search. The PTS may respond with multiple matching records. In this case, OPERA presents a summarized list of the profiles for the used to select the desired entry.
OPERA performs a profile merge that attempts to match incoming profile information with existing records. OPERA does not allow two profiles that have different player IDs to be merged. However, if both profiles have the same player ID, or one of the profiles does not have a player ID, a merge will be created.
For additional information about this form, see Gaming Lookup.
The ProfileLookup operation sends a ProfileLookup request message, which may include a player ID, the guest’s name, and address details. The response is a list of ProfileLookup records that match the requested parameters. From this list, the user may select a desired profile, and transfer complete details into the OPERA system.
The FetchProfile operation retrieves complete profile details from the external system for the profile selected by Profile Lookup. The calling system sends the external profile ID (returned as part of the profile list elements), and the receiving system responds with a complete profile message.
|
See Also |
