Setup MeetingBroker integration
Administrators need to complete several tasks when a property acquires a MeetingBroker integration.
Users
Administrators need to create a user profile in both Delphi and MeetingBroker for each user that responds to leads.
The user’s email address needs to be the same in both systems. If you have eProposal, the email address in the Cendyn user profile needs to match as well.
Users who perform the duties of the Default lead coordinator (DLC) require full access to every lead. They need to have Director access to the location in MeetingBroker and Edit All Records access in Delphi. See the following topics for help:
In MeetingBroker, changes to email addresses and user names can only be completed by the user. If you find a discrepancy after you save the profile, ask the user to log in to MeetingBroker, click My Profile, and make the correction.
If changes are made to users in Delphi, the same changes need to be made in MeetingBroker.
Property details
Complete your property’s details in both systems. See the following topics for help:
Default Lead Coordinator
The MeetingBroker section of the Delphi property page has a Default Lead Coordinator (DLC) field. New RFPs are sent from MeetingBroker into Delphi, and an inquiry is created. The user who is assigned as the DLC in MeetingBroker is assigned as the owner of the inquiry. If MeetingBroker is unable to find that user in Delphi, the inquiry is assigned to the user in the Default Lead Coordinator field in Delphi.
If you want to change the DLC for your property, you need to update the DLC fields in both systems.
Setup values
Seven types of setup values are shared between MeetingBroker, Delphi, and the channels:
| MeetingBroker name |
Delphi name |
Delphi location |
|---|---|---|
| Event Setups | Function Room Setups | Setup Values |
| Event Types | Event Classifications | Property Page > Event Classifications |
| Lead Sources | Lead Sources | Setup Values |
| Lost Business Reasons | Booking Lost Reasons | Setup Values |
| Market Segments | Market Segments | Setup Values |
| Meeting Types | Booking Types | Setup Values |
| SIC Codes | Industry Codes | In Salesforce Classic: Setup > Build > Accounts > Fields In Salesforce Lightning: Object Manager > Account > Fields & Relationships |
To ensure information is shared accurately between the channels, MeetingBroker, and then Delphi, you need to compare and map these values. First, you need to compare your MeetingBroker location setup values with the values defined in Delphi. Then you need to map these setup values with your channels.
Location setup values
First, make sure that your library of location setup values from MeetingBroker includes the values from Delphi. To see your current location setup values in MeetingBroker, click Administration, open your location, click Settings, and then click Setup.
If no exact match exists for a Delphi value, you can add it to MeetingBroker and then map it to a similar subscription value. For example, if Delphi has 'U-Shape' as a function room setup, but MeetingBroker has 'U - Shaped,' do the following:
- Click Add below the Event Setup Type section. A blank field is added to the bottom of the existing list.
- Enter 'U-Shape' in the Setup Value column.
- In the Map To column, select the corresponding value, for example, 'U-Shaped.'
- When all values are added and mapped, click Save.
If the Setup Value column is blank, add all your Delphi values to the appropriate section.
If you see values listed in the Setup Value column that you cannot edit, those are subscription values controlled by your corporate administrator.
Channel setup values
Next, you need to map your values with each channel you subscribe to. If mapping is not done, the values display as 'unknown' in the RFP and are blank when you create the booking in Delphi. In MeetingBroker, click the Channels sub-tab in the Settings folder and select Active in the Viewing list.
If you have eProposal, two Cendyn channels display as active. No action is required for those channels because they do not have setup values.
To map a channel’s setup values, do the following:
- Click the channel to open the Information page.
- Click Auto Map and wait for the yellow confirmation message to display. If any of the channel’s values match your subscription or location values, they map automatically. Values that are not matched during the Auto Map process begin with 'Unknown.'
- Review all the selections in the Your Value column and make sure they are values you use in Delphi. Select the best matching Delphi value from the list in the Your Value column.
- Click Save and Close.
- Repeat the steps for each active channel.
If none of your values are similar to the channel's value, you can leave the value as 'Unknown.' For example, a channel has an event type of Golf, but your location does not offer golf. In this case, the sales manager needs to discuss the event with the planner rather than mapping the event type to something that does not apply.
Outbound mapping
Channels that receive business data from MeetingBroker also require mapping of outbound information. The following table explains which channels and values you need to map.
| Channel name |
Inbound |
Outbound |
|---|---|---|
| Cendyn eProposal | No | No |
| Cendyn Notifications | No | No |
| Cvent | Yes | Only Lost Business Reason |
| Groups360 | Yes | Only Lost Business Reason |
| SpeedRFP | Yes | Only Lost Business Reason |
| SignUp4 | Yes | Only Lost Business Reason |
| Venue Directory | Yes | Only Lost Business Reason |
| 1000Meetings | Yes | Only Lost Business Reason |
| Your Local Convention & Visitor's Bureau | Yes | Only Lost Business Reason |
| Private CRM Channels, including Central Sales or Smarter Sourcing, depend on the channel design. If you see values listed in the channel, full mapping is available in both directions. | Yes | Yes - All Values |
Guestroom type mapping
MeetingBroker has four categories of guestrooms:
- Run of House
- Standard
- Double
- Suite
You can cross-reference the four MeetingBroker guestroom categories with four of Delphi’s guestroom types in the MeetingBroker Information section of the Property page.
After you complete these tasks, your team is ready to receive and respond to leads.
Cross-subscription integration (CSI)
You have a cross-subscription integration (CSI) if you receive RFPs from more than one MeetingBroker subscription and those subscriptions are all integrated with Delphi.
For example, your management company has a MeetingBroker subscription that includes RFPs from your property’s website and Cvent. Your brand has a separate MeetingBroker subscription that includes RFPs from the regional sales offices and the central reservations desk. With CSI, all RFPs are sent to Delphi, and the steps are consistent for creating bookings and sending proposals and business data back to MeetingBroker.
If your property is configured for CSI, make sure you read this page in MeetingBroker Training & Help: Overview: Cross-Subscription Integration (CSI).
If you have multiple MeetingBroker subscriptions and want to have them integrated with Delphi, contact your Amadeus sales representative.
Learn more...
Learn about the RFP business cycle
Understand how to satisfy assignment rule escalation