Lead scoring in Salesforce works best as two separate measures: fit, meaning how closely a lead matches the customers you win, and engagement, meaning how much interest it has shown recently. You can calculate both with formula fields and Flow, with the scoring and grading built into Marketing Cloud Account Engagement, or with Einstein's AI scoring, which learns from your converted leads. Whichever method you pick, the score only pays off once it changes who gets a lead, how fast, and what happens next.
Fit and engagement are different questions
A single blended number hides the reason a lead ranks high. A student who downloads every guide can outscore a plant manager at a target account who filled in one form, and reps learn quickly to ignore a number that sends them to the student. Keeping fit and engagement apart lets you read a lead at a glance: strong fit with low engagement belongs in nurture or targeted outreach, weak fit with high engagement may need a qualifying question, and strong on both goes to a rep today.
Fit comes from attributes: industry, company size, role, region, and whether you actually serve that use case. Engagement comes from behavior: form fills, email clicks, pricing-page visits, event attendance and replies. Fit changes slowly and can be checked against closed-won history. Engagement changes daily and should fade over time, because a burst of activity from last spring says little about intent now.
A business lender we worked with received 24,000 leads a month, while its sales team could work roughly 3,000 a month. The answer was a dual-tier model: a lead grade for fit and a lead score for progress through the application, so reps started each day with the candidates most likely to be worth their time.
Three ways to build a score
| Rules in Sales Cloud (fields and Flow) | Account Engagement scoring and grading | AI scoring (Einstein) | |
|---|---|---|---|
| What it measures | Whatever you define, usually fit plus a few key actions | Score for engagement, letter grade for fit | Likelihood to convert, learned from past conversions |
| Where the data comes from | Lead fields and logged activity you already track | Tracked email, form and website behavior plus profile criteria | Historical lead fields and activity in your org |
| Transparency | Complete; every point is a rule you wrote | High; rules and criteria are visible to admins | Shows top positive and negative factors per lead |
| Needs | An admin to build and maintain it | Account Engagement and a working connector | The right edition or add-on, and enough conversion history |
| Good first choice when | Volume is modest and the ideal customer is clear | Marketing already runs campaigns in Account Engagement | You have years of consistent lead and conversion data |
Rule-based scoring in Sales Cloud is usually a set of number fields, one for fit and one for engagement, updated by record-triggered Flows or formulas. Keep the logic in one place, document every weight, and put a scheduled Flow in charge of reducing engagement points for leads that go quiet. It is the easiest method to explain to reps, and the easiest to let drift if nobody owns it.
Account Engagement already separates the two measures: prospects collect score points from activity and receive a grade from profile criteria. Our Account Engagement setup guide covers how scoring and grading are configured; the point here is that the score and grade sync to the lead or contact, so routing and reporting in Sales Cloud can use them directly.
Salesforce's AI options learn patterns instead of taking weights from you. Einstein Lead Scoring studies past converted leads, including custom fields and activity data, and falls back to a global model built from anonymized data across Salesforce customers until your org has enough history of its own. Account Engagement also offers Einstein Behavior Scoring, which rates engagement on a 0 to 100 scale and builds in decay. Feature names and packaging change often, so confirm what your edition and add-ons include before you plan around a specific AI score.
Routing on the score
A score that only appears on the record is decoration. Decide which combinations trigger a handoff, then build the routing so the handoff happens without anyone checking a list view. Assignment rules and queues handle ownership; a record-triggered Flow can watch for a lead crossing the threshold, change its status, assign it and create a follow-up task with a due date.
- Write the handoff as a rule both teams signed, such as a grade of B or better and a score above the agreed line.
- Send leads that meet the threshold to a named rep or a monitored queue, never to a catch-all user.
- Route strong-fit, low-engagement leads to targeted outreach or nurture rather than straight to a rep.
- Hold weak-fit, high-engagement leads for a qualifying step so reps are not chasing researchers and students.
- Create the first task automatically, with the due date set by your response-time commitment.
- Record the score and grade at the moment of handoff in separate fields, so later reviews can compare them with outcomes.
Service levels between marketing and sales
A threshold is a promise in both directions. Marketing commits to sending leads that meet the agreed definition; sales commits to working them within an agreed time and recording what happened. Set the response window by lead tier, not one number for everything, because a demo request deserves a faster reply than a content download that just tipped over the line.
Make the commitment visible. Add a first-touch timestamp populated by the first logged call, email or task, and report the gap between assignment and first touch by rep and by tier. Give leads that sit untouched past the window an escalation path: a reminder to the owner, then reassignment or a notice to the manager. Require a disposition when a rep rejects a lead, with reasons such as wrong contact, no budget or competitor, because those rejections are the best evidence you will get about whether the model works.
Reviewing and adjusting the model
Treat the first version as a hypothesis. After a quarter, pull every lead that crossed the threshold and compare conversion to opportunity and closed-won rates by grade and score band. If high-scoring leads convert no better than mid-scoring ones, the engagement weights are rewarding the wrong actions. If a grade band converts well but rarely reaches sales, the threshold is too strict, or those leads are stuck in nurture.
Look at rejections next. A cluster of wrong-contact rejections usually points at fit criteria that reward the company without checking the role, while a run of not-ready rejections suggests engagement is counting activity that signals research rather than buying. Change one thing at a time, record what changed and when, and review again the following quarter. Einstein models retrain on their own, but the same review still applies: check whether top-scored leads actually convert, and whether the factors Einstein shows make sense to the people selling.
Give the model an owner, typically in revenue operations or a senior admin, with a standing review that includes one marketing lead and one or two reps. Tie the review to a report pack built for it: conversion by band, time to first touch, and rejection reasons. Scoring stays useful when those three numbers are looked at together on a schedule.
