Fabrikam's Lead Triage Overload
Fabrikam receives 4,200 leads per month from three web forms, a trade show app, and inbound email. Leads are created in Dynamics 365 Sales with no owner, and a shared mailbox is used. Sales accelerator is enabled, but only 9 sellers use it. Symptoms: 1,800 leads sit unassigned for more than 48 hours; duplicate leads arrive from repeated form submissions; lead scores are not updating; sequences stop after the first email; sellers complain about too many irrelevant leads. Constraints: no custom code; one sequence per record; business hours are 8-5 Eastern; the solution must use out-of-box lead scoring and sales accelerator; data quality must improve without deleting leads. Managers want high-score leads routed to a senior team and low-score leads placed in a nurture sequence. They also want to prevent duplicates by email and phone.
1. Configure a lead scoring model and explain why lead scores may not be updating.
Read the worked answer
Reasoning: Lead scoring in Dynamics 365 Sales combines a demographic model and a behavioral model. The demographic model scores fit attributes such as industry, company size, or source; the behavioral model scores actions such as email opens, website visits, and event attendance. Both models must be published, and the lead must be active for the score to attach. If scores are not updating, check that Sales Insights is enabled, the scoring models are published rather than draft, and the lead has not been disqualified or merged. Behavioral scoring depends on data being processed from connected sources; if activities are not tracked, the behavior score stays flat. Also verify that the scoring model has had time to process and that the lead's fields are populated; blank fields may receive zero points. Do not create a separate custom score field, because the out-of-box score and grade fields drive work lists and automation.
2. Design routing and sequence assignment for high-score and low-score leads while respecting the one-sequence limit and business hours.
Read the worked answer
Reasoning: Because a record can be in only one sequence at a time, do not try to assign two sequences to the same lead. Build one sequence with branch steps: a high-score branch that creates a task for a senior seller and sends a personalized email, and a low-score branch that sends a nurture email and waits several days. Use sales accelerator assignment rules to route leads by score, territory, or seller capacity rather than manual assignment. Set the sequence's business hours to 8-5 Eastern so that wait steps and email sends occur only during working hours. For high-score leads, route to the senior team's work list; for low-score leads, assign to the nurture queue. If a lead's score changes, the record stays in its current sequence; the branch condition should be evaluated at the step where it matters. Test with a high-score lead and a low-score lead to confirm routing and sequence progression.
3. Recommend a duplicate detection strategy and lead qualification mapping that improves data quality without deleting leads.
Read the worked answer
Reasoning: Enable duplicate detection rules for Lead on Email and Phone, publish them, and turn on duplicate detection during create and update. When a duplicate is found, present the match and use merge rather than delete so that activity history and source details are preserved. For repeated web-form submissions, consider using the same email as the primary match key and normalize phone numbers before comparison. For qualification, map lead fields to Account, Contact, and Opportunity so that data carries forward: company name to account name, contact name and email to contact, estimated value to opportunity, and source to lead source. If a matching account already exists, qualify to that account instead of creating a duplicate. Review the mapping with the sales team and test with a lead that has a known account and a lead that is new.