---
title: "Lead assignment rules and lead scoring"
url: "https://trailassembly.com/lead-assignment-and-scoring/"
topic: "Admin and Permissions"
published: "2026-09-16T03:13:01+00:00"
updated: "2026-10-06T13:56:11+00:00"
---

# Lead assignment rules and lead scoring

**The short answer:** one [assignment rule](https://trailassembly.com/case-assignment-rules/) is active at a time, its entries are evaluated in order, and the first match wins. If nothing matches, the lead goes to the Default Lead Owner and nobody hears about it. That silent fallback is the same failure cases have, and it is where leads go to be forgotten.

## How the rule actually evaluates

An assignment rule is a container of ordered rule entries. Each entry has criteria (or a formula), a target owner that is a user or a queue, and an optional [email template](https://trailassembly.com/salesforce-email-templates/). Evaluation stops at the first entry whose criteria are true.

Order is therefore the logic. An entry matching Country equals United Kingdom placed above one matching Industry equals Financial Services means UK financial services leads never reach the second entry. Reading from the top and asking what each entry steals from the entries below it is the only reliable review.

Formula entries are underused. One can express what four criteria entries would, reference related fields and do arithmetic. The cost is that the formula is invisible in the [list view](https://trailassembly.com/salesforce-list-views-and-filters/), so a rule mixing both styles reads worse than one that picks a side.

## When the rule runs, and when it does not

This is the part that catches integrations.

- **UI creation:** only if the “Assign using active assignment rule” checkbox is ticked on the layout. You can force it on by default in Lead Settings.

- **Web-to-Lead:** always runs the active rule.

- **API and Apex:** only if the request asks for it.

- **Flow:** record-triggered flows creating leads do not run assignment rules unless you set the header, which flow cannot do directly. This usually means an Apex-invocable action.

```apex
Database.DMLOptions opts = new Database.DMLOptions();
opts.AssignmentRuleHeader.UseDefaultRule = true;
Lead l = new Lead(LastName = 'Okafor', Company = 'Acme');
l.setOptions(opts);
insert l;
```

Without those three lines, an integration inserting ten thousand leads assigns every one of them to the integration user. That is the single most common lead routing bug and it produces no error at all.

## The silent no-match

When no entry matches, ownership falls to the Default Lead Owner in Lead Settings. The lead is created, assignment “succeeded”, and the record sits in a user or queue that exists for exactly this reason and that nobody has a list view for.

Make the fallback loud. A final catch-all entry with criteria that are always true, pointing at a named Unrouted queue, plus a morning report on leads owned by it. A deliberate catch-all also documents the rule, because the last entry tells the next admin what the author expected to go unmatched.

## Queues

A queue is a shared inbox with an owner Id. Assign a lead to a queue and it appears in that queue’s list view until a member accepts it, which transfers ownership to them.

Queue membership takes users, public groups, roles and roles-and-subordinates. Use public groups. Individual users in queues make every joiner and leaver a production edit. A group is one place to change.

Queue ownership grants access to the record for members regardless of [sharing rules](https://trailassembly.com/sharing-rules/), which is the mechanism people forget when auditing who can see what.

## Scoring approaches, ranked

**A formula field** is the honest starting point. Points for job title, company size, country, product interest, summed into a number. It is transparent, changeable in five minutes, and marketing can argue with it productively because they can read it.

**Einstein Lead Scoring** learns from your converted and unconverted leads and scores against that history. It needs enough closed history to learn from, and it refuses to run rather than producing a bad model when there is not enough. Its real value is the field-level reasons it surfaces alongside the score.

**Behavioural scoring** from a marketing automation tool measures engagement rather than fit. It answers a different question from the other two and the two together beat either alone.

What does not work is a hand-built scoring flow with thirty decision branches maintained by one person. It goes stale, nobody trusts it, and eventually the reps ignore the score and sort by created date.

## Frequently asked

**Can two assignment rules be active?** No, one per object. Multiple business processes means multiple entries in one rule.

**Do rules run on update?** Not on their own. Re-running assignment on an existing lead means an Apex update with the header set, or the reassign option where it appears.

**Does the assignment email always send?** It sends when the matching entry names a template. Leave it blank and assignment happens silently, which is often what you want for queues with their own list views.

**Should a score drive assignment?** Only if the score is calculated before insert. A formula field works. A flow that stamps a score after insert has already missed the rule.

---

Source: https://trailassembly.com/lead-assignment-and-scoring/
Trail Assembly — independent Salesforce write-ups.