# Write lead scoring rules: points for what a customer says and does

> Add points when a lead does something, write the rule as a condition or in plain words, and read the breakdown behind every score.

Source: https://www.linkubit.com/docs/lead-scoring-rules  
Section: Linkubit help centre › Leads, pipeline and automations  
Updated: 2026-10-17

## In short

Pipeline › Setup › Scoring rules adds or subtracts points while a condition holds, and the score is the plain sum of the rules that match — with each rule's contribution recorded so you can always see why. A score of 70 and up is Hot, 40 and up Warm, below 40 Cold. On Pro and Scale a rule can also be described in words, at 0.1 credit per reply.

## Add a rule

1. Open **Pipeline › Setup › Scoring rules** and press **New scoring rule**.
2. Fill the **Label** (shown in the score breakdown — keep it readable) and the **Key** (a short identifier like engaged_5_messages, unique in the workspace).
3. Under **When**, build the condition (below).
4. Set **Points**, from −100 to 100. Negative points push a lead down — a disqualification, say.
5. Leave **Active** on (an inactive rule adds nothing) and press **Create scoring rule**.

## Structured conditions

Choose **Structured**, then **all of these match** or **any of these match**, and **Add condition**. Fields come in groups — **What they've done** (signals), **What they told you**, **Their company**, **Contact** and **Your fields** — with operators such as is, is not, is more than, is at least, is any of, includes, and has been collected.

| Signal | What it measures |
| --- | --- |
| Messages from them / to them | How many each way |
| Conversations | How many they have had |
| Channel used | WhatsApp, email, Instagram or Messenger |
| Days since they last wrote | Recency |
| Goal completed / Goals completed | Which goals, and how many |
| Product sent to them / Products sent | What you have shared |
| Qualification class, Lead source | High, medium, low or disqualified; where they came from |
| Replied to a campaign, Payment requested, Paid | Yes or no |

## Described in words (Pro and Scale)

Choose **Described in words** and write the condition: "The customer said their budget is approved and they want delivery in Mumbai" (10 to 400 characters). The agent answers it as it reads the conversation, and the answer sticks once it is yes. It costs 0.1 credit per reply however many such rules you have, a workspace may have ten active, and a conversation a person took over isn't read — use a structured rule over the signals for those. Editing or deleting the rule clears its stored answers.

## Where the score shows

As a **Score** column on Contacts and Leads, on a contact's page, and beside the conversation in the inbox, labelled Hot, Warm or Cold. A workflow can react to it — the starter set qualifies a lead at a score of 40 ([how](https://www.linkubit.com/docs/pipeline-scoring-and-workflows)).

## Related
- [Pipeline stages, scoring and workflows](https://www.linkubit.com/docs/pipeline-scoring-and-workflows)
- [Contacts, companies, leads and deals](https://www.linkubit.com/docs/contacts-companies-leads)
- [Edit your AI agent in plain words](https://www.linkubit.com/docs/edit-your-agent)
