This section lists the setup items needed to support the SIRVA QLAB Lead Upload and SIRVA QLAB Lead/Opportunity Download.
In addition to this setup, configuration is also required in MoversConnect. Please contact MoversSuite Professional Services for setup information related to MoversConnect.
For a lead to be sent to SIRVA QLAB, all required data must be defined for the record. Please see SIRVA QLAB Lead Upload for required fields and appropriate settings.
The following table describes the administrative setup needed in MoversSuite to support integration with SIRVA QLAB.
|
IMPORTANT |
|
Errors will occur during upload and download processes if setup is incomplete and/or inaccurate. Contact SIRVA the most accurate list of supported codes and information. |
|
NOTES |
|
SIRVA QLAB Integration utilizes MoversConnect to communicate between MoversSuite and SIRVA. Setup in addition to the items listed is required. Please contact MoversSuite Professional Services for setup details. |
|
Setup for SIRVA QLAB Integration is considered an addition to that needed for SIRVA sHub Integration. |
|
Your company must be setup for SIRVA QLAB. |
|
SIRVA QLAB can utilize the Pass Thru Connector to gather information from an outside service and push the lead or order into MoversSuite. This requires additional setup and considerations. Refer to Pass Thru Connector Setup and Administration. |
|
Setup |
Description | ||||||||||||||||||||||||
|
Verify that the following entries exist with this setup. These are the only two countries valid for addresses associated to the SIRVA QLAB Lead Upload.
| |||||||||||||||||||||||||
|
SIRVA QLAB Integration utilizes MoversConnect to communicate between MoversSuite and SIRVA. Additional setup is needed. Please contact MoversSuite Professional Services for setup details. | |||||||||||||||||||||||||
|
Verify that note type records are defined that include a Van Line Code of “LEAD” and “QLAB.” The following table includes recommended Note Type values.
Notes associated to a Van Line Code of “LEAD” originate from a SIRVA QLAB Lead/Opportunity Download. Notes associated to a Van Line Code of “QLAB” originate from a SIRVA QLAB Lead Upload. | |||||||||||||||||||||||||
|
The Salesperson assigned to the Lead/Opportunity must be linked to QLAB. For all appropriate personnel, set the Interface Mapping to the Interface of “Qlab,” Labor Type of “Sales,” and the UserID assigned to the person through SIRVA, e.g. “Q0186009999.” | |||||||||||||||||||||||||
|
The “QLAB Integration” module has no effect on security, therefore it does not have to be assigned to any profile. | |||||||||||||||||||||||||
|
Phone types in MoversSuite must link to those supported by SIRVA. Create the following types to support uploads and downloads to the QLAB system for the SIRVA interface.
The above External Code values must be established and linked to phone types to support upload and download requests through the QLAB system. | |||||||||||||||||||||||||
|
Define QLAB interface with a Vendor Name of “Qlab.” Then, link all supported branches to this interface by adding them as Branch Items with appropriate Authority Type (cross reference Branch Setup). | |||||||||||||||||||||||||
|
Create two system records: One for Order Information uploads and the other for Lead/Opportunity downloads.
Order Information Uploads Define a system record for the Qlab Interface. Set the Internal System and External System values to “Qlab” as well and create the necessary system data type mapping with the following data type. To process QLAB upload requests:
Lead and Opportunity Downloads Define a system record for the Qlab Interface. Set the Internal System and External System values to “Qlab Leads” as well and create the necessary system data type mapping with the following data types.
To process QLAB download Opportunity requests:
|
RELATED TOPICS:
MoversSuite Fields Referenced by SIRVA
SIRVA QLAB Lead Upload Content
SIRVA QLAB Lead/Opportunity Download