Connects an incoming Lead to the right existing Account. This capability uses two rules working together — a strict one and a looser one. Both trigger when a Lead is saved and compare it against your Accounts (Company → Account Name, Website → Website, Phone → Phone, Lead address → Billing address).
Rule #1 — the strict check
If the Lead's company name is an exact match for an Account's name, that's the Account.
# | Field | Matching method | Blank value behavior |
1 | Name | Exact | Null Not Allowed |
Filter logic: Single criterion — no boolean filter.
A Lead matches an Account when the Lead's Company exactly equals the Account's Name. This is the highest-confidence signal, and it works even when the Lead has no other organizational data filled in.
Rule #2 — the looser check
Catches the matches Rule #1 misses: the company name only needs to be a loose match, supported by exact details like the website, phone number, or billing address.
# | Field | Matching method |
1 | Name | Fuzzy: Company Name |
2 | Website | Exact |
3 | Phone | Exact |
4 | BillingStreet | Exact |
5 | BillingCity | Exact |
6 | BillingCountry | Exact |
7 | BillingState | Exact |
8 | BillingPostalCode | Exact |
Filter logic:
1 AND (2 OR 3 OR 4 OR (5 AND 6 AND 7 AND 8))
A fuzzy company-name match on its own is never enough — it must be backed up by at least one corroborating signal. In plain terms, a Lead matches an Account when the Company/Account Name matches (fuzzy — e.g., "Acme Inc." vs. "Acme Incorporated"), plus at least one of the following:
Same Website, or
Same Phone, or
Same Street, or
Same full location: City + Country + State + Postal Code
This additional matching requirement is what prevents false positives from generic or similar-sounding company names, while still extending coverage to the name variations Rule #1 would miss.