Sales Cloud Applications (9%) Flashcards
How can leads be captured within Salesforce?
a. Web to Lead
b. Lead Import
Lead assignment rules
Change the owner of a newly created or reassigned lead based on a set of rules defined by the system administrator
Executed sequentially
Multiple sets of assignment rules, only one can be active at a time e.g. uploaded from marketing vs website submission
Default lead owner - when no rules are matched
Web-to-Lead: Name 4 steps to setting up Web-to-Lead?
Generates a contact form that can be integrated within an existing website
Each form submission create a lead record in Salesforce
- Configure default response template, and auto-response rules
- Configure Web-to-Lead Settings (Enabled, Default Creator, Default Response Template)
- Generate the web-to-lead HTML code
- Customize your web-to-lead HTML code (CSS, styling elements, form validation)
Web-to-Lead: Limitations
Relationships:
Cannot capture lookup relationship fields, with the exception of the Campaign field. When the campaign field is included with a web-to-lead submission, the lead will be automatically joined to the specified campaign.
Validation:
The web-to-lead form generated by Salesforce does not restrict data entered into the form. Any validation (e.g. required, email) must be added to the generated HTML code
Daily Limits:
500 per day. Can contact Salesforce to have the limit increased. Or, use another method to capture leads.
Lead Auto-Response Rules
Which email template used in reply to web-to-lead submission
Multiple sets allowed, only one active at a time e.g. Response set just for holidays
Pre Lead Conversion: Lead flow
Typically, leads are converted when they have been identified as qualified sales prospects.
Common lead flow is as follows:
- Lead generated through web-to-lead
- Lead assigned to inside sales queue via auto-assignment rule
- Inside sales rep manually takes ownership of lead from queue
- Inside sales rep calls and qualifies lead
- Lead is converted and transferred to outside sales rep
Lead Conversion:
Name 3 object records that are created from lead?
Name 2 other things that happen to the Lead record?
- The following are created and populated with the lead’s data (unless otherwise specified during conversion):
a) Contact
b) Account
c) Opportunity - The lead field “Converted” is changed from False to True.
- The lead record can no longer be viewed by users and will not be displayed within search results. (The lead record and its data are still present, however, and can be reported on) Note: For custom lead fields to transfer to the contact/account/opportunity during lead conversion, the administrator must map them
Lead Conversion: Custom Field Mapping
- Create field to store the data on the target object.
- Map the lead field to the target object.
Note: A custom lead field can only be mapped to a single field on either contact, account, or opportunity. For instance, could not map “Lead.Product Interest” to both “Account.Product Interest” and “Opportunity.Product Interest”.
A workaround for this is to create a formula field that replicates the value of the original field. Then map the formula field to the second field.
Lead Conversion: What if the account/contact/opportunity already exists?
Opportunity: Option “Do not create a new opportunity on conversion”. There is no way to convert a lead to an existing opportunity
Account: Accounts listed with the same name as the field “Company” on the lead record. If an account name contains the company’s name, then you will have the option to use the existing account record.
Contact: If you attach the lead to an existing account and the lead name matches the name of an existing contact, then you will also have the option to use the existing contact record:
Lead Conversion: Considerations
- Converted leads cannot be modified (even via the API)
- Custom fields (e.g. items in a picklist) on each object are maintained separately
- Record Type set to the default record type of the user performing lead conversion
- Custom relationships (look-up/master-detail) to the lead object do not transfer during conversion. An apex trigger or custom VisualForce lead conversion page is required for this logic
- The Chatter feed of the lead record is not transferred during conversion
- Once a lead is converted, it cannot be reverted to an unconverted state
Sales Processes and Opportunity Stages: Name 5 fields on Opportunity Stages object?
Bonus Point: How is Expected Revenue calculated?
When you define an opportunity stage, several other variables must be defined in addition to stage name:
- Stage Name
- Type (Open, Closed/Won, Closed/Lost)
- Probability
- Forecast Category
- Chart Colours
Probability represents the likelihood that an opportunity will be sold, and is used to calculate expected revenue.
Expected Revenue = Amount x Probability / 100
Sales Processes and Opportunity Stages: Sales Processes
Determine which opportunity stages are selectable when record types are enabled
A sales process is not required if record types are not enabled (all stages are available)
Forecasts
Used to predict future sales within an organisation
Forecast data is aggregated from each user’s opportunity records, and the related forecast category of each opportunity’s stage
Can be overridden without updating the source opportunity records
Quotas
Used to set target sales goals for forecast users
Allows organisations to establish greater accountability for meeting sales expectations.
Campaigns: What license is required to create a campaign?
User must have the “Marketing User” feature license as well as corresponding object-level security