Understanding Sales Leads and Opportunities

This chapter discusses:

Click to jump to parent topicLeads and Opportunities

This section discusses:

Click to jump to top of pageClick to jump to parent topicLead and Opportunity Management

The key to a successful sales cycle is efficiently managing leads and opportunities toward the closing of a sale. You start by bringing leads into the system, qualifying them, and then converting them to opportunities. Then, you assign potential revenue figures and expected close dates to the opportunities, and you review the opportunities within pipelines and forecasts to estimate individual and company revenue.

Some companies have fast transaction cycles with no distinction between a lead and an opportunity. Other companies have longer sales cycles, and tracking opportunity information becomes critical. Whether a company uses leads only, opportunities only, or both leads and opportunities, sales representatives typically enter and track all of the information. PeopleSoft Sales is a flexible, configurable management tool that enables you to enter and track lead and opportunity data and enables sales managers to view that data to manage sales progress and predict close sales ratios. This diagram illustrates the business flow for managing leads, starting from their creation to their conversion to opportunities:

Processing of leads from their creation to their conversion to opportunities

Sales users can:

Additionally, managers can identify sales teams and assign sales team members.

Delivered Lead and Referral Business Process

PeopleSoft CRM delivers a business process that takes in lead and referral (leads that come from internal employees) information for lead generation and processing. Eligible leads are then converted to opportunities, which go through the usual opportunity management process until closure. This business process is invoked when customers import leads from external sources into the CRM system, and is only available with the integration between the CRM system and Oracle BPEL Process Manager.

See Sales Delivered Business Processes and Web Services.

See Also

Understanding the Sales Process

Click to jump to top of pageClick to jump to parent topicLeads

A lead represents a potential customer for the sale of the company's products and services. In some sales organizations—especially those that sell products and services over the telephone as part of a call center operation—the lead can be used to track all elements of the sales transaction, from qualification to closure. In other sales organizations, a telemarketing organization might use the lead to track and qualify potential customers that are then handed over to an inside sales or field sales organization as opportunities.

PeopleSoft Sales enables you to manage leads and track them from beginning through closures. When a lead is qualified, it can be converted into an opportunity for pursuit by selling organizations. A single person can be a lead sales representative for multiple opportunities. An opportunity can also be associated with multiple leads.

The minimum requirements for creating a lead in PeopleSoft Sales include:

It is recommended that you also include the customer name and at least one contact name and phone number for follow-up. You can enter as much additional information as needed.

You can enter leads into PeopleSoft Sales by:

See Oracle's PeopleSoft CRM Marketing Applications Preface.

You qualify leads to determine how likely it is that the potential customer will make a purchase. With PeopleSoft Sales, you can use a branch script, or survey, to do this. A survey is a set of questions with specified score levels to rate the customer's response. When you finish entering the customer's responses, the system tallies a total of the scores and rates the lead; for example, it might rate a lead as hot, warm, or cold. The marketing or telemarketing department often administers the survey as part of a marketing campaign, or a sales representative might select a survey script to run.

In many organizations, the telemarketing organization is responsible for qualifying leads to a certain point. They can then transfer the lead to the territory management and configurable assignment criteria system to assign it to the sales representative who can accept it, reject it, or turn it back. Sales managers can establish rating rules that automatically assign a rating—for example, hot, warm, or cold—to each lead that is generated from the TeleSales application.

Click to jump to top of pageClick to jump to parent topicOpportunities

You can add an opportunity directly to PeopleSoft Sales, or you can convert an existing lead to an opportunity.

If the organization does not use leads, you can add opportunities and manage and track them as you do leads, including qualifying and assigning them and developing the sales proposals. You cannot, however, accept, reject, or turn back an opportunity; these actions are relevant to assignment of leads by PeopleSoft TeleSales to Sales.

If you use leads and a lead meets the organization's requirements, you can convert the lead to an opportunity.

Note. Opportunities are included in pipelines and forecasts, but leads are not.

As with leads, the minimum requirements for creating an opportunity include:

Click to jump to top of pageClick to jump to parent topicProspects

Sometimes you might want to enter a potential customer or contact into the system so that you can capture their information, but because adding unnecessary information to the database can affect performance, you do not want to commit their information to your database until they become actual customers or contacts. These potential customers or contacts are called prospects, and only the minimal information necessary to identify them is included. Prospects are associated with leads and opportunities (and referrals, in Client Management), but cannot be assigned to partner representatives.

These sales pages display prospect information for leads and opportunities. You can edit prospect information directly on these pages:

Prospects are not stored in the Customer Data Model (CDM); rather, they are stored along with their leads and opportunities. Customers and contacts from the CDM, however, appear as links that enable you to access the CDM component for editing.

When a lead is converted to an opportunity or an opportunity is set to Closed/Won, the prospect information is transferred (pushed) to the CDM, converting the prospect to a contact or customer. A prospect is also pushed to the CDM when you use quick create to manually convert prospects from leads and opportunities to customers or contacts.

If Customer Data Hub (CDH) integration is activated in the CRM system, prospect information that exists in leads is subject to duplication check during the lead to opportunity conversion process.

See CDH Impact on Lead-to-Opportunity Conversion.

Prospect information appears on Sales components only (Lead, Opportunity, Referral) and does not appear on these elements:

Click to jump to parent topicProfile Enablement

The Lead and Opportunity components support the display of profile fields on the More Info page. You can set up separate sets of profile fields to show in leads and opportunities based on the business object that is referenced (person or company).

To add profile fields to the More Info page:

  1. Define profile fields on the Profiles page.

    The CRM system delivers profile fields, some are for general use and some are geared towards specific industries. For profile fields that you want to use, make sure that they are activated.

  2. Add profile fields to profile groups on the Define Profile Group page.

  3. Assign the profile groups to the Sales Person component (for leads and opportunities referencing consumers) or the Sales Company component (for leads and opportunities referencing companies) on Assign Profile Group Display page.

    Here, you can configure if a profile field appears as read-only or can be updated at runtime.

Refer to the see reference for more information on how to set up profiles to display in profile-enabled components.

See Understanding Profiles.

At runtime, the profile fields appear on the More Info page of the component that is set up to display them. You can update the values of these profile fields if they are not set as read-only, which are stored in the corresponding lead or opportunity. However, the current status of the lead or opportunity also plays a role in determining the availability of profile fields for edits. In other words, if a lead or opportunity is in a status (for example, Converted to Opportunity for leads) that does not allow any update to be made, profile fields are not available for edit even if they are not set to be read-only on the Assign Profile Group Display page.

See Also

Maintaining Profile Data for a Lead or Opportunity

Click to jump to parent topicHigher Education for Sales

In the higher education world, when prospects are qualified from the marketing application, telemarketers can create leads for these prospects and leads are then assigned to recruiters either manually or automatically. Recruiters work the leads and convert the qualified ones to opportunities. PeopleSoft Sales helps to build an effective recruiting system in CRM by providing enhancements in these areas:

Click to jump to top of pageClick to jump to parent topicLeads and Opportunities

Enhancements for the Lead and Opportunity components include:

Academic Information Support

A new section is added to the Discover page of leads and opportunities to support the selection and storing of education information for constituents, which include institution, career, programs and plans.

When you convert a lead to an opportunity, you can select to include the academic information in the conversion process. The system displays a warning message if it detects a mismatch of institution and career in the conversion process (especially when converting a lead to an existing opportunity).

Unlike lead conversion, academic information cannot be copied to the new object or objects in the case of cloning.

Refer to the see reference for more information on the Academic Information section.

See Creating a Sales Lead.

Changes in Pages, Sections and Fields

The CRM system delivers the Higher Education Sales Display Template Family (HE_SALES) for displaying Higher Education leads and opportunities. The system renders leads and opportunities using the HE_SALES display template if the Higher Education option is selected in the Installation Options page.

The HE_SALES display template makes these visual changes to the Lead and Opportunity components:

See Creating a Sales Lead, Creating a Sales Opportunity, Assigning Sales Representatives to a Lead or Opportunity, Managing a Lead or Opportunity on the Summary Page.

Click to jump to top of pageClick to jump to parent topicAssignment Group for Higher Education

PeopleSoft Sales uses the application engine to assign sales representatives to leads and opportunities automatically. The engine refers to assignment groups for assignment configurations and criteria, together with territory definitions, to determine the appropriate sales representatives or sales teams for leads and opportunities. The system delivers a new assignment group to support the automatic assignment of recruiters and recruiting teams for Higher Education leads and opportunities. The assignment configuration and criteria of the new HE_SALES assignment group are similar to the setup of the existing Sales assignment group, with these differences:

See Also

Creating or Editing Territories

Configuring Assignment Criteria

Click to jump to top of pageClick to jump to parent topicPublishing Academic Information Changes

The CRM system stores the academic information (which includes institution, career, programs and plans) of a constituent in both its consumer and its lead and opportunity records. To keep the information synchronized between these records, the system publishes academic information to Constituent Lifecycle Management (CLM), which is a one-way operation, when a change occurs in a lead or opportunity so that the update is reflected in the consumer record as well.

The system publishes academic information to CLM when a change occurs in one of these items in a lead or opportunity at save time:

The published update includes this list of information, which is passed to CLM:

Note. This publication pertains only to changes that occur between lead or opportunity and consumer (individual) records and it does not apply to leads and opportunities that are created for companies (organization).

This graphic illustrates the logic flow for publishing academic-related information changes taking place leads and opportunities:

Logic flow for sending one-way publish to update consumer records with changes in academic-related information that occurred in leads or opportunities

Click to jump to parent topicDifferences Between Leads and Opportunities

A significant difference between leads and opportunities is their relation to pipelines and forecasts. Opportunities, but not leads, are rolled up into pipelines and forecasts. If you integrate PeopleSoft Incentive Management with the system, you can include opportunities (but not leads) in the compensation calculations of Incentive Management.

For the most part, the Lead component has the same pages (Summary, Discover, Assign, Qualify, Propose, Tasks, Notes, History, Call Reports, and More Info) and the same sections as the Opportunity component. The following exceptions relate specifically to forecasting, which uses products, prices, and revenue allocations:

Here are some additional differences between leads and opportunities:

Click to jump to parent topicWorkflow for Leads and Opportunities

You can set up workflow to send notifications when certain events occur in the Lead and Opportunity components. For example, the system can send a workflow notification to a sales manager if a sales representative rejects a lead. PeopleSoft delivers several policies that specify the details for workflow:

Policy Name

Description

Lead is Rejected or Turnback

The system sends notification if a sales user rejects or turns back a lead.

Lead ESA Pricing Info Received

The system sends notification when it receives pricing information from the PeopleSoft Service Automation application for a quote created from within a lead.

Lead not accepted in due time

The system sends notification when a lead is not accepted in due time, which is defined for the lead rating.

Opportunity ESA Pricing Info Received

The system sends notification when it receives pricing information from the PeopleSoft Service Automation application for a quote created from within an opportunity.

Like other PeopleSoft Customer Relationship Management applications, PeopleSoft Sales uses the Active Analytics Framework (AAF) to configure workflow.

See Setting Up PeopleSoft CRM Workflow.

Click to jump to parent topicHistory Tracking for Leads and Opportunities

The CRM system supports history tracking to maintain records of events that occur in the Lead and Opportunity components through the AAF. For example, the system can log a record if a sales manager changes the sales representative assignment for a lead. PeopleSoft Sales delivers these AAF policies that specify the details for history tracking:

Policy Name

Description

Lead Assigned To Changed

The system logs a history record if a sales user changes the sales representative assignment for a lead.

Lead Rating Changed

The system logs a history record if a sales user changes the rating for a lead.

Lead Status Changed

The system logs a history record if a sales user changes the status for a lead.

Opportunity Assigned To Changed

The system logs a history record if a sales user changes the sales representative assignment for an opportunity.

Opportunity Sales Stage Changed

The system logs a history record if a sales user changes the sales stage for an opportunity.

Opportunity Status Changed

The system logs a history record if a sales user changes the status for an opportunity.

When enabled, these policies are triggered when a lead or opportunity of the specified setID is saved. The framework evaluates the conditions of the policies and carries out actions for the policies that have a positive evaluation result.

See Also

Understanding CRM Action Types

Configuring Sales History Actions