Skip to main content

Use lead scoring in lemlist

Score each lead in a campaign from its email, LinkedIn, WhatsApp and SMS activity and from AI reading of its replies, then sort, filter and branch your sequence on that score.

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. Lead score is calculated per campaign. For one score per contact across all campaigns, including points from your Signal agents, see Track a contact's overall engagement with the contact score.


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 or LinkedIn actions 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 across email, LinkedIn, WhatsApp and SMS, and as AI reads their replies.

The values in the 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

The lead scoring settings are grouped in four sections:

Section

What it covers

AI

AI analysis: AI reads incoming replies for tone-based lead scoring.

Activities

Email: Email sent, Open, Clicked on a link, Replied. LinkedIn: Linkedin sent, Linkedin InMail sent, Invite acceptation, Open a conversation, Replied to a message. WhatsApp: Replied to a message, Opened message, Opened voice note, Replied to a voice note. SMS: Replied to sms.

Downgrade

Score decays over time: if a lead takes no action for 3 days, their score starts to drop by 3% each day. It never goes below 1, and a new action restores the full score.

Negative

Email: Not delivered (Bounced), Unsubscribed. WhatsApp: Message failed, Voice note failed. SMS: Sms failed. API: Unsubscribed.

Signals from your Signal agents (job change, website visitors, hiring and others) do not change the lead score. They add points to the contact score.


What you can and can't do

You can:

  • Turn each event on or off in the lead scoring settings

  • Change the points of each event, or reset it to its default

  • Turn AI analysis off. When it is off, reply content is never sent to the AI provider.

  • Use the score operationally by sorting and filtering leads and tasks

You can't currently:

  • Add events of your own to the lead score

  • 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 the lead scoring settings

Click your profile in the bottom-left corner, then select Settings.

Screenshot showing the profile menu opened from the bottom-left avatar with Settings selected.

In the settings sidebar, under Team settings, click Data management, open the Scoring tab, then select Lead scoring at the top right of Score calculation. Review the events and the points assigned to each one. These values tell lemlist which events should matter more or less when calculating the final score.

Screenshot showing the settings sidebar with AI lead scoring selected and the scoring configuration page open.

Step 2: Review and adjust event weights

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. To go back to the default value of an event, click the reset icon next to its points.


Step 3: Enable only the events you want included

Turn events on or off based on what matters in your workflow. For example, if your team doesn't use LinkedIn, WhatsApp or SMS steps, turning off those events keeps the score 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.

Screenshot showing the Campaigns page with a campaign selected.

Inside the campaign, click Leads list. You'll see a Lead score column directly in the list so you can compare leads at a glance.

Screenshot showing the campaign Leads list with the Lead score column visible.

Step 6: Filter leads by score to focus on the most engaged ones

Click Filters, 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.

Screenshot showing the campaign lead list filters with Lead score selected and score ranges displayed.

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 from the task list toolbar. This opens your available task and lead-based filters so you can narrow the queue to the most relevant work first.

Screenshot showing the Tasks page with the Filters button highlighted.

Step 8: Add a Lead score filter

Click the + button in the active filter bar, then choose Lead score. This adds lead score as a filter condition for your task list.

Screenshot showing the task filter bar with the plus button opened and Lead score selected.

Step 9: Choose the score range you want to work from

Select the score band you want to focus on, such as 91 to 100, 71 to 90, 51 to 70, or 0 to 50, then apply the filter. This helps you work the highest-priority tasks first without checking every lead one by one.

Screenshot showing the Lead score filter options in the task list.

You can also hover over a lead's score in the task list to view the activity breakdown behind that score and get more context before taking action.

Screenshot showing a lead score tooltip in the task list with the activity breakdown.

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 events 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, event combinations, AI reading of replies, and decay after inactivity.
Fix:

  • Check which events are turned on in the lead scoring settings

  • Review the lead's activity breakdown to understand what contributed

  • Check whether one of the leads has been inactive for more than 3 days: its score decays by 3% a day

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 events like clicks and replies when setting weights

  • Use the score range operationally instead of expecting exact per-event math

Issue: A signal like a job change or a website visit didn't change the lead score
Root cause: Signals from Signal agents don't count toward the lead score. They add points to the contact score.
Fix:

Issue: I want to manually edit or override a lead's score
Root cause: Manual overrides are not currently supported.
Fix:

  • Adjust enabled events and their relative weights instead

  • Use filters and workflow rules around the computed score

  • Treat the score as a system-calculated prioritization layer

Did this answer your question?