Sales-Cloud-Consultant Questions and Answers

• Mapping the ERP unique ID to a custom external ID unique number field is the best way to meet the requirement of organizing data using the unique ID that is a number type in the ERP. An external ID is a custom field that has the “External ID” attribute, meaning that it contains unique record identifiers from a system outside of Salesforce. A unique number field is a custom field that has the “Unique” attribute, meaning that it does not allow duplicate values in the field. By mapping the ERP unique ID to a custom external ID unique number field, Cloud Kicks can use this field to match records during data import or update operations, avoid duplicate records or incorrect data, and maintain data integrity between Salesforce and the ERP system.

• The Opportunity’s Account will be implicitly Read for the team is something that the consultant should consider when rolling out Opportunity Teams with Private Account organization-wide defaults. An Opportunity Team is a group of users who work together on an Opportunity, such as sales reps, sales engineers, managers, etc. Each Opportunity Team member has a role and a level of access to the Opportunity and its related records, such as Products, Quotes, Activities, etc. Organization-wide defaults are the baseline level of access that users have to records they do not own or share. Private organization-wide defaults mean that only the record owner and users above them in the role hierarchy can view and edit the records. Implicit sharing is a type of sharing that grants additional access to records based on relationships between objects or users. Implicit Read means that users can view but not edit a record.
• By rolling out Opportunity Teams with Private Account organization-wide defaults, the consultant should consider that the Opportunity Team members will have implicit Read access to the Opportunity’s Account, meaning that they can view but not edit the Account record related to the Opportunity they are working on.

Creating a junction object between Campaign and Opportunity is the best way to track which marketing activities influenced a customer to make a purchase. This junction object will allow you to track the influence of multiple Campaigns on a single Opportunity, which can be used to gain insights into which Campaigns are most effective.

• Enabling the Person Accounts feature is irreversible is something that the consultant should consider when evaluating Person Accounts. Person Accounts are a type of account that represent individual consumers rather than business accounts. Enabling Person Accounts is a permanent action that cannot be undone or deactivated once it is done. Therefore, the consultant should carefully evaluate the pros and cons of using Person Accounts and make sure that Cloud Kicks understands the implications and limitations of this feature before enabling it.

• Building a custom report on Opportunity with custom summary formulas to show win/loss ratio is the best way to meet the requirement of measuring the win ratio for all of the sales associates. A custom report is a report that can be created and customized by users based on their needs and preferences. A custom summary formula is a formula that can be added to a report to calculate values based on the report data, such as sums, averages, percentages, etc. A win/loss ratio is a metric that measures the percentage of closed won Opportunities out of all closed Opportunities. By creating a custom report on Opportunity with a custom summary formula that calculates the win/loss ratio, managers can easily see the performance of their sales associates.

The most likely cause of the records failing is that updates to child records that have the same parent record are being processed simultaneously. This can cause the records to fail because child records must be imported after the parent records have been imported, and if the parent record is being updated at the same time as the child records, the import will fail. The other options are not likely to be the cause of the failed import.

When implementing sharing rules, the consultant should explain the following considerations to CK:

• CK can expand access beyond the organization-wide default levels with sharing rules. Sharing rules are used to grant additional access to records based on record ownership, criteria, or territory.
• Organization-wide defaults must be Public Read Only or Private to create sharing rules. Sharing rules cannot be created for objects with Public Read/Write or Public Read/Write/Transfer organization-wide defaults.
• When multiple sharing rules are assigned, the user is assigned the least restrictive access. For example, if one sharing rule grants Read-Only access and another sharing rule grants Read/Write access to the same record, the user will have Read/Write access.

Opportunity Splits allow users to divide credit for an opportunity among multiple sales reps who contribute to closing it. Users can specify how much revenue or quantity each sales rep receives from an opportunity, either as a percentage or an amount. Opportunity Splits can be enabled from Setup, and they require that Opportunity Teams are also enabled. Users can then add or edit Opportunity Splits from the Opportunity Splits related list on Opportunity page layouts.

• Adoption Dashboards Pack is the best feature to measure core Sales Cloud record data and track data trends and adoption after implementing Sales Cloud for a mid market sales team. Adoption Dashboards Pack is a package that contains pre-built dashboards and reports that show how users are adopting and using Salesforce features and functionalities, such as creating and updating records, logging activities, running reports, etc. By using Adoption Dashboards Pack, Universal Containers sales management can monitor and analyze core Sales Cloud record data such as accounts, contacts, opportunities, etc., and see how they change over time and across different dimensions.

Path is a feature that helps users visualize and update key fields for each stage of a process, such as an opportunity sales process. By checking the Key Field Required checkbox, the consultant can make sure that users enter the data that managers expect at each stage before moving to the next stage. This can improve data quality and reporting accuracy.

Einstein Activity Capture (EAC) allows users to store emails and attachments in Salesforce and have them visible in the Activity Timeline and Related Lists. Users can choose to show emails added via EAC in the Related Lists activities view.

To use Einstein Activity Capture, users must connect their email accounts to Salesforce. They must also agree to the terms of the service provider before they can send emails in Lightning.

Schedules on the Product object allow users to track the revenue and quantity of products over time, such as for subscription or installment payments. Schedules can be enabled for any product that has a schedule type of Revenue or Quantity, and they can be customized to match the payment terms of each opportunity.

Setting opportunity access on the role to View All opportunities associated with their accounts allows sales users to view all opportunities that are related to accounts they own or are above them in the role hierarchy. This meets the requirement of giving sales users access to opportunities that are tied to accounts they own. Setting organization-wide defaults for opportunities to Private restricts access to opportunities by default, so that only the owner and users above them in the role hierarchy can view them. This meets the requirement of giving sales users access to opportunities they own.

• Activating the products and adding them to the price book are the two steps required to make products available for sales reps to add to Opportunities. A product is a good or service that can be sold in an Opportunity. A product must be active in order to be added to a price book. A price book is a list of products and their prices that sales reps can use when creating Opportunities. A product must be added to a price book before it can be added to an Opportunity.

According to the Salesforce Sales Cloud Consultant Study Guide, in order to support multiple currencies in Salesforce Opportunities and forecasting, each currency requires its own custom price book. It is not necessary for each user to select their personal currency or for every currency price to be added to all of the products in the standard price book.

Salesforce Maps is a feature that allows users to visualize and optimize their sales territories and activities on interactive maps. Users can also access various data sources to enrich their maps with additional information, such as demographics, weather, traffic, or business data. The Demographic Context data source is one of the data sources that users can add to their maps to display income ranges for regions within their territories, such as zip codes, counties, or states. This can help sales reps determine the best neighborhoods to canvas based on the household income range of their potential customers.

• The data update will cause sharing recalculations and should be completed during off-peak hours and the team can defer sharing calculations to decrease the risk of lock errors during the data update are two factors that should be considered when updating the sales territories and Account owners for 400,000 accounts with Private organization-wide defaults. Sharing recalculations are processes that update record access based on changes to sharing settings or ownership. Off-peak hours are times when there is less user activity or system load on Salesforce. Deferring sharing calculations is an option that allows users to postpone or schedule sharing recalculations for later times instead of running them immediately. Lock errors are errors that occur when two or more processes try to access or modify the same record at the same time.
• By considering these two factors, Universal Containers can ensure that the data update is performed efficiently and effectively without affecting user experience or data integrity. By completing the data update during off-peak hours, Universal Containers can avoid impacting user performance or availability during peak hours when there is more user activity or system load on Salesforce. By deferring sharing calculations, Universal Containers can reduce the risk of lock errors during the data update by running them at a later time when there is less concurrent access or modification of records.

reCAPTCHA is a service that protects websites from spam and abuse by using a simple test to verify that users are human. By enabling reCAPTCHA verification in Web-to-Lead settings, the customer can prevent bots from submitting web-to-lead forms and creating unwanted leads.

Creating retailer and distributor lead processes can help CK follow two different lead qualification processes before converting leads into opportunities, as it allows them to define different sets of picklist values for the Status field for each lead type. A lead process is a collection of stages that represent the steps that users take to qualify leads, such as Open, Contacted, Qualified, or Converted. Creating Status picklist values specific to each lead type can also help CK follow two different lead qualification processes, as it allows them to customize how they track and measure their progress with different types of leads. For example, they may have different criteria or actions for qualifying a retailer lead versus a distributor lead. Creating distributor and retailer lead record types can also help CK follow two different lead qualification processes, as it allows them to assign different page layouts, processes, and business logic for each lead type. A record type is a way to categorize records based on different business requirements or user profiles.

• Using quotation marks operator around contact’s first and last name is a recommendation that can yield better search results when searching for contacts in global search. Global search is a feature that allows users to search for records or information across multiple objects and fields in Salesforce. Quotation marks operator is an operator that can be used in global search to find an exact phrase or match in a record or field. For example, searching for “John Smith” will return only records or fields that contain John Smith as an exact phrase or match, not John Doe or Adam Smith or John Smithson. By using quotation marks operator around contact’s first and last name, Cloud Kicks users can narrow down their search results and find the contacts they are looking for more easily and quickly.

Using a validation rule on Opportunity Products can prevent a sales rep from adding Products marked as requiring the myTrailhead badge if the rep has yet to complete the badge. The validation rule can check the value of a custom field on the Product object that indicates whether the myTrailhead badge is required, and compare it with a custom field on the User object that tracks whether the sales rep has completed the badge. If the validation rule evaluates to true, it can display an error message and block the addition of the Product. Using a separate price book for the Products requiring the myTrailhead badge and only sharing the price book with sales reps who have completed the badge can also validate that sales reps have completed the myTrailhead badge. The price book can contain only the Products that require the badge, and it can be shared with sales reps who have a custom field on their User record that indicates they have completed the badge. This way, only those sales reps can access and add those Products to their Opportunities.

When Account Teams are enabled and used for an account, Sales Rep A can grant Read access on the account’s cases to Sales Rep B by adding Sales Rep B as a team member on the account and assigning a team role that has Read access to cases. Sales Rep A can also allow Sales Rep B to view one of the opportunities on the account by adding Sales Rep B as a team member on that opportunity and assigning a team role that has at least Read access to opportunities.

• Account relationships are visible from Person Account records and Account Hierarchy displays only the Accounts users have Read permission to view are two considerations that the consultant should take into account when showing Account relationships to sales reps and reporting on them. Account relationships are connections between Accounts that indicate how they are related to each other, such as parent-child, partner, competitor, etc. Account Hierarchy is a feature that shows how Accounts are related in a tree structure based on their parent-child relationship. Account relationships are visible from Person Account records, meaning that sales reps can see how Person Accounts are related to other Accounts from their record page. Account Hierarchy displays only the Accounts users have Read permission to view, meaning that sales reps can only see the Accounts they have access to in the hierarchy.

To set sales quotas for all sales reps, the consultant should consider the following solutions:

• Enable Forecast Quotas from Setup. This allows the administrator to enable quotas for users and assign them to forecast types.
• Use the API. This allows the administrator to import quota data from external sources using SOAP or REST API calls.
• Use Data Loader. This allows the administrator to import quota data from CSV files using a graphical user interface.

Advanced Currency Management allows you to specify different conversion rates for different time periods, such as monthly or quarterly, and use them in reports and forecasts. This can help you generate accurate reporting that reflects the currency fluctuations over time. Org-wide reporting can also display deal values in different currencies based on the user’s preference or the corporate currency. Verified References:

• https://developer.salesforce.com/resources2/certification-site/files/SGCertifiedSalesCloudConsultant.pdf (page 14)
• https://help.salesforce.com/s/articleView?id=sf.admin_currency.htm&type=5

• Using Salesforce Maps, configure a Data Layer showing open opportunities is the best solution to meet the requirement of visualizing all open opportunities based on the location of the related Account. Salesforce Maps is a feature that allows users to view and manage their geographic data on an interactive map. A Data Layer is a layer of data that can be added to a map to show records from one or more objects based on filters and criteria. By using Salesforce Maps, configure a Data Layer showing open opportunities, Cloud Kicks sales representatives can see all open opportunities on a map based on the address fields of their related accounts, and perform actions such as creating tasks, logging calls, updating fields, etc.

To test the changes and updates before go-live, the consultant should recommend creating a new Sandbox, populating it with data, and asking volunteers to test it with use cases. A Sandbox is a copy of the production org that can be used for development, testing, and training purposes. A Sandbox allows the consultant to test the changes in a safe and isolated environment without affecting the live data and users. A Sandbox can also be refreshed to get the latest data and metadata from the production org.

These answers will allow CK to sell its products in different currencies, as each custom price book can have a different currency and each product can have multiple prices in different currencies. The standard price book must have at least one price for each product in each currency that is used in the org.

Arranging multiple sessions with small groups of employees is an efficient approach to conduct discovery meetings, as it allows the consultant to interact with different types of users and gather more detailed and specific feedback from them. Sending a survey to all employees asking for a list of desired changes is another efficient approach, as it enables the consultant to collect quantitative and qualitative data from a large number of users in a short time. Asking management to select which employees should participate in sessions is also an efficient approach, as it ensures that the consultant meets with the key stakeholders and representatives of each business unit or function.

Revenue Schedules are a feature that allow users to track the revenue and quantity of products over time, such as for subscription or installment payments. Revenue Schedules can be enabled for any product that has a schedule type of Revenue or Quantity, and they can be customized to match the payment terms of each opportunity. By using Revenue Schedules, Universal Containers can capture the installment payment plan details for each product, such as the number of installments, the amount per installment, and the frequency of installments. This can help the finance department forecast the revenue and cash flow from each opportunity more accurately.

This is the approach that the consultant should use for the source data migration. Accounts, Contacts, and Opportunities are related objects in Salesforce, and they have dependencies based on their lookup or master-detail relationships. Accounts are parent objects of Contacts and Opportunities, so they should be migrated first. Contacts are child objects of Accounts and parent objects of Opportunity Contact Roles, so they should be migrated second. Opportunities are child objects of Accounts and parent objects of Opportunity Products and Opportunity Splits, so they should be migrated last. Verified References: [Data Migration Best Practices]

• Approach and Scope are two sections of a SOW that the consultant should discuss further with Cloud Kicks to meet the requirement of clearly stating who will train users on new features and how the training will be delivered. A SOW is a document that defines the project objectives, deliverables, timeline, costs, and responsibilities of both parties involved in a project. The Approach section describes the methodology and strategy that will be used to achieve the project objectives and deliverables. The Scope section defines the specific work items and activities that will be performed as part of the project, as well as any assumptions, exclusions, or dependencies. By discussing these two sections with Cloud Kicks, the consultant can specify who will be responsible for providing user training (e.g., consultant or client), what type of training will be offered (e.g., online or onsite), how many sessions will be conducted (e.g., one or multiple), what topics will be covered (e.g., new features or best practices), etc.

Creating a Slack channel to gather and discuss feedback from users is a good way to improve the rate of user adoption after a Sales Cloud implementation. A Slack channel can provide a platform for users to share their opinions, suggestions, questions, and issues about the new solution. It can also help the consultant and the leadership team to monitor user sentiment, address user concerns, and provide support and guidance. Verified References:

• https://developer.salesforce.com/resources2/certification-site/files/SGCertifiedSalesCloudConsultant.pdf (page 20)
• https://trailhead.salesforce.com/en/content/learn/modules/sales_admin_user_adoption/sales_admin_user_adoption_feedback

Moving the invoice related list to a separate tab on the Lightning page can solve the issue of long rendering time, as it allows the account record to load faster without loading the invoice related list at the same time. The user can then click on the tab to view the invoice related list when needed. This also improves the user experience and the page layout by reducing clutter and scrolling.

Adding the Lead Score field to the Lead Page layout is a necessary step to fix the issue of pilot users not being able to view the Lead Score field on the Lead record page. The Lead Score field is a standard field that shows how likely a lead is to convert based on Einstein’s analysis of historical data and predictive factors. The Lead Score field must be added to the Lead Page layout for users to see it on their lead records. Assigning the Einstein Lead Scoring permission set is another necessary step to fix the issue, as it grants users access to view and use Einstein Lead Scoring features, such as Lead Score, Lead Score Insights, and Lead Score Field History Tracking.

• Deploying after the Salesforce Release ensures that the configuration is compatible with the latest version of Salesforce and avoids any potential issues or errors that might arise from deploying during a release window.
• Testing new configurations in a Preview Sandbox allows the configuration to be validated against the upcoming Salesforce Release before deploying to production. A Preview Sandbox is a sandbox that is upgraded when the next release begins its preview period.

Account Teams are groups of users who work together on an account and its related records, such as opportunities, contracts, and cases. Account Teams allow users to share different levels of access to accounts and associated records based on their team roles and responsibilities. For example, a sales rep may have full access to an account and its opportunities, while a customer service agent may have read-only access to the account and full access to its cases.

Deploying the changes from the sandbox to production once both environments are on the same version is the safest and most reliable option, as it ensures that there are no compatibility issues or errors due to different versions of Salesforce. The fix requires functionality in the sandbox version, which means that it cannot be deployed to production until production is upgraded to the same version. Deploying before or during the upgrade window may result in failures or conflicts.