14Leads

This chapter contains the following:

Leads provide a way for your sales organization to capture the potential interest in your products. After your organization qualifies the information and determines the lead is worth pursuing, you turn it into an opportunity and the sales process begins in earnest.

Use the Contact time zone field to capture the preferred time zone of a contact pursued on your lead. The contact time zone is based on the contact address and helps you know the preferred time to call or email a prospect or customer. You can also use the functional who columns to capture the record history of a lead. The columns let you accurately report on leads that are imported from other systems.

Other lead management features help to align marketing and sales objectives from lead generation to lead execution. Lead information is generated from a variety of sources and captured from:

  • A company's existing contacts

  • Sales campaigns

All leads then undergo the qualification and assessment process and are qualified either manually by a salesperson or automatically based on predefined rules. Finally, qualified leads are converted into opportunities.

Lead Processing

Overview of Lead Processing

Lead data is generated from a variety of sources and goes through further enrichment based on updates and follow-up activities. As a result, lead quality must be assessed periodically so that leads are distributed to the right salesperson to ensure timely lead follow up and closure.

This section contains information about how to import lead data from an external data source into your sales application using the Import Management feature.

This topic provides an overview of the components used to import data.

Import Process Flow

The following figure explains the various stages in the import process:

Import process flow
  1. Evaluate your import data.

  2. Identify the relevant import objects.

  3. Map your data to the import objects.

  4. Create an import activity.

  5. Verify the import results.

Import Objects and Import Queue

You can find details about the attributes such as data type, length, and user key information for each object on the Import Objects tab. You can download the template for each import object by clicking the Download icon. You can create a mapping either while creating an import or separately using the Import Objects tab. On the Import Object Details page, click the Display Name link for the object to navigate to the Manage Mapping page. On this page, you can create a new import mapping, upload a map, or manage an existing mapping.

The Import Queue tab lets you view the imports that are in various statuses, such as active, completed, or unsuccessful. You can further drill down into an import activity by clicking the import name link to view the status details.

Application Composer and Custom Extensions

If you create additional attributes on an object in Application Composer, then these extensions are available for import and export once you publish your sandbox.

Import Your Sales Lead Data

Use this topic to import Sales Lead data into Oracle Applications Cloud. You can use the import functionality to create, update, or delete Sales Lead records.

To import Sales Lead records, perform the following tasks:

  1. Map your source sales lead data to Oracle Applications Cloud object attributes.

  2. Create source Comma Separated Values (CSV) file for import.

  3. Create the import activity.

  4. Review the import results.

Use the Contact time zone field to save the preferred time zone of a contact pursued on your sales lead. The contact time zone is based on the contact address and helps you know the preferred time to call or email a prospect or customer. You can also use the functional "who" columns to save the record history of a sales lead. The columns let you accurately report on sales leads that are imported from other systems.

Other sales lead management features help to align marketing and sales objectives from sales lead generation to sales lead execution. Sales Lead information is generated from a variety of sources and obtained from:

  • A company's existing contacts

  • Sales campaigns

All sales leads then undergo the qualification and assessment process and are qualified either manually by a salesperson or automatically based on predefined rules. Finally, qualified sales leads are converted into opportunities.

How You Map Your Source Data to Target Object Attributes

To import your sales lead data into Oracle Applications Cloud, you must populate a .csv file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You must do the following before creating the .csv file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your objects.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

  • Identify the target object attributes that are required in the .csv file for a successful import

To better manage your sales lead information, the sales lead object has the following child objects:

  • Sales Lead Contact

  • Sales Lead Product

  • Sales Lead Resource

If you want to import only a few records, then you can create a single CSV file for all sales lead attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the sales lead child objects. Note that you must have imported the CSV file for sales lead object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Applications Cloud.

The preferred options to uniquely identify an object record are as follows:

  • Internal ID: If you're identifying a record that already exists in Oracle Applications Cloud, then you can use the internal ID of the record, a system-generated unique identifier Attributes with "id" in the attribute name are typically internal IDs. You can determine the internal ID of a record by exporting Oracle Applications Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Sales Lead object, this attribute is LeadId.

  • Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Sales Lead object, the attribute is LeadNumber.

Required Attributes and Validations for Sales Lead Object

To import data successfully into Oracle Applications Cloud, your .csv file must include the required attributes. Ensure that you provide valid values for the attributes.

This table lists the required attributes for importing new Sales Lead records, required attributes for updating Sales Lead records, prerequisite setup tasks for the attributes, and specific validations, if any, for Sales Lead import:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Sales Lead record Updating an Existing Sales Lead record

AcceptedDate

The date the recommended lead generated by the Sales Prediction engine was accepted by a sales person or lead qualifier to pursue

No validation

A value is required if you specify the value for LeadAcceptedFlag as Y.

Not required

ActionCode

Indicates explicitly the operation to be performed on a row: INSERT to create a new record in the destination tables, UPDATE to update an existing record in the destination table, DELETE to delete the record.

If no value is provided, the record is updated if it already exists. Else, it's inserted

Not required

Not required

ConvertedTm

The date when the lead was converted to an opportunity

No validation

A value is required if you specify the value for Lead StatusCd as CONVERTED.

Not required

LeadName

The name that identifies the lead

No validation

A value is required if you're creating a new lead.

Not required

LeadNumber

The Lead's public unique identifier value

If providing a value to update an existing lead, the value must exist in the column LEAD_NUMBER.of the MKL_LM_LEADS table.

If providing a value and creating a new lead, the value must be unique.

A value is required, if updating an existing lead and you're not providing the unique ID of the lead (ObjectKey)

ObjectKey

The unique ID for the existing lead record in the destination table

Automatically generated by the import process if creating new record. If updating an existing record and providing the LEAD_NUMBER, the import process defaults the LEAD_ID.

Do not provide a value if creating a new lead.

A value is required, if updating an existing lead and you're not providing the LeadNumber.

OwnerId

The unique ID for the existing resource party in the destination table. The owner must also be an internal resource included as a member of the lead's sales team

If providing a value, the value must exist in the column PARTY_ID of the HZ_PARTIES table, The value must also exist in the column PARTY_ID of the JTF_RS_RESOURCE_PROFILES table. The identified party must be assigned as a sales team resource for the existing lead or included in the resources imported in the same batch as this record.

A value is required, if creating a new lead and you don't provide the owner's source system code and reference (OwnerOrigSystem and OwnerOrigSystemReference)

Not required

QualifiedDate

The date when the lead was qualified

No validation

A value is required, if you optionally provide the lead status (StatusCd) value as QUALIFIED, indicating that the lead is qualified.

Not required

RejectedTm

The date when the lead was rejected

No validation

A value is required, if you optionally provide the lead registration status (ApprovalStatus) value as REJECTED, indicating that the lead is rejected.

Not required

RetiredTm

The date when the lead was retired

No validation

A value is required, if you optionally provide the lead lead status (StatusCd) value as RETIRED, indicating that the lead is retired.

Not required

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the sales lead object. The page also lists attribute information like type, length, description, and so on.

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Sales Lead object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the sales lead information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Sales Lead from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Import Your Sales Lead Contact Data

You can use the Import Management to create, update, or delete sales lead contact records.

You can import sales lead contact records using these steps:

  1. Map your source sales lead contact data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.

  2. Create the source CSV file with the sales lead contact data you want to import.

  3. Kick off an import activity.

  4. Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

To import your sales lead contact data into Oracle Applications Cloud, you must populate a .csv file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You must do the following before creating the .csv file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your objects.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

  • Identify the target object attributes that are required in the .csv file for a successful import

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

All records must be unique in the application. You can use one of these to identify records:

  • Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

  • Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new sales lead contacts or are updating sales lead contacts that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Sales Lead Contact Object

To import data successfully into Oracle Applications Cloud, your .csv file must include the required attributes. Ensure that you provide valid values for the attributes.

This table lists the required attributes for sales lead contact records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Sales Lead Contact record Updating an Existing Sales Lead Contact record

LeadOrigSystem

The code that identifies the original source system for the sales lead

If providing a value and importing a new sales lead in the same import as this lead contact association, the value must be part of a unique combination of the source system reference (LeadOrigSystemReference) and the source system code (LeadOrigSystem) in the MKT_IMP_LEADS_T table.

Conditionally required, when the lead is created in the same batch as adding a new lead contact

Not required

LeadOrigSystemReference

The ID that identifies the original source system reference for the sales lead

If providing a value and importing a new sales lead in the same import as this lead contact association, the value must be part of a unique combination of the source system reference (LeadOrigSystemReference) and the source system code (LeadOrigSystem) in the MKT_IMP_LEADS_t table.

Conditionally required, when the lead is created in the same batch as adding a new lead contact

Not required

LeadId

The unique ID for the existing lead record in the destination table

The value provided must match the value in the LEAD_ID column of the MKL_LM_LEADS table.

Conditionally required, when the lead is created in a different batch as adding a new lead contact.

Not required

PartyOrigSystem

The code that identifies the original source system for the contact

If providing a value, the combination of source system reference (PartyOrigSystemReference) and source system code (PartyOrigSystem) must exist in the columns ORIG_SYSTEM_REFERENCE and ORIG_SYSTEM of the HZ_ORIG_SYS_REFERENCES table.

Conditionally required, when you don't provide the contact's party ID (PartyId)

Conditionally required, when you don't provide the unique ID for the record (LeadTcMembersId) or the contact's party ID (PartyId)

PartyOrigSystemReference

The ID that identifies the original source system reference for the contact

If providing a value, the combination of source system reference (PartyOrigSystemReference) and source system code (PartyOrigSystem) must exist in the columns ORIG_SYSTEM_REFERENCE and ORIG_SYSTEM of the HZ_ORIG_SYS_REFERENCES table.

Conditionally required when you don't provide the contact's party ID

Conditionally required when you don't provide the unique ID for the record (LeadTcMembersId) or the contact's party ID (PartyId)

PartyId

The unique ID for the existing contact's party record in the destination table

The value provided must match the value in the PARTY_ID column of the HZ_PARTIES table.

Conditionally required when you don't provide the contact's source system and source system reference

Conditionally required when you don't provide the contact's source system and source system reference

PrimaryFlag

Specifies whether the provided contact is a primary contact on the sales lead

The value must be either Y or N.

Conditionally required, as at least one contact for a lead has this value set to Y.

Conditionally required, as at least one contact for a lead has this value set to Y.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the sales lead contact object. The page also lists attribute information like type, length, description, and so on.

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Sales Lead Contact object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the sales lead contact information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Sales Lead Contact from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Import Your Sales Lead Product Data

You can use the Import Management to create, update, or delete sales lead product records.

You can import sales lead product records using these steps:

  1. Map your source sales lead product data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.

  2. Create the source CSV file with the sales lead product data you want to import.

  3. Kick off an import activity.

  4. Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

To import your sales lead product data into Oracle Applications Cloud, you must populate a .csv file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You must do the following before creating the .csv file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your objects.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

  • Identify the target object attributes that are required in the .csv file for a successful import

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

All records must be unique in the application. You can use one of these to identify records:

  • Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

  • Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new sales lead products or are updating sales lead products that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Sales Lead Product Object

To import data successfully into Oracle Applications Cloud, your .csv file must include the required attributes. Ensure that you provide valid values for the attributes.

This table lists the required attributes for sales lead product records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Sales Lead Product record Updating an Existing Sales Lead Product record

ItemId

The unique ID for the existing sales catalog product (item) record in the destination table

The value provided must match the value in the INVENTORY_ITEM_ID column of the EGP_SYSTEM_ITEMS_B table.

Conditionally required, when you don't provide the ProductName and ProductGroupId/ProductGroupName

Conditionally required, when you don't provide the ProductName and ProductGroupId/ProductGroupName

ItemNumber

The unique ID for the existing sales catalog product (item number) record in the destination table

The value provided must match the value in the ITEM_NUMBER column of the EGP_SYSTEM_ITEMS_B table.

Conditionally required, when you don't provide the ProductName and ProductGroupId/ProductGroupName

Conditionally required, when you don't provide the ProductName and ProductGroupId/ProductGroupName

LeadNumber

Leads Public Unique Identifier value

The value provided must match the value in the LEAD_NUMBER column of the MKL_LM_LEADS table.

Conditionally required, when you don't provide the LeadId

Conditionally required, when you don't provide the LeadId

PrimaryFlag

Indicates whether the product or product group is the primary product of interest for the lead

The value must be either Y or N.

Conditionally required, as at least one product or product group for a lead has this value set to Y

Conditionally required, as at least one product or product group for a lead has this value set to Y

ProductGroupInternalName

Internal name for the sales catalog product group

The value provided must match the value in the INTERNAL_NAME column of the QSC_PROD_GROUPS_B table.

Conditionally required, when you don't provide the ProductGroupId and ItemId/ProductName

Conditionally required, when you don't provide the ProductGroupId and ItemId/ProductName

ProductGroupId

The unique ID for the existing product group record in the destination table

The value provided must match the value in the PROD_GROUP_ID column of the QSC_PROD_GROUPS_B table.

Conditionally required, when you don't provide the ProductGroupName and ItemId/ProductName

Conditionally required, when you don't provide the ProductGroupName and ItemId/ProductName

ProductGroupName

The internal name for the sales catalog product group

The value provided must match the value in the INTERNAL_NAME column of the QSC_PROD_GROUPS_B table.

Conditionally required, when you don't provide ProductGroupId and ItemId/ProductName

Conditionally required, when you don't provide ProductGroupId and ItemId/ProductName

ProductName

The internal name for the sales catalog product

The value provided must be defined for the sales catalog specified for the QSC_SALES_PRODUCTS_INVENTORY_ORG_ID profile.

Conditionally required, when you don't provide the ItemId and ProductGroupId/ProductGroupName

Conditionally required, when you don't provide the ItemId and ProductGroupId/ProductGroupName

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the sales lead product object. The page also lists attribute information like type, length, description, and so on.

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Sales Lead Product object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the sales lead product information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Sales Lead Product from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Import Your Sales Lead Resource Data

You can use the Import Management to create, update, or delete sales lead resource records.

You can import sales lead resource records using these steps:

  1. Map your source sales lead resource data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.

  2. Create the source CSV file with the sales lead resource data you want to import.

  3. Kick off an import activity.

  4. Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

To import your sales lead resource data into Oracle Applications Cloud, you must populate a .csv file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You must do the following before creating the .csv file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your objects.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

  • Identify the target object attributes that are required in the .csv file for a successful import

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

All records must be unique in the application. You can use one of these to identify records:

  • Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

  • Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new sales lead resources or are updating sales lead resources that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Sales Lead Resource Object

To import data successfully into Oracle Applications Cloud, your .csv file must include the required attributes. Ensure that you provide valid values for the attributes.

This table lists the required attributes for sales lead resource records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Sales Lead Resource record Updating an Existing Sales Lead Resource record

LeadId

The unique ID for the existing lead record in the destination table

The value provided must match the value in the LEAD_ID column of the MKL_LM_LEADS table.

Conditionally required, when you don't provide the LeadNumber

Conditionally required, when you don't provide the LeadNumber

LeadNumber

The Lead's Public Unique Identifier value

The value provided must match the value in the LEAD_NUMBER column of the MKL_LM_LEADS table.

Conditionally required, when you don't provide the LeadId

Conditionally required, when you don't provide the LeadId

LeadOrigSystem

The code that identifies the original source system for the sales lead

If providing a value and importing a new sales lead in the same import as this lead resource association, the value must be part of a unique combination of the source system reference (LeadOrigSystemReference) and the source system code (LeadOrigsystem) in the MKT_IMP_LEADS_T table.

Conditionally required, when the lead is created in the same batch as adding a new team member

Not required

LeadOrigSystemReference

The ID that identifies the original source system reference for the sales lead

If providing a value and importing a new sales lead in the same import as this lead resource association, the value must be part of a unique combination of the source system reference (LeadOrigSystemReference) and the source system code (LeadOrigSystem) in the MKT_IMP_LEADS_T table.

Conditionally required, when the lead is created in the same batch as adding a new team member

Not required

LeadResourceId

The unique ID for the existing sales team member (resource) association record in the destination table

Automatically generated by the import process

Automatically generated by the import process if creating a new record

Required

ResourceId

The unique ID for the existing resource's party record in the destination table

Provided value must match with PARTY_ID column of HZ_PARTIES table.

Conditionally required, when you don't provide the resource's source system and source system reference or the resource's user name.

Conditionally required, when you don't provide the unique ID for the record or the resource's source system and source system reference.

ResourceOrigSys

The source system code that identifies the original source system of the lead sales team members party

If providing a value, the combination of source system reference (ResourceOrigSysRef) and source system code (ResourceOrigSys) must exist in the columns ORIG_SYSTEM_REFERENCE and ORIG_SYSTEM of the HZ_ORIG_SYS_REFERENCES table.

Conditionally required, when you don't provide the resource's party ID (ResourceId)

Conditionally required, when you don't provide the unique ID for the record (LeadResourceId) or the resource's party ID (ResourceId)

ResourceOrigSysRef

The ID that identifies the lead sales team member's party in your legacy or external system

If providing a value, the combination of source system reference (ResourceOrigSysRef) and source system code (ResourceOrigSys) must exist in the columns ORIG_SYSTEM_REFERENCE and ORIG_SYSTEM of the HZ_ORIG_SYS_REFERENCES table.

Conditionally required, when you don't provide the resource's party ID (ResourceId)

Conditionally required, when you don't provide the unique ID for the record (LeadResourceId) or the resource's party ID (ResourceId)

UserName

The resources application user name.

No validation

Conditionally required, when you don't provide the resource's source system and source system reference or the resource's unique ID

Not required

PrimaryFlag

Indicates whether the resource is the Owner of the lead

The value must be either Y or N.

Conditionally required, as at least one contact for a lead has this value set to Y

Conditionally required, as at least one contact for a lead has this value set to Y

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the sales lead resource object. The page also lists attribute information like type, length, description, and so on.

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Sales Lead Resource object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the sales lead resource information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Sales Lead Resource from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Lead Follow Up

The lead life cycle includes an automated process that captures leads and then prioritizes them for sales engagement through a scoring and ranking process. Leads are distributed to appropriate sales resources for further lead qualification, follow-up, and conversion. A sales lead cycle ends when salespeople convert a lead to an opportunity or when they retire a lead. A lead is retired if no possibility exists for converting the lead to an opportunity.

Lead Life Cycle

Leads are automatically monitored for sales representative acceptance. Unaccepted or rejected leads are reassigned as appropriate. The quality of the lead is continuously reviewed and adjusted by the lead owner at different stages of the lead life cycle. The lead owner can be a marketing resource or a sales resource, depending at what stage the lead is at in its life cycle. The lead life cycle is captured in the following sections:

  • Lead Generation

  • Lead Qualification

  • Lead Distribution

  • Lead Assessment

  • Lead Conversion

Lead Generation

Leads are generated and captured from many different sources, such as:

  • Campaign responses

  • Third-party lead sources

Flexible lead import, customer and contact creation, and deduplication ensure that sales lead generation efforts are optimized. For example, the lead import process checks whether leads represent new or existing customers. For new customers, data must be created for the lead. If the lead is an existing customer, then part of the lead import process checks to ensure customer and lead information isn't duplicated.

Lead Qualification

Marketing departments help with the lead qualification process to ensure that only qualified leads are handed over to sales. Leads are typically ranked as Hot, Warm, or Cool. Leads are further qualified by the use of company-specific standard questions to score a lead. Lead scores are numeric values typically ranging from 1 to 100, in which a high score represents high quality.

It isn't good practice to let stale leads build up. Standardized criteria for lead qualification ensure that quality leads reach the sales representative and help maximize the conversion rate from leads to opportunities. For example, your organization has criteria and processes for ensuring that leads are either developed or retired within 30 days. When the lead age is greater than 30 days and the rank is Warm, Marketing reassigns the leads for follow-up by an internal telemarketing group. If leads can't be qualified or further developed to revenue opportunities, then rejected leads are reassigned or manually set to retired.

Lead Distribution

As the qualification of leads progresses into real potential prospects, assignment manager uses expression-based rules to associate one or more internal sales representatives with each lead. If the lead is associated with either a sales prospect or a sales account, then assignment manager uses territory definitions to associate (typically one) internal territory with each lead. The sales representative newly assigned to the lead can be related to the lead record directly through the lead team or indirectly through a territory associated with the lead. The sales representatives can view and update those leads assigned to them in the lead work area and can claim ownership of the lead by accepting the lead.

Other assigned resources can view and update the lead, but they can't make themselves the owners. If a sales prospect changes to a sales account by adding an address, assignment manager is automatically called during the next automated assignment cycle. Depending on the assignment logic, the lead can be reassigned to a different territory or sales resource. If the assigned sales representative takes no action on a lead for several days, then the lead can be manually reassigned to another sales representative.

Lead Assessment

Sales representatives must evaluate the quality of the information that they have received for the lead. They determine whether the details are sufficient to reach out to the customer and assess whether a lead is worth pursuing with the help of preconfigured assessment templates. Assessment templates help qualify the lead by:

  • Reviewing the content shared with the customer during a campaign

  • Framing the lead in the context of the campaign

  • Ensuring the salesperson understands the information sent to the customer

You use the lead assessment feature to assess leads. Predefined questions help determine the likelihood of the lead being accepted by Sales. For example, you're a sales representative and you ask the customer a series of questions created by Marketing and Sales to assess the quality of the lead. You record the answer of each question and the lead assessment tool automatically factors the answer into the assessment score of the lead. At the end of the call, you note that the assessment lead score is high, so you request that the lead is assigned to the direct sales team. If the lead score was low, then you might want to retire the lead. If the lead needs qualifying, then you can decide to leave it in your list of leads for follow-up. Finally, if the lead is good, but the potential revenue opportunity is less than a predetermined monetary amount, for example, twenty-five thousand dollars, then you can convert the lead to an opportunity to pursue as part of the sales cycle.

Lead Conversion

After establishing that the lead has potential, the sales representative can convert the lead to an opportunity. You can schedule meetings and presentations with your lead contact to move the opportunity along the sales pipeline. To track the progress of the lead, you can capture contact notes and associate them with the contact and opportunity.

Note: Administrators can write a validation rule to check if there's more than one lead attached to an opportunity. For example, using a Groovy script, you can restrict the creation of another opportunity from a lead. To learn more about writing validation rules and scripts, see the Groovy Tips and Techniques chapter in the Groovy Scripting Reference guide, and the Groovy Scripts chapter in the Configuring Applications Using Application Composer guide.

As the lead progresses through its life cycle, decisions to retire the lead are based on reasons such as:

  • You can't verify the customer and lead details.

  • The customer isn't interested in pursuing the lead any further.

Differences Between Response, Lead, and Opportunity

This table describes the main differences between a response, a lead, and an opportunity.

Response Lead Opportunity

A response is an interaction initiated by the customer in response to a marketing stimulus. Every outbound sales activity is a sales stimulus.

A lead is an inquiry, referral, or other information, obtained through a sales campaigns, or other means that identifies:

  • Potential contact or prospect

  • Specific purchase interest

You can create a lead if the specific purchase interest isn't known at the time. However, to qualify a lead you must record a primary purchase interest.

An opportunity is a pending sale of a product or service that can be forecasted and tracked using summary data such as:

  • Potential revenue

  • Sales stage

  • Win probability

  • Expected close date

Responses are created from interest recorded in response to sales activities. Responses include:

  • Providing answers to phone survey questions

  • Subscribing to a list

  • Replying to an email response form request

As interest for the product or service matures, responses are elevated as leads.

Leads are mostly created by automated lead capture or lead import processes which periodically create qualified responses as sales leads.

Leads are sometimes created from the response data of a contact or prospect who has expressed a need or interest in a product or service offered by the business.

Opportunities are created by sales administrators when they have identified a qualified lead with a potential revenue opportunity. Leads are converted to opportunities when significant sales investment is foreseen to close the deal.

A salesperson can create opportunities from scratch, without previously having a response or lead created.

Responses aren't included as part of the sales forecast.

Leads aren't included as part of the sales forecast.

Inclusion of opportunities in the sales forecast is at the discretion of the sales administrator. However, not all opportunities are included and the decision to include them may depend on your company's requirements.

Use lead actions to manage leads. This topic provides a brief description of the actions that you perform on a lead. Lead actions are generally grouped into these categories:

  • Standard create, edit, delete, and update functions such as performing a mass update

  • Ranking, scoring, and qualifying actions to assist in prioritizing leads

  • Accepting, rejecting, reassigning, and retiring actions to ensure leads are in the right queue for pursuing

  • Converting leads to opportunities to continue sales pursuits and include in sales forecasting

The ability to perform each action depends on:

  • Privileges assigned to your role

  • Access level as a lead sales team member

  • Current status of the lead

Lead Actions

Here are some of the actions you perform to manage leads.

Action Description

Mass Update

Performs a mass update of specific attributes and user-defined attributes from the Leads Overview work area when selecting multiple records.

Rank

Submits the Request Sales Lead Assignments process to automatically assign a lead rank based on predefined rules specified in the Assignment Rule for Ranking Leads profile option. A rank represents the priority of the lead, such as Hot, Medium, and Cool.

Score

Submits the Request Sales Lead Assignments process to automatically assign a lead score based on predefined rules specified in the Assignment Rule for Scoring Leads profile option.

Lead assignment score is different from qualification and assessment scores. A lead score can be used as a source for predefined rules that automatically assign lead rank, qualification status, territories, and resources.

Qualify

Updates the lead status to Qualified, bypassing the automated sales lead classification process.

Reassign

Provides choices for when the sales lead assignment process evaluates the lead to reassign sales team members and territories to the lead:

  • Automatic assignment

    Lead is selected for reassignment and is reassigned when the Request Sales Lead Assignments process next runs using the Reassign process selection criteria.

  • Immediate automatic assignment

    Immediately runs the Request Sales Lead Assignments process, reevaluating, and reassigning per the process.

  • Manual assignment

    You can select an owner to assign to the lead from a list of eligible resources.

A lead must have a Qualified or Unqualified status to be reassigned.

Note: You can send a notification when a Lead is assigned to a new owner. See the section Sample Groovy Scripts for Notifications in the Configure Notifications chapter of the Implementing Sales guide for more information.

Retire

Updates the lead status to a retired lead indicating the lead is no longer one that needs pursuing.

Reject

Removes you as the lead owner. The accepted indicator and assignment status are also updated to reflect that the lead is no longer accepted. The lead is eligible for reassignment when:

  • The next scheduled Sales Lead Processing Activity submits the Request Sales Lead Assignments process

  • The lead meets the processing activity's selection criteria

  • The previous lead owner is excluded when assigning team resources

The reject reason, and the number of times the lead is rejected, is available when searching leads. This information is displayed in the Overview page for analysis and to provide possible indicators that the lead should be retired.

Accept

Updates the lead with you as the owner. The Request Sales Lead Assignments process assigns sales team territories and resources based on predefined rules. The rules are specified in the Assignment Rule for Ranking Leads profile option.

Convert to Opportunity

Creates an opportunity based on lead information. The lead status is updated to converted.

The status of a lead is primarily determined by a user performing an action on a lead, or upon successful completion of the lead qualification activity. Once leads have been assigned to lead qualifiers or related sales roles, lead follow-up activities begin. As specific actions are performed on a lead, the status of the lead changes accordingly.

Lead Status

This table describes the statuses of leads.

Status Description

Unqualified

A lead with a status of unqualified signifies that the lead requires additional information and qualification activities by the lead team. Unqualified is the default status assigned to all newly created leads.

Qualified

A qualified lead signifies that the lead is ready for sales attention. The status can be updated to qualified by either the user selecting the Qualify action or upon successful completion of the qualification processing activity. Leads can have a status of qualified based on many factors including the status of the budget and the time frame of the project.

Converted

When a lead is converted to an opportunity, then the status is set to Converted.

Retired

The status of a lead is updated to Retired when a user selects the Retire action. A lead is retired when:

  • There's no likelihood of the lead being converted to an opportunity

  • A lead is no longer followed up by Sales

  • A lead isn't evaluated by Marketing over a certain period of time

A retired lead can't be converted to an opportunity. Marketing users can review retired leads and then delete them as required.

A lead's life cycle ends either when a lead is converted to a sales opportunity, or when the lead is retired. Conversion to an opportunity stage allows the sales representative to pursue the account in the sales cycle. After establishing that the lead has potential, the sales representative converts the lead to an opportunity. Contact is established and meetings and presentations are scheduled to move the opportunity along the sales pipeline.

To convert a lead to an opportunity depends on the privileges assigned to your role, your access level as a lead sales team member, and the current status of the lead. You can convert a lead to an opportunity from the Actions menu by selecting Convert. This action creates an opportunity based on lead information. When a lead is converted to an opportunity, the lead status is set to Converted.

Leads to Opportunities Conversion

You convert a lead to an opportunity when the lead is ready for further processing along the sales cycle. Once the conversion is successfully completed, you can review the newly created opportunity using the opportunities UI. During your review, you might want to retain only a select few lead product lines to pursue as opportunity revenue line items. Since the conversion process automatically creates revenue lines from all lead lines, you can remove unwanted revenue lines from the opportunities UI. You can, at a later stage, create another opportunity from the removed lead revenue lines by converting the lead to an opportunity again. You can then decide to keep only those revenue lines that you want on the newly created opportunity.

When you convert a lead to an opportunity, the following rules may apply depending on the setup criteria for your company:

  • The person converting the lead becomes the primary sales team member for the opportunity.

  • The customer reference on the original lead is maintained for the opportunity.

  • The associated lead team members are copied with the same primary team member.

  • The newly created opportunity is assigned to the appropriate sales territories.

You can view opportunities associated with leads in the leads UI. If you don't see the converted lead in your list of opportunities, this means that the opportunity is assigned to a different territory.

Converting a lead to an opportunity lets you pursue the account in the sales cycle. You can choose whether you want to be redirected immediately to the opportunity page after the successful conversion. This reduces the time spent going to the Opportunities subtab on the Lead and finding the right opportunity to open.

To get redirected to the edit opportunity page depends on the privileges assigned to your role, your access level as a lead sales team member, and whether your sales administrator has configured the Redirect to Opportunity After Conversion check box on the Convert Lead page in Application Composer. You can convert a lead to an opportunity from the Actions menu by selecting Convert. An error message displays if you don't have the required privilege to convert the lead. You will be returned to the lead details page or the lead list page from where you started the lead conversion action.

Note: The Redirect to Opportunity After Conversion check box is deselected by default and is available only for single lead conversions. It isn't available on the Mass Convert Layout Pages for Leads.

How to Redirect to Opportunities Page After Conversion

You convert a lead to an opportunity when the lead is ready for further processing along the sales cycle. Here's how to select whether you want to be redirected immediately to the opportunity page after a successful lead to opportunity conversion.

  1. Navigate to the Leads UI and select the lead you want to convert to an opportunity.

  2. From the Actions drop-down list, select Convert.

  3. From the Convert Leads dialog, select the Redirect to Opportunity After Conversion check box. Its

  4. Click Submit.

Once the conversion is successfully completed, you're brought immediately to the opportunities UI where you can review and edit the newly created opportunity.

You can apply changes to several fields on multiple leads at once using the mass update feature. For example, you can update the rank of multiple leads at the same time without having to go into each individual record.

Among the fields that you can update are:

  • Account

  • Budget Amount

  • Budget Status

  • Campaign

  • Currency

  • Customer Need

  • Deal Size

  • Decision Maker Identified

  • Description

  • Primary Contact

  • Primary Product

  • Rank

  • Sales Channel

  • Source

  • Time Frame

Note: Your administrator must enable this feature before it's available in the application.

Steps to Apply Mass Update

Here's how to update several fields on multiple leads at once:

  1. Navigate to the Leads landing page.

  2. Search for the records you want to update.

  3. Click Update from the Actions menu.

  4. Select the records that you want to update and click the Update button.

  5. Select the fields and assign or enter values for them. Keep in mind:

    • If you want to update a field that has a parent field, then the value of the parent field must be the same across all child records selected for mass update.

    • You can't apply mass update to conditionally updatable fields.

  6. When you're done making updates click Submit.

This topic explains how the security reference implementation provided by Oracle determines who can access what lead information in your sales organization. Qualified leads are assigned to a sales team based on sales territories. Unqualified leads are assigned to individual lead qualifiers either manually or based on rules defined in the assignment manager application. Whether or not you can access a particular lead depends on your membership in the resource and territory hierarchies.

You can access a lead if the following conditions apply:

  • You're the lead owner.

  • The lead owner or sales team member is your direct or indirect report in the resource hierarchy.

  • You're a member of the lead sales team.

    Resources in the management hierarchy of a newly added lead sales team member have the same level of access to the sales leads as the team member.

  • You're the owner or you're a member of the territory assigned to the lead.

  • You're the owner or member of an ancestor territory of the territory assigned to the lead.

Note: Your administrator can provide view only access to users by creating a custom role and adding new data security for the sales lead with all values set to view only privileges. See the Data Sharing Mechanisms and Object Visibility chapter of the Oracle CX Securing CX Sales and B2B Service guide on Oracle Help Center (https://docs.oracle.com).

The flowchart illustrates some of the different ways you can gain access to a lead:

  • Named agents in the diagram (A, B, and C) can access the lead.

  • Unnamed agents (highlighted in yellow) can't access the lead.

  • Sales managers can access the lead because a salesperson in their management chain has access.

Here's an example flowchart that shows who in a sales hierarchy can access a sales lead. Access using accounts isn't shown.

How data security policies determine access to
leads.
  • Agent A can access the lead because agent A created it. When you create a lead, you're the initial owner.

  • Agent B can access the lead because agent B is on the sales team.

  • Agent C can access the lead because agent C is the owner of the NW territory.

  • Sales managers who are higher up in the management chain can also see the lead because access is provided through the resource hierarchy. The manager of agent C can access the lead information, but colleagues of agent C don't have access to the lead.

Special Access

Not all access is affected by the management hierarchy and membership in sales teams or territories. For example, special access includes:

  • Administrators: Administrators get access to leads and other objects. This access is based on their privileges, regardless of where the administrators are in the management hierarchy. Administrators don't have to be on the sales team or members of territories.

  • Deal Registration: Salespeople assigned to a deal registration retain access even if they're moved to another deal registration.

A market is typically organized into territories that include customers and prospects. Marketing is closely aligned with sales, and marketing activities are launched to generate leads and maintain the strength of the sales pipeline. This topic explains lead ownership and sales team resources.

When the lead doesn't have any owner, the sales representative can accept the lead which makes him or her the lead owner. All resources who are given access to leads get full access. Full access level allows the user to update the sales lead team by adding or removing individual resources. Hence, territory resources, sales team members and lead owner and resources in their hierarchy, all get full access. Territory team members inherit the access level of the territory. All members of sales territories assigned to the lead have full access to the lead. Ancestor territory owners of all sales territories assigned to the lead also have full access to the lead. Resources who access leads have different roles such as:

  • Operations

    Support an automated process to capture leads, prioritize leads for sales engagement, and distribute the leads to appropriate sales or territory team resources.

  • Marketing and lead qualifiers

    Monitor leads, reassign leads, and continually review and adjust the lead quality.

  • Sales and territory teams

    Enable lead qualification, perform follow-up lead activities, and convert leads to opportunities.

This topic includes these sections:

  • Lead, Sales, and Territory Resources

  • Assignment of Leads to Marketing and Sales Resources

  • Sales Resource Role

Lead, Sales, and Territory Resources

Sales resources are organized into flexible teams and are associated with the sales territories. These sales territories are then assigned to customers, leads, and opportunities to carry out the sales process. The lead follow-up team can include a lead team made up of individual sales resources who are predominantly active during the lead qualification stage. All sales resources who are assigned to the territory team can view and follow up the lead.

Assignment of Leads to Marketing and Sales Resources

Qualified leads are assigned to a sales team based on sales territories. Unqualified leads are assigned to individual lead qualifiers either manually or based on rules defined in the assignment manager engine. Users can be assigned to a lead in one of several ways:

  • Ownership through lead creation

  • Territory-based lead assignment

  • Rule-based sales team member assignment

  • Manual selection of resources

Sales Resource Role

Here are some of the activities performed by sales resources.

  • Review quality leads that are augmented with sales collateral, marketing content, customer contact interactions, and references.

  • Qualify and assess the lead quality further with the help of user-defined or company-defined assessment templates.

  • Use the resource drop-down list to manually select a resource to add to the team.

    Include a description to indicate what role the resource has on the sales team. Many sales team members can access each lead, and each team member is identified as either an internal (sales force), or an external (channel partner sales force) resource. Each sales team member can be associated with a specific resource role to indicate what capacity the member has on the lead.

  • Add additional contacts and products to the lead as the lead moves further down the sales cycle.

A sales lead team is made up of assigned territories and individual team members. This topic provides examples to illustrate some of the features available for the sales lead team:

  • Automate assignment of individual resources to sales lead team

  • Add ad hoc members to sales lead team

  • Update access rights based on the resource

  • Change the lead owner

Automate Assignment of Individual Resources to Sales Lead Team

The sales lead team for your company wants to add a support person to the lead. Typically, support people aren't part of any sales territory. Use the Manage Sales Lead Assignment Rules task to set up a rule set for the category, Sales Lead Resource Rule Category. For example, assign support team members as individual resources based on rules which match the lead product with specific support team members.

Add Ad Hoc Members to Sales Lead Team

Generally, sales team resources are automatically assigned to leads based on configured assignment rules. The following scenarios provide examples of when you may want to manually add additional team members to assist with the lead.

  • The lead owner, who has full access to your company lead, wants to add one of his company's contractual experts to his team to help pursue the lead. The lead owner manually accesses the resource drop-down list and selects the ad hoc resource that he wants to add to his team.

  • When pursuing a lead for an insurance policy, the customer contact requests a unique and complex combination of policy components that require a review from an expert in the company. The lead owner adds the expert resource to the lead with full access. Now, the expert resource can update the lead with valid combinations of products and services, and, if required, add more team members to the team.

  • A salesperson is pursuing a lead that requires the export of products outside the country. He wants to ensure there are no legal issues with exporting the products. The salesperson adds a member of their company's legal team to the lead to review the details before contacting the customer again.

Update Access Rights Based on the Resource

When a resource is added to the sales lead team through rule-based assignment, a profile option determines the member's default access level. Resources in the management hierarchy of a newly added team member have the same level of access to the sales leads as the team member.

All members of the sales territories assigned to the lead have full access to the lead. Owners of ancestor territories of all sales territories assigned to the lead also have full access to the lead.

Change the Lead Owner

Only the lead owner, or the resources in the management hierarchy of the lead owner, can change the ownership of the lead.

Qualification

The lead qualification process can either be performed by internal marketing or internal sales groups. This topic provides a brief overview of what constitutes a qualified lead. Qualifying leads is an important first step in bringing the sales lead to a conclusion. At the end of the lead qualification process, you can classify the lead as a qualified lead that's ready for conversion to an opportunity. Or you can retire the lead if the purchase interest for the lead can't be validated. What constitutes a qualified lead varies from company to company.

Basic Lead Qualification

In some companies, basic lead qualification data is gathered by lead qualifiers and contains data such as:

  • Customer need

  • Urgency or time frame for the project

  • Budget considerations such as available amount and status

The scheduled process that determines lead qualification status also takes into consideration basic lead data.

Additional Lead Qualification

In other companies, the lead qualifier or salesperson uses a lead qualification questionnaire as part of the qualification process. Based on the answers received, he or she can decide to manually set the lead to a Qualified status using the lead actions menu. Your application administrator assigns the questionnaire to your Lead Qualification Template profile. The answers entered are assessed using a weighted scoring model with instant feedback available as a scoring status bar in the UI.

Lead qualification helps you in the lead follow-up process. Assess the lead quality and lead conversion potential by using the preconfigured qualification templates.

Lead qualification is part of the lead follow-up activity where you further nurture the lead in order to qualify it. Your administrator must set the Advanced Lead Qualification Enabled profile option after the qualification templates are created. This action specifies the qualification template to display in the Edit Lead UI to assist with evaluating the lead.

You can conduct a lead qualification, view completed lead qualifications, and view the responses to the questions posed in the qualification template. Qualification templates enable you to analyze the lead and suggest the appropriate next steps based on the overall assessment score and feedback for the lead.

Edit a New Lead Qualification

  1. From the Navigator, click Leads.

  2. In the list of leads, click on a lead to edit it. The Edit Lead page appears.

  3. Click the Qualification tab to open the default qualification template.

  4. Fill out and complete the lead qualification template.

If there are multiple qualification templates associated with the lead, then you can choose to select a different qualification by clicking Replace Qualification.

Overview of Lead Qualification Templates

When you create a lead, you can qualify the lead by leveraging the many templates provided by your sales organization. This means you can evaluate various aspects of the lead which can subsequently help you sell more by converting the leads in less time.

Qualification Templates

After you create the lead, go to the Qualifications tab to view and complete the recommended qualification template created for you by your organization. If there are multiple templates associated with the lead, select one by clicking Replace Qualification. Any responses for the current qualification will be reset and can't be restored. You can choose to cancel the operation and use the current qualification template, or you can choose to continue.

If you continue, the qualification UI is refreshed to display the questions from the template you selected. Start entering responses to the questions and track the updates from the Qualification status fields on the page. Statuses toggle between: Not Started, In Progress, and Completed. You can also include other status values such as the number of questions answered, last updated date, and name of the template. Track the total score by summing up the weighted answers and display a graphical circular format of the score.

Perform Multiple Lead Qualifications Using the Same Template

From time to time, you might want to requalify your sales lead information and perform multiple qualifications for leads using the same qualification template. To do this, your administrator must set the profile option Enable Multiple Assessments Per Qualification Template to Yes at the site level.

From the Edit Qualification page click Add Qualification and then select the template you want from the available templates for your sales lead. If you add an additional qualification using the same qualification template, the application automatically generates a qualification name using the qualification template name plus a counter suffix. For example, if you have an existing qualification for a lead named Lead Qualification V1, then if you add another qualification using the same template, the new qualification name is displayed as Lead Qualification V2. You can edit this name to suit your own requirements.

When all questions are answered, the qualification is set to Complete status and continues to be available for edit. You can view all ongoing or historical qualifications, scores, statuses, and qualification template names. Use the Delete and Submit features only if the buttons are enabled by your administrator using Page Composer. You can delete a qualification that's no longer required or if it was created by mistake as long as it hasn't been submitted. The Submit button, if enabled, becomes available only when you have entered responses for all questions. Submit isn't available on the single lead qualification page. You can't edit the lead qualification once the status is set to Submitted but you can continue to view it.

Perform Multiple Lead Qualification

Before you begin, ensure that your administrator has set the Enable Multiple Assessments Per Qualification Template (MOW_MULTIPLE_QUALIFICATIONS_ENABLED) profile option to Yes. You must also have Full or Edit access on a lead to perform multiple qualifications and update existing qualifications for leads using the same qualification template. With View Only access, you can view qualifications but not update them.

Here's how to perform multiple lead qualifications using the same qualification template:

  1. From the Navigator, click Leads.

  2. In the list of leads, select a lead to edit it. The Edit Lead page appears.

  3. Click the Qualification tab to open the Edit Qualification page.

    If existing qualifications are available for the selected lead, they're listed here.

  4. Click Add Qualification. The Add Qualification dialog appears.

  5. From the Template drop-down list, select the qualification template previously chosen for the selected lead qualification.

  6. Click Save and Continue.

  7. Select the appropriate responses to all the questions.

  8. Click Submit and then click Yes from the confirmation dialog box.

    Once the qualification has a status of Submitted, it can't be revised.

This topic explains the lead qualification process and provides examples of the different methods used for qualifying leads.

Lead Qualification Process

Lead quality is assessed as soon as a lead is generated and is mainly based on:

  • The characteristics of the customer contact on the lead

  • The type of response which caused the lead to be generated

  • The type of sales campaign that the lead may be associated with

Leads are enriched further, typically by means of prequalification telemarketing activities performed by internal marketing, internal sales groups, or external third-parties. Qualification data is added to the lead such as:

  • Customer need

  • Urgency or time frame for the project

  • Budget considerations such as available amount and status

At the end of this process, the lead is either:

  • Classified as a qualified lead which is ready for conversion to a sale

  • Retired if purchase interest for the lead can't be validated

The following scenarios illustrate some of the lead qualification processes.

Rule-Based Lead Qualification

The rule-based lead qualification process requires that the value of the Lead Status attribute be set to Qualified if qualification rules evaluate to a positive answer. For example, consider the sample rule:

Sample rule-based lead qualification rule

If this rule evaluates to TRUE, the value of Lead Status is set to Qualified.

Internal Marketing Qualification

Internal lead qualifiers or inside salespeople conduct phone conversations to gather qualification data about leads. They can use qualification templates to define consistent and specific qualification criteria for similar leads. The qualification questions are tailored to a specific product, industry, and source of the lead.

Before updating the lead status to qualified, the lead must have a valid primary product associated with it. Users can select multiple leads and select Qualify from the Actions list. Leads meeting the requirements for lead qualification are processed.

As the qualification data is gathered using the leads management user interface, the lead qualifier or salesperson can decide to manually set the lead to Qualified status. In some companies, the lead qualification data gathered by lead qualifiers is considered in the scheduled automated lead process. For example, the assignment manager engine can calculate lead score or lead rank, as well as assign sales team territories. For such companies, a simple rule to move leads to a Qualified status when the lead score reaches a specific threshold is sufficient.

A lead can be qualified when the basic attributes of the lead indicate interest in the purchase of a product. For example, basic attributes might include:

  • Contact attended a product event

  • Budget is approved

  • Purchase time frame is less than a year

The Additional Qualification tab displays the qualification template with questions where you can enter the answers on the same page. Most of the data required to qualify the lead is available from the Basic Qualification area of the Lead details page. Supporting data is included in the contextual area for easy reference.

Internal Sales Group Qualification

Leads are generated and captured from many different sources. Leads are created when customers are created. Leads are also generated from leads that already exist. After salespeople accept the generated leads, they can evaluate the quality of the information received for the lead. They determine if the details are sufficient to reach out to the customer and assess whether a lead is worth pursuing with the help of predefined assessment templates. If they can establish that the lead has potential and can be marked as qualified, they can then convert the lead to an opportunity. Contact is established and meetings and presentations are scheduled to move the opportunity along the sales pipeline.

External Third-Party Qualification

External third-party qualification involves using input from a third-party source to qualify leads. For example, your company has obtained a list of contacts that purchased a car in the last 90 days. You have hired a telemarketing company to call each contact to determine if there is interest in your company's auto security products. The third-party telemarketer provides weekly files of potential contacts who are interested in your products. Using the Import Management framework and qualification rules configured using the assignment manager engine, the interactions resulting from the telemarketer's activities are imported as leads. The marketing operations manager schedules the rule-based qualification process to occur as soon as the enriched lead data is imported to the lead management application. If the rules evaluation is successful, the result sets the lead status as Qualified.

Lead Adaptive Intelligent (AI) Score

You can use the AI Lead Score field to indicate the lead conversion probability of a sales lead being converted to an opportunity. Lead scores are numeric values typically ranging from 1 to 100 and where the higher value represents a high conversion probability. At a glance, the AI Leads Score helps you to prioritize and focus on those leads that are more likely to get converted to opportunities.

What happens when the AI lead score changes ?

The AI Lead Score is associated with the AI Update Who Columns Threshold (ORA_ZCA_AI_UPDATE_WHO_THRESHOLD) profile option value. The profile option is set to a predefined value of 5 which represents the percentage threshold value of a potential change in the Adaptive Intelligent (AI) lead score based on data from Oracle Adaptive Intelligent Apps for Customer Experience. When the AI Lead Score changes, and if your administrator has exposed the AI Lead Score field, then the latest score value is displayed on the Lead details page. In the Workspace UI, the latest value of the AI lead score is available only if the recent change exceeds or equals the percentage threshold value specified in the AI Update Who Columns Threshold profile option.

When a change to the AI Lead Score exceeds or equals the percentage threshold value, the Last Updated Date field gets updated for the lead. This ensures that the updated records are included in the next run of the Adaptive Search indexing process.

Use Slack for Leads

View Your Leads in Slack

Slack is a team communication tool that facilitates synchronous communication across different devices. Regardless of whether your team is co-located or distributed, Slack provides an effective communication channel that's easy to use. Let's say you're traveling and you would like to quickly view a list of the current leads owned by you. You can do this on Slack using any device, without signing in to your sales application.

Note: The only criterion is that your administrator has set up the integration of Slack with your sales application.

You can view the first five leads owned by you. These first five leads are selected from only the qualified and unqualified leads owned by you in the last three months.

To view your first five leads in the last three months on Slack:

  1. Navigate to your workspace in Slack.

  2. Select one of the following:

    • Any public channel in the Slack workspace

    • Slackbot

    • Oracle Sales Slack app: This refers to the app that your administrator has created in Slack for integrating with your sales application.

    Note: Due to security restrictions, you can't view your leads if you select the following:
    • Private channels

    • Any user under direct messages

  3. Enter the following command at the command line: /ec-my-leads

  4. Press Enter.

    The first five leads owned by you in the last three months are displayed in Slack. The following fields are displayed for each lead:

    • Lead Name

    • Lead Status

    • Account Name or Customer Party Name

    • Description

    • Campaign Name

    • Rank

Note: Every sales representative who executes the /ec-my-leads command can see only the leads owned by him or her. You can't view the leads owned by other sales representatives. Moreover, your leads are only visible to you and not to any other user.

FAQs for Leads

This section contains some frequently asked questions (FAQs) for Leads. Scroll or search to find answers to common questions.

How can I quickly enter and search address details for leads?

Lead address fields such as Country, City, State, and Postal Code have type-ahead and autocomplete features based on the values you start to enter. For example, when you begin to enter one of these fields, the application either displays the matching filter names and makes it possible for you to select filter values or the associated values are automatically inserted for you in the appropriate fields.

Use letter keys on your keyboard to display values within the Country field. You can also filter by City, State, and Postal Code fields based on the selected country, and you can filter by City and Postal Codes, based on the state selected.

What leads are displayed when I select My Open Leads?

Selecting the My Open Leads list in the Leads work area displays a list of all of the qualified and unqualified leads where you're listed as the lead owner and that were created within the last 90 days, or another number of days specified by the administrator in a system profile. You are automatically the lead owner if you create the lead or you can be designated as the owner by an application administrator.

Who can view the record sets for leads for saved searches?

The different record sets provided in the Saved Searches window restrict your saved searches to different sets of leads.

The following table lists and describes the record sets for leads. Not all record sets are available to all users. For example, the record sets involving subordinates are available only to managers.

Tip: To improve saved search performance, restrict your saved searches to smaller record sets. For example, rather than searching all the records you can see, search all the records in your territory hierarchy. Or restrict your searches to a smaller geographical area. For example, search all the leads in one state instead of the whole country.
Record Set Name Description

I own

Leads you own, including those leads you created or where ownership is assigned to you.

I am on the team

Leads where you're on the lead team. You are on the lead team if you're the lead owner or were added as a member by another team member.

My territory

Leads in your sales territories.

My subordinates own

Leads where you or your subordinates are on the lead team.

My territory hierarchy

Leads in your sales territories and all of their subordinate territories in the sales territory hierarchy.

All records I can see

Leads that you can view based on your lead team membership, sales territory assignments, your position in the organization, and security permissions.

Why do I see two Primary Product options for Advanced Search on Leads?

Two Primary Product search options are available in the Lead Advanced Search dialog. While both options point to the same Primary Product field, the difference is that when selected, one option performs a List of Values search and the other option performs a Text search.

The first option is the default List of Values search (as Primary Product is a Dynamic Choice List (DCL) field) and the second Primary Product search option lets you use a text search with improved search results performance.

By default, the leads pages display only names of accounts and contacts that already exist in the application. If you want to create leads for new accounts or add new contacts, then you must create the appropriate account and contact records before creating the lead.

If your business uses net new leads where contact and account values are entered manually using free form text fields, then your administrator can make the New Account and New Contact fields available on the Leads UI through Application Composer. These fields are hidden by default so to use them for your new leads, your administrator must manually unhide these fields.

What happens when I enter a last name with two parts?

During lead creation, if you enter a value for Last Name with two parts that aren't separated by a hyphen, the application removes the first part of the last name and moves the value to the Middle Name.

A customer reference is based on the customer industry and associated lead product or product group related to the specific lead. For example, a customer reference displays for your lead if a customer has purchased a similar product or service. You can leverage the reference details for effective lead follow-up.

The leads UI is designed to ensure that you're productive and can readily access related lead information with as few clicks as possible. Supporting data related to each lead is included in the contextual area for easy reference. It includes references to all open leads and open opportunities for the lead customer, as well as supporting collateral. This information is useful to the lead sales team to facilitate an effective lead follow-up.

Can I create more than one opportunity from a single lead?

Yes, you can convert the same lead into another opportunity and then delete unwanted product lines. For example, during your review of an opportunity, you decide you want to retain only a select few of the lead product lines to pursue as opportunity revenue. Since the conversion process automatically creates the product lines from all lead lines, you can remove unwanted product lines from the opportunity details page. You can, at a later stage, create another opportunity from the removed lead product lines by converting the lead to an opportunity again. You can then decide to keep only those product lines that you want on the newly created opportunity.

How can I check for duplicate leads?

As a sales representative you want to know if your leads for new contacts or accounts have any duplicates in the application. You can manually check for leads duplicates from the edit leads page. Select the lead that you want to check and from the Actions menu, select Duplicate Check. Duplicate check can only be run on new (non-existing) contacts and accounts.

A message is displayed if no duplicates are found for new contacts or accounts. If potential duplicates exist, the Resolve Duplicates page is displayed for the contact or account where you can select the appropriate contact or account to resolve any duplicates.

Why did the deal size change?

The deal size is automatically determined by the products entered for the lead. When you add or remove products for a lead the deal size is recalculated. You can override the calculated amount after all products are entered. For example, if the lead is eligible for a discount, you can manually change the total of the deal size to apply the discount. However, the application overrides the deal size total if you add or remove a product from the lead after having manually adjusted the deal size. In this case, you have to reapply the manual change.

Can I perform a mass update for leads of different business units?

You can't perform a mass update of modified values for leads that apply to different business units. A dialog box is displayed if the selected leads belong to different business units which don't share the same reference data sets. You must remove the set-enabled attribute for the offending leads and perform the mass update only for leads with business units containing the same reference data sets. For more information on reference data sets, see the topic How Business Units Work with Reference Data Sets. Also, consult the online help, using keywords "reference data".

Why can't I see the lead source channel from the lead details page?

The Source field value is removed from the lead details each time the lead business unit (BU) is changed. You enter your source field value based on a BU and set ID lookup types when you create a lead. Since multiple business units can exist, the set ID lookups are reset each time a BU is changed to reflect the values specific for the changed business unit. For more information about lead business units and set ID lookups, see the Multiple Business Units in Leads section of the Implementing Sales guide.

Where can I find the primary phone number for my lead contact?

The primary phone number for you contact is available from the Contacts overview page. The phone number displayed is the same phone number that's displayed in the Contact Phone field in the Edit Lead summary page.

Why did I receive an error when I convert a lead that has more than 255 characters in a custom Description field?

You can't convert a lead if your custom Description field has exceeded the maximum limit of 255 characters. The long text Description custom field must correspond to the Description field character limit values that are copied from the lead to the account during the conversion process. Reduce the number of characters by less than or equal to 255 characters and try again. Alternatively, request that your administrator increase or remove the character constraint for the custom Description field in Leads.

Lead rank suggests a priority to help you select leads for follow up. When the lead is created, a lead rank is first calculated by the assignment manager engine based on ranking rules. You can select a different lead rank from the list in the UI. When the lead is further processed, a different rank may be assigned based on enriched lead data, or the rules may cause the lead to revert to its original rank.

How can I add lead contacts to my sales campaign?

From the Leads overview area, select the lead you want to be part of your sales campaign. From the Lead details page, click the Contacts tab. Select the contacts that you want to add to your sales campaign. From the Actions menu, select Add to Sales Campaigns to view and select a campaign from your saved campaigns. Your selected contacts are notified when you launch your sales campaign.

How can I select and add products or product groups to my lead?

To browse the sales catalog and select and add products or product groups to your lead, your administrator must have added the Browse Catalog button to the Product region of the Edit Lead page.

Click Browse Catalog to open the sales catalog page from where you can search the product or product group that you want. Select the groups or products to include for your selected lead, and when done, click OK to return to editing your selected lead.

What happens if I convert a lead to an opportunity?

You convert a lead to an opportunity when the lead is qualified and is ready for further processing along the sales cycle. Once the conversion is successfully completed, you can review the newly created opportunity using the opportunities UI. During your review, you might want to retain only a select few lead product lines to pursue as revenue on the opportunity. Since the conversion process automatically creates product lines (representing revenue) from all lead lines, you can remove unwanted product lines from the opportunities UI.

You can view opportunities associated with leads in the leads UI. When you convert a lead to an opportunity, the following rules may apply depending on the setup criteria for your company:

  • The person converting the lead becomes the primary sales team member for the opportunity.

  • The customer reference on the original lead is maintained for the opportunity.

  • The associated lead team members are copied with the same primary team member.

  • The newly created opportunity is assigned to the appropriate sales territories.

How can I copy notes, attachments, and activities during Lead to Opportunity conversion?

You can copy notes, attachments, and activities from a lead record to an opportunity record during the lead to opportunity conversion process. Your administrator must set the Standard Reference Copy Lead to Opportunity Map value to the Direct Lead to Opportunity Mapping profile option.

Why can't I see converted leads in my list of opportunities?

If you don't see the converted lead in your list of opportunities, this means that the opportunity is assigned to a different territory.

How can I fix an invalid relationship error when converting leads?

If you try to convert a lead that contains an invalid contact relationship, you may receive an invalid relationship error during the conversion. For example, you create a lead with a valid active primary contact and account. An issue might arise when you go to convert the lead if an incorrect relationship exists for a second contact on the lead. In such a scenario, you must deactivate the relationship and after some time try to convert the lead again.

However if you want the association of the lead and contact to remain, you must add the contact back on the lead through the Contacts tab on the Edit Lead page. Here's how to resolve the issue:

  1. Navigate to the Edit Lead page.

  2. In the Contacts tab, remove the second (nonprimary) contact.

  3. Click Save.

  4. Add the contact that you just removed back again to the lead.

  5. Click Save.

  6. Convert the lead.

Lead qualification determines whether a lead has a budget and project timeline defined, and indicates if someone with purchasing authority is identified. Company-specific standard questions and the associated scoring mechanism help to capture the additional data critical to qualifying leads. A lead is typically considered qualified when the need and purchase interest are confirmed.

Lead assessment helps in the lead follow-up process, where the salesperson continues to assess the lead quality and lead conversion potential through preconfigured assessment templates. From the Assessment tab, the salesperson can conduct a new assessment, view completed assessments, and view the responses to the questions. Assessment templates provide the mechanism for the salesperson to analyze the lead and suggest appropriate next steps based on the overall assessment score and feedback for the lead.

You can use assessments to evaluate the health of a business object, such as an opportunity or a lead..

Administrators set up assessment templates that consist of weighted questions and possible responses that get scored. After selecting the appropriate assessment type, you enter responses for all the questions in an assessment, and achieve a score once the assessment is submitted. This score is used to evaluate the health of the business object. For example, the score could help determine whether an opportunity is viable enough to offer the potential customer a discount.