Sales Cloud Consultant Interview Questions

The Lead lifecycle moves a prospect through statuses such as Open, Working, Nurturing, Unqualified, and Converted. Lead Status tracks where the lead is in the qualification process; admins customise picklist values to match the sales process. Lead Scoring (Einstein or custom formula fields) ranks leads by engagement signals or demographic fit. Lead Assignment Rules automatically route new leads (created via Web-to-Lead, import, or manual entry) to the correct user or queue based on criteria such as geography, industry, or lead source. When a lead is qualified, Lead Conversion creates up to three records: an Account (new or matched to an existing one), a Contact, and optionally an Opportunity. Custom lead fields can be mapped to Account, Contact, or Opportunity fields using Lead Field Mapping in Setup so data carries over cleanly. Converted leads are hidden from standard list views and cannot be unconverted without third-party tools.

Web-to-Lead lets organisations capture lead information from a website form directly into Salesforce. Configuration steps: (1) Enable Web-to-Lead in Setup. (2) Use the Web-to-Lead generator to select up to 255 fields and download the HTML snippet. (3) Embed the snippet on your website. Key considerations: (a) Default Lead Creator — the user whose name appears as the creator of submitted leads; ensure this user has the correct profile and is active. (b) Response email template — auto-acknowledge the submitter. (c) Spam / CAPTCHA — Salesforce's built-in reCAPTCHA can be enabled to reduce bot submissions. (d) Daily limit is 500 leads per day by default (can be raised via a case to Salesforce). Leads exceeding the limit are emailed to the default creator. (e) Assignment rules apply to Web-to-Lead submissions just like manually created leads. Always map the lead source to "Web" for tracking.

Campaigns track marketing initiatives and their impact on revenue. Key concepts: (1) Campaign Member Statuses are customisable per campaign (e.g., Sent, Opened, Responded, Converted) and one status is marked as "Responded". (2) Campaign Hierarchy allows parent/child grouping so totals from child campaigns roll up to the parent (up to 5 levels). (3) Campaign ROI is calculated as ((Actual Cost − Budgeted Cost) / Budgeted Cost) × 100 — the ROI % field is auto-calculated. (4) Campaign Influence links campaigns to opportunities to show marketing's contribution to revenue. Models include: Primary Campaign Source (only the campaign on the opportunity), First Touch / Last Touch / Even Distribution models (via Customisable Campaign Influence). Admins configure influence models and time-decay rules. The campaign on the Opportunity's Primary Campaign Source field and the Contact Roles' associated campaigns determine influence credit.

Each Opportunity Stage picklist value has three attributes configured in Setup: (1) Probability (%): The default win probability for that stage — Salesforce auto-populates this on the Opportunity when the stage changes, but reps can override it manually. (2) Forecast Category: Maps the stage to a forecasting bucket — Pipeline, Best Case, Commit, Omitted, or Closed. This determines whether the opportunity appears in collaborative forecasting totals. (3) Close Date: Required field; the expected close date drives pipeline aging reports and forecast periods. Best practice is to align stage names to real buyer milestones (Discovery, Proposal, Negotiation, Closed Won/Lost) so probability reflects actual win likelihood. Admins can create multiple Opportunity record types with different stage picklists to support different sales motions (e.g., New Business vs Renewal).

Opportunity Teams allow multiple users to collaborate on a single opportunity. Each team member has a team role (e.g., Account Executive, Sales Engineer, BDR) and an access level (Read Only or Read/Write) to the opportunity record. Default opportunity teams can be set on a per-user basis so they are auto-added to new opportunities. Opportunity Splits (enabled separately in Setup) allocate a percentage of the opportunity's revenue credit across team members — the splits for a given type must total 100%. Types of splits: (1) Revenue Split (built-in): Allocates the opportunity amount for commission tracking. (2) Overlay Split: Can total more than 100%, used for supporting roles such as pre-sales engineers. Custom split types can be added. Splits feed into collaborative forecasting if configured, allowing forecast managers to see individual quota attainment based on split credit.

Account Teams are defined on the Account record and represent a persistent group of users who work together on that account. Each member has a team role and an access level (Read Only or Read/Write) for the account, and optionally for related contacts, opportunities, and cases. Account teams are ideal for large, strategic accounts managed by a named account team. Differences from Opportunity Teams: (1) Account teams are account-wide and persist across all associated opportunities; opportunity teams are per-opportunity. (2) Account team members can be automatically added to new opportunities created on the account. (3) Account teams do not have splits — revenue attribution is handled at the opportunity level. Use account teams to manage CRM access and relationship ownership; use opportunity teams for deal-specific collaboration and compensation splits.

A Standard Price Book is the system default and contains the list price for every active product. Every product must have an entry in the standard price book before it can be added to a custom price book. A Custom Price Book contains a subset of products at negotiated or market-specific prices and is associated with an opportunity or quote to drive pricing. Typical use cases: regional pricing, partner pricing, or segment-specific discounts. With Multi-Currency enabled, each price book entry can have a price per active currency, and Salesforce converts amounts to the corporate currency using the defined exchange rates. With Advanced Currency Management (dated exchange rates), currency conversion on Opportunity Amount and related fields uses the exchange rate in effect on the Opportunity Close Date rather than the current rate, providing historically accurate revenue reporting.

Quotes are records that present proposed pricing to a customer. They are created from an Opportunity and pull the associated Price Book. Quote Line Items mirror Opportunity Products — each line has a product, quantity, unit price, discount, and total price. Key behaviours: (1) Quote PDF: A formatted quote document can be generated from a Quote Template and emailed to the customer directly from the record. (2) Syncing: Only one quote per opportunity can be synced at a time. When a quote is synced, changes to quote line items automatically update the opportunity products and amount, and vice versa. Syncing stops if the quote is unsynced or if another quote is synced. This ensures the opportunity's financials always reflect the latest proposed deal. Quote Approval Processes can be layered on top for discounting governance.

Enterprise Territory Management (Territory Management 2.0) lets organisations assign accounts and opportunities to territory-based sales structures. A Territory Model has three lifecycle states: (1) Planning: The model is being built — territory types, territories, and assignment rules can be configured but the model is not active. Users can preview assignments. (2) Active: The model is live; Salesforce applies territory assignment rules to accounts and opportunities. Only one model can be active at a time. (3) Archived: The model is deactivated and becomes read-only. Key concepts: User Assignments associate sales users with territories so they gain access to accounts in those territories. Filter-based Opportunity Territory Assignment runs a rule or custom Apex logic to automatically assign the territory to new opportunities based on the account's territory. Territory hierarchies roll up revenue for territory-based reporting and forecasting.

Collaborative Forecasting allows sales managers to review and adjust their team's forecast in a hierarchical view. Key components: (1) Forecast Types: Each type measures a different field — Opportunity Revenue, Opportunity Quantity, Product Family Revenue, Opportunity Splits, or Territory (when Territory Management is enabled). Multiple forecast types can be active simultaneously. (2) Forecast Periods: Monthly or quarterly, based on the fiscal year settings. (3) Forecast Categories: Pipeline, Best Case, Commit, Most Likely, Omitted, and Closed — mapped from opportunity stages. (4) Adjustments: Managers can adjust their own or their subordinates' forecast amounts without changing the underlying opportunities; both the original and adjusted values are preserved. (5) Quotas: Uploaded via Data Loader or the UI; compared against the forecast to show attainment. Forecast sharing allows delegates to manage a user's forecast.

Products (Product2 object) are the items or services a company sells. Each product has a product family, product code, and description. A product becomes available for sale by adding a Price Book Entry — the combination of a product and a price book with a specific unit price and currency. Opportunity Products (OpportunityLineItems) link products to opportunities via the selected price book. Revenue Schedules spread an opportunity line item's revenue over multiple periods (e.g., a $120k annual subscription split into 12 monthly $10k increments). Quantity Schedules spread product delivery over time (e.g., 12 monthly shipments of 100 units). Schedules can be established/renewed automatically based on the product's default schedule settings or set manually per line item. Scheduled revenue feeds into forecasting and revenue reports.

Tasks are to-do items with a due date, priority, and status. They can be assigned to a user and related to records (Opportunity, Account, Contact, Lead). Events are time-specific calendar entries with a start/end time and can be tied to related records. They appear in the Salesforce Calendar and can sync to Outlook or Google Calendar via integrations. Log a Call creates a completed task with a call description and is accessible via the Quick Actions menu or Activity Composer. The Activity Timeline on a record page shows upcoming tasks and events, past activities, and email threads in chronological order — admins can configure which activity types appear. Shared Activities (enabled in Setup) allows one activity to be related to multiple contacts. Task and Event record types can differentiate call logs from follow-up tasks. Einstein Activity Capture automates activity logging from connected email and calendar accounts.

Einstein Lead Scoring uses machine learning trained on an org's historical lead conversion data to predict how likely each lead is to convert. The model analyses patterns across lead fields (job title, industry, lead source, company size, etc.) and surfaces a score (1–99) plus the top factors driving that score. Configuration: (1) Enable Einstein Lead Scoring in Setup under Einstein > Lead Scoring. (2) Ensure there is sufficient historical conversion data (Salesforce recommends ≥ 1,000 converted leads in 6 months). (3) Optionally configure Scoring Segments to build separate models for different lead segments (e.g., by region or lead source) for higher accuracy. (4) Add the Einstein Lead Score field and Scoring Factors component to lead page layouts and list views. (5) Assign the Einstein Analytics permission set licence. Sales reps use the score to prioritise their outreach queue.

Einstein Opportunity Scoring uses AI to predict the likelihood of winning each open opportunity, expressed as a score from 1 to 99. The model is trained on your org's closed (won and lost) opportunities and considers fields such as stage, age, activity patterns, product, industry, and deal size. Key features: (1) The score appears on Opportunity records and list views, allowing reps to focus on deals most likely to close. (2) Score Factors explain why a score is high or low (e.g., "No activity in 14 days" or "Strong engagement from decision-maker"). (3) Scores update continuously as opportunity data changes. (4) Forecast managers can use scores alongside forecast categories to validate commit accuracy. (5) Einstein Opportunity Scoring requires a Sales Cloud Einstein or Revenue Intelligence licence. Ensure sufficient historical data: Salesforce recommends at least 200 closed won and 200 closed lost opportunities.

Einstein Activity Capture (EAC) automatically logs emails and calendar events between a connected email/calendar account (Microsoft 365 or Google Workspace) and Salesforce records, reducing manual data entry. Key configuration: (1) Connected Accounts: Each user connects their email/calendar in their personal settings; admins can deploy connections org-wide via a configuration in Setup. (2) Sync Settings: Control direction — Salesforce to email/calendar, email/calendar to Salesforce, or bidirectional — separately for events and contacts. (3) Sharing Settings: Activities captured by EAC are stored in a separate data store (not standard Activity object) by default; enabling the "Share Activities" setting makes them visible on record timelines to other users. (4) Exclude Rules: Admins configure email/domain exclusions (e.g., internal company domain, personal emails) so private or irrelevant communications are not logged. (5) EAC does not create editable Task/Event records by default — use Inbox or custom flows for writeback if needed.

Sales Cadences (part of High Velocity Sales / Sales Engagement) are automated, multi-step outreach sequences that guide SDRs and sales reps through a defined series of touchpoints (emails, calls, LinkedIn tasks) with prospects. Key concepts: (1) Sequence Steps: Each step has a type (email, call, custom), a wait time before the next step, and optional branching logic based on prospect responses. (2) Call Scripts: Text guidance shown to reps during a call step, accessed from the Work Queue. (3) Work Queue: A prioritised list of tasks generated by active cadence assignments, surfaced in the Sales Console or Einstein Conversation Insights panel. (4) Reps add Leads or Contacts to a cadence; the cadence engine creates and assigns tasks automatically at each step's scheduled time. (5) Cadence branch logic allows different paths for replied vs non-replied emails. Cadences require High Velocity Sales or Sales Engagement licences and must be built by users with the Cadence Creator permission.

Salesforce Inbox is a productivity tool that embeds Salesforce context directly into a rep's email client (Outlook or Gmail). Key features: (1) Salesforce records sidebar: Shows the related Account, Contact, and Opportunity record details alongside any email thread without switching to a browser. (2) One-click logging: Log emails to Salesforce records instantly from the inbox. (3) Insert Availability: Share calendar availability slots via a link so prospects self-schedule meetings — booked meetings are logged automatically. (4) Email Tracking: Notify reps when an email has been opened (requires Inbox licence). (5) Recommended Connections: Surfaces colleagues who have relationships with a contact to facilitate warm introductions. Salesforce Inbox is part of the Sales Cloud Einstein or Inbox add-on licence. It pairs with Einstein Activity Capture to ensure all email interactions are captured in the CRM without manual effort.

Salesforce's standard Contract object is related to an Account and tracks the terms of a legal agreement (start date, end date, contract term, status, billing/shipping address). Key workflow: (1) Contracts are commonly created from a Closed Won Opportunity (via a button or automation) linking the contract to the associated Account. (2) Contract Status lifecycle: Draft → In Approval Process → Activated. Activated contracts become read-only unless re-opened. (3) Contract Line Items are not natively included in standard Sales Cloud but are available with CPQ. Without CPQ, related products or entitlements are tracked via custom objects or Notes & Attachments. (4) Entitlements and SLAs can be linked to contracts for service obligations. (5) Renewal automation can be built via Flow to create a new Opportunity when a contract approaches its end date. For complex contract lifecycle management (CLM), organisations typically integrate tools such as Docusign CLM or Conga Contracts.

Orders in Salesforce record what a customer has committed to purchase after an opportunity is won. Configuration: (1) Enable Orders in Setup. (2) Orders are created from an Account (and optionally from a Contract). Opportunity-to-Order automation is typically built via Flow or custom button. (3) Order Products mirror the opportunity products — each order product references a Price Book Entry. (4) Order Status: Draft → Activated. Activated orders are locked (unless the "reduction orders" setting is enabled for amendments). (5) Reduction Orders: Record the reduction or cancellation of order quantities. (6) Order data feeds downstream to invoicing, fulfilment, or ERP integrations. For advanced order management with amendments, renewal, and billing, Salesforce Order Management (a separate product) or CPQ with Billing extends the standard capability significantly.

Partner Relationship Management (PRM) enables organisations to manage indirect sales through a partner portal built on Experience Cloud. Key components: (1) Partner Accounts: Standard Accounts flagged as partner organisations via the "Enable as Partner" action, creating an associated partner user. (2) Partner Users: External users with Community/Experience Cloud licences who access the partner portal. Their access is governed by profiles, permission sets, and sharing rules. (3) Deal Registration: Partners submit opportunities (leads) for approval to avoid channel conflict. Approved deals give the partner exclusive rights to the deal. (4) Lead Distribution: Vendors push leads to partners via the portal. (5) Channel Manager: An internal user assigned to manage a partner account — visible on the partner's portal as their point of contact. (6) Market Development Funds (MDF): Track co-marketing budget allocations and claims through PRM. Requires Experience Cloud and PRM licences.

Pipeline Reports are typically Summary reports on the Opportunity object grouped by Stage, Close Date (month/quarter), Owner, or Account. Key fields: Amount, Expected Revenue (amount × probability), Forecast Category, Age, and Number of Days in Stage. A Pipeline Trend report using the Opportunity History report type shows how pipeline has changed over time — it captures a snapshot of key field values (Amount, Stage, Close Date, Probability) each time they change, enabling analysis of how deals have been updated, pushed, or pulled forward. Best practice: use Opportunity Forecast report type to see amounts by forecast category. For dashboards: a funnel chart of count of opportunities by stage and a metric showing total pipeline by close quarter are standard for sales leadership. The Opportunity History object must be enabled to preserve field change history for trending analysis.

Duplicate Management for Leads and Contacts operates through two layers: (1) Matching Rules: Define how Salesforce compares records to identify duplicates. Standard rules for Leads match on Email, Name + Company, or Name + Phone. Standard rules for Contacts match on Email or Name + Account. Custom rules can apply fuzzy matching (handles name variations) or exact matching. (2) Duplicate Rules: Define the action when a match is found during record creation or edit. For Leads, common actions include blocking save or alerting the rep to review the existing record. For Contacts, rules can also check for duplicate Leads (cross-object matching). Potential Duplicates component on the page layout shows matched records so reps can review before proceeding. Duplicate record sets store references to identified duplicates for later bulk review and merging. Standard merge is available for Leads (merges up to 3), Contacts (up to 3), and Accounts (up to 3). Merged records consolidate related records onto the winning record.

A Sales Console is built using the Lightning App Builder as a Lightning Console App. Configuration: (1) Split View: Enables a side panel showing a list view while working on a record, allowing reps to navigate records without leaving the current context. Enabled in App Manager when creating or editing the Lightning Console App. (2) Workspace Tabs: Define which objects appear as primary tabs in the console (e.g., Accounts, Opportunities, Leads). Each workspace tab can have sub-tabs. (3) Related List Quick Links: A component added to the record page layout that shows counts for related lists (Contacts, Opportunities, Activities) as clickable links — avoids scrolling. (4) Utility Bar: A persistent footer bar for utilities like Open CTI softphone, History, Notes, or Macros. (5) Navigation Rules: Control whether related records open in the same workspace tab, a new tab, or a new window. Assign the console app to the relevant profiles/user segments.

Salesforce offers two integration paths for email clients: (1) Salesforce for Outlook (legacy): A desktop plugin (being retired) that synced Contacts, Events, and Tasks between Outlook and Salesforce. It required client-side installation and could conflict with email security policies. (2) Lightning for Outlook / Lightning for Gmail (Salesforce add-in): The modern, web-based add-in that runs inside Outlook (desktop and web) or Gmail as a sidebar. It shows related Salesforce records for the open email, allows one-click logging, and lets reps create or update records without leaving their inbox. Configuration: Enable via Setup > Email > Email Integration; deploy the add-in to users via Microsoft 365 Admin Centre or Google Workspace Admin Console. (3) Einstein Activity Capture complements the add-in by automating background sync of emails and calendar events. Key distinction: the add-in is for manual, in-context actions; EAC is for automatic background capture.

Mobile configuration for sales teams involves: (1) Mobile Navigation: Configure the navigation menu in Setup > Salesforce Mobile App > Navigation. Add objects (Accounts, Opportunities, Leads), apps, and utilities in the order reps will use them most. (2) Compact Layouts: Define the 4–5 fields shown in record headers and list item previews on mobile. Configured per object and assigned to record types. For Opportunities, surface Stage, Amount, and Close Date. (3) Global Quick Actions: New Task, Log a Call, New Event, and New Opportunity quick actions should be in the global publisher layout so reps can capture information on the go without opening a full record. (4) Object-Specific Quick Actions: Custom actions (e.g., Update Stage, Schedule Follow-up) can be surfaced on the action bar of specific objects. (5) Mobile-Specific Lightning Pages: Use Lightning App Builder to create phone-form-factor pages that show the most relevant components without the clutter of the desktop layout. (6) Offline: Enable offline access for key objects so reps can view and edit records without connectivity.