Lead Routing and Duplicate Management for a 12-Person Solar Installer
SunHarvest Solar is a 12-person residential solar installer using Sales Cloud. They generate about 400 leads per month from three sources: website forms (200), a home-show booth (100), and a purchased list (100). Two sales reps, Maya and Devon, split leads by territory: Maya covers the north, Devon the south. The operations manager notices that 18% of leads have duplicate email addresses, and that leads from the purchased list are often assigned to the wrong rep because the list lacks a state field. Reps complain they lose time manually checking duplicates. They want to automate assignment and deduplication. They have Sales Cloud Enterprise and two Sales Cloud licenses. They are considering a third-party dedupe app but have a tight budget.
1. What is the most appropriate way to handle duplicate prevention and lead assignment within native Sales Cloud, given the budget constraint?
Read the worked answer
Reasoning: The core issue is duplicate leads (18% with duplicate emails) and misassignment due to missing state data on purchased leads. Native Salesforce provides duplicate rules and matching rules for deduplication, and lead assignment rules for routing. Since the purchased list lacks state, assignment rules based on state will fail for those leads. The team should first clean the purchased list to append state before import, or use a default assignment queue for unassigned leads. Duplicate rules can block or alert on duplicate emails at creation. Since they have Enterprise Edition, duplicate rules are available (they are available in Professional and above). A third-party app is unnecessary if they configure native duplicate rules and assignment rules. However, assignment rules cannot route based on a missing field; they need a fallback. Also, leads from the home-show booth might be entered manually and could be subject to duplicate rules. The budget constraint means avoid paid apps. So the answer: enable duplicate rules with a matching rule on Email, set to alert or block; create lead assignment rules with territory logic, but for purchased leads lacking state, either enrich data before import or assign to a queue for manual review. Also, consider using Web-to-Lead for website forms to auto-create leads, and use a lead import wizard with duplicate prevention. The key is native configuration, data quality step, and fallback assignment.
2. How should the team measure the effectiveness of the duplicate rules and assignment rules after implementation?
Read the worked answer
Reasoning: To measure effectiveness, they need metrics before and after. Before: 18% duplicate email rate, and misassignment rate (not quantified but can be measured by rep complaints or by auditing a sample). After implementing duplicate rules, they can run a duplicate report to see how many duplicates are being blocked or flagged. They can also track the number of leads created vs. number of duplicates prevented. For assignment, they can report on lead owner and compare to territory; for purchased leads, they can track how many went to the fallback queue and how quickly they were reassigned. Key metrics: duplicate rate (target reduction from 18% to <5%), assignment accuracy (percentage of leads assigned to correct rep based on state), time to assignment, and rep satisfaction. Use standard reports: Leads by Owner, Leads with Duplicates, and custom report on lead source vs. owner. Also, set up a dashboard for the operations manager. Since they have Enterprise, they have reporting and dashboards. They should also monitor lead conversion rates to ensure no leads are lost due to over-blocking.