By the end of this tutorial, you'll know how to configure lead scoring, use it to prioritize follow-up in your campaign lead list and task list, and apply score-based logic in your outreach workflow.
Why this matters
Lead scoring helps you quickly identify which leads are showing the strongest buying or reply intent, so you don't have to manually check opens, clicks, replies, LinkedIn actions, or other signals one by one. Instead of guessing who to follow up with next, you can sort and filter by score and focus on the most engaged leads first.
Prerequisites
You should already know the basics of running a campaign in lemlist
You should already have at least one active campaign or leads with tracked activity
You should have Admin access to your workspace to manage lead scoring settings
How lead scoring works
Before changing any settings, it's important to understand what the score actually means.
Lead scoring is a prioritization signal, not a guaranteed, manually calculable points total.
The score is dynamic and updates automatically as leads interact with your outreach. That includes email engagement, LinkedIn engagement, and other intent signals that may be active in your workspace.
The values in Lead Scoring settings act as relative importance or weighting. They do not mean every event adds a fixed number you can sum like a spreadsheet.
As a result:
Two leads can perform similar actions and still end up with different scores
A lead opening multiple times does not necessarily gain score in a perfectly linear way
Replies are generally treated as stronger signals than opens or clicks
The final score is calculated automatically and may not match a simple manual sum
What impacts the score
Depending on what your workspace uses, lead scoring can take signals from the following categories into account:
Category | Examples |
Email engagement | Opens, link clicks, replies |
LinkedIn engagement | Connection invite acceptance and other LinkedIn interactions used in campaigns |
Deeper intent signals | Job change, company change, broader LinkedIn activity, website visits |
Other enabled sources | Additional external or CRM-style events, depending on your workspace setup |
Not every workspace uses every signal. If a related product or feature is not enabled, that signal won't affect the score.
What you can and can't do
You can:
Enable or disable the signals exposed in Lead Scoring settings
Adjust how important each available signal is relative to the others
Use the score operationally by sorting and filtering leads and tasks
You can't currently:
Create brand-new custom signals from scratch
Precisely audit the final score as a strict additive formula
Manually override the computed score for an individual lead
Phase 1: Configure lead scoring
Step 1: Open Lead Scoring settings
Click your workspace avatar in the bottom-left corner, then select [Settings]. This is where workspace-level scoring behavior is managed.
In the settings sidebar, click [Lead scoring]. This opens the configuration page where you choose which engagement signals matter in your workspace.
Step 2: Review and adjust signal weights
On the Lead scoring page, review the available signals and the value assigned to each one. These values tell lemlist which signals should matter more or less when calculating the final score.
Use these values as weights, not fixed points. For example, giving replies a higher value than opens tells lemlist that a reply is a stronger sign of interest, but it does not guarantee a simple “+X” increase every time a reply happens.
Step 3: Enable only the signals you want included
Turn signals on or off based on what matters in your workflow. For example, if your team doesn't use LinkedIn steps or website visitor tracking, disabling those signals can keep the score more aligned with the activity you actually care about.
Step 4: Set expectations before you use the score
Once configured, the score updates automatically as lead activity changes. Use it as a fast prioritization layer, then check the activity breakdown when you want context on why a lead ranks higher.
Phase 2: Use the score in your campaign lead list
Step 5: Open a campaign and go to the lead list
Go to [Campaigns], then open the campaign you want to review. This is the fastest place to see which leads inside a specific campaign are most engaged.
Inside the campaign, click [Lead list]. You'll see a Lead score column directly in the list so you can compare leads at a glance.
Step 6: Filter leads by score to focus on the most engaged ones
Click the filter icon, choose [Lead score], and select the score range you want to review. This is especially useful when you want to focus only on the hottest leads instead of scanning the full list manually.
Use the score as a prioritization shortcut: start with the highest-score leads for personal follow-up, call tasks, or faster handoff.
Phase 3: Use the score in your task list
Step 7: Open the task list
Go to [Tasks], then click [Filters]. This lets you narrow your task queue to the leads that matter most right now.
Step 8: Add a Lead score filter
Click [Add a filter], then expand [Lead]. Lead-level filters let you prioritize tasks based on the associated lead's engagement.
Select [Lead score]. This tells lemlist you want to filter tasks using the lead's computed engagement score.
Step 9: Choose the score range you want to work from
Choose a score band such as 91 to 100, 71 to 90, 51 to 70, or 0 to 50. These ranges help you operationalize the score without having to inspect every lead individually.
After applying the filter, your task list updates to show only tasks tied to leads in that score range. This is a good workflow for working high-intent leads first.
Phase 4: Use score-based logic in sequences
You can also use lead score inside campaign sequences to adapt the path a lead takes based on interest level.
Step 10: Add a Lead score condition
In your campaign sequence builder, add a Lead score condition. Set the score threshold you want a lead to reach, and, if needed, define a timeframe for how long the system should wait before evaluating that condition.
Use this when you want the sequence to react differently depending on engagement. For example, a highly engaged lead can move to a stronger call-to-action, while a lower-score lead can stay in a lighter nurture path.
Practical application
Here's a simple way to use lead scoring in a real workflow:
Give replies and strong engagement signals more weight than opens
Review your campaign lead list daily to spot leads rising in score
Use the task list filter to work medium- and high-score leads first
Add a Lead score condition in sequences so interested leads get faster, more direct follow-up
A practical example: if a lead opens, clicks, and then replies, their score will usually rise enough to move them above leads who only opened emails. That makes it easier to focus your next manual action on the lead showing stronger intent.
Troubleshooting & pitfalls
Issue: The score doesn't match the values I set in settings
Root cause: The settings act as relative weights, not as a strict additive formula.
Fix:
Treat the configured values as importance, not guaranteed “+X points” events
Compare the lead's activity history instead of trying to manually total the score
Use the score to prioritize, not to audit exact math
Issue: Two leads with similar actions have different scores
Root cause: Scores are dynamic and can reflect different timing, signal combinations, and enabled workspace features.
Fix:
Check which signals are enabled in Lead Scoring settings
Review the lead's activity breakdown to understand what contributed
Expect differences when one lead has stronger or more recent intent signals
Issue: A lead opened multiple times but the score didn't grow as expected
Root cause: Multiple interactions of the same type do not necessarily increase the score in a perfectly linear way.
Fix:
Don't interpret the score as a simple per-open counter
Prioritize stronger signals like clicks and replies when setting weights
Use the score range operationally instead of expecting exact per-event math
Issue: I don't see expected signals affecting the score
Root cause: Some signals depend on additional products or features being enabled in the workspace.
Fix:
Confirm the signal is available and enabled in Lead Scoring settings
Verify the related setup exists, such as website tracking or Signals features
If the workspace doesn't use that feature, that signal won't contribute to scoring
Issue: I want to manually edit or override a lead's score
Root cause: Manual overrides are not currently supported.
Fix:
Adjust enabled signals and their relative weights instead
Use filters and workflow rules around the computed score
Treat the score as a system-calculated prioritization layer











