Uses the Component:SalesLeadDetailType
Sales Lead Detail
Table 6.102. Fields and Components
| Name | Description | Occurrence | Type | Data Type | User Notes |
|---|---|---|---|---|---|
| LeadStatus |
Status of Sales Lead. Ex: Appointment made, Just looking, etc.. | 0..1 | Field | udt:TextType | |
| Preference |
Identifies what qualities are important to the contact. | 0..* | Field | udt:TextType | |
| Financing | 0..1 | Component | FinancingABIEType | ||
| Appointment |
The Appointment component represents information about an appointment such as service appointment including appointment date, appointment time, etc. | 0..* | Component | ServiceAppointmentExtendedType | |
| SalesActivity |
Represents the activities that occur for a Sales Lead | 0..* | Component | SalesActivityType | |
| LeadRequestTypeString |
Identifies the type of lead request. EX: Brochure Request, Test Drive Request, Quote Request, etc. | 0..1 | Field | qdt:StringType | |
| LeadIndustryTypeCode |
Industry type identifies the type of industry to which the lead applies, i.e., automotive, marine, truck, powersport, etc. | 0..1 | Field | scl:LeadIndustryTypeEnumeratedType | |
| SalesLeadLineItem |
The detail information for a Sales Lead Line Item | 0..1 | Component | SalesLeadLineItemType | |
| CompetingSalesLeadLineItem |
The detail information for a Competing Sales Lead Line Item | 0..1 | Component | SalesLeadLineItemType | |
| LeadDepartment |
The department in the dealership that the lead applies to. | 0..1 | Field | udt:TextType | |
| ExpirationDate |
Expiration Date | 0..1 | Field | udt:DateType | |
| ID |
A unique identifer for the sales lead detail information. | 0..1 | Field | udt:IdentifierType | |
| ServiceContract |
The ServiceContract component represents information about the extended service agreement on the vehicle. | 0..* | Component | ServiceContractType | |
| ETADate |
Estimated time of arrival | 0..1 | Field | udt:DateType |
The XML Sample provided here is an approximation of the generated XML for this component. Not all of the fields are required for implementation.
Example 6.102. SalesLeadDetail
<SalesLeadDetail>
<LeadStatus>......</LeadStatus> [0..1]
<Preference>......</Preference> [0..*]
<Financing>......</Financing> [0..1]
<Appointment>......</Appointment> [0..*]
<SalesActivity>......</SalesActivity> [0..*]
<LeadRequestTypeString>......</LeadRequestTypeString> [0..1]
<LeadIndustryTypeCode>......</LeadIndustryTypeCode> [0..1]
<SalesLeadLineItem>......</SalesLeadLineItem> [0..1]
<CompetingSalesLeadLineItem>......</CompetingSalesLeadLineItem> [0..1]
<LeadDepartment>......</LeadDepartment> [0..1]
<ExpirationDate>......</ExpirationDate> [0..1]
<ID>......</ID> [0..1]
<ServiceContract>......</ServiceContract> [0..*]
<ETADate>......</ETADate> [0..1]
</SalesLeadDetail>