Partner leads go to the general queue.

Where it goes wrong

• A general entry sits above the partner entry. Salesforce stops at the first match. See which entry wins.
• The source is spelled several ways. Partner, Partner referral and partners are three values. Test whether case matters in your org.
• A portal or form creates the lead. Check who owns leads made that way. See leads owned by the integration user.
• One entry serves every partner. A rule by source alone sends all partners to one queue. It cannot reach each partner's manager.
• The partner registered a lead you already hold. The duplicate may go to a different rep. See duplicate leads.

Count it yourself

SELECT LeadSource, COUNT(Id) n FROM Lead WHERE CreatedDate = LAST_N_DAYS:90 AND LeadSource LIKE '%artner%' GROUP BY LeadSource

Each spelling in the result needs an entry, or one entry listing them all. Then group the same leads by owner.

SELECT OwnerId, COUNT(Id) n FROM Lead WHERE CreatedDate = LAST_N_DAYS:90 AND LeadSource LIKE '%artner%' GROUP BY OwnerId

If one owner Id holds most of them, check it is who you meant.

The free scan checks your export for:

• entries hidden behind broader ones
• entries that can never match
• values not in the picklist

No export access? Paste your rule entries instead.

A worked example

A made-up result of the first query: Partner 40, Partner referral 15, partners 6. The rule has one entry for the exact value Partner.

Check whether your org matches case. Either way, the 15 Partner referral leads match nothing, so they reach the general queue.

List the values in one entry, Partner and Partner referral. Then check the second query. If one owner Id holds all 61 leads, ask whether a single person manages every partner. If not, split by partner.

Steps

1. Run the grouped count and list every spelling.
2. Put all of them in the partner entry.
3. Place that entry above any general entry.
4. Run the owner count. Check it matches who manages each partner.

A partner map to keep

Keep one row per partner. Use the same table to write the entries. See entry order for where each row goes.

This table is made up. If two partners share a source value, the source alone cannot split them. Add a field that names the partner.

Questions to settle first

Settle these before you write an entry. See duplicate leads for partner leads you already hold.

• Which field names the partner on the lead?
• Who sets it: the form, the partner or a rep?
• What happens when the partner is not in the map?
• Who updates the map when a partner joins?

Without an answer to the first question, no rule can reach the right manager.

Questions

Why do partner leads go to the general queue?

A general entry above the partner entry wins. Salesforce stops at the first match. The source may also be spelled several ways.

How do I list the partner source spellings in use?

Group the last 90 days of leads by lead source, filtered to values containing partner. Each spelling needs an entry, or a place in a list.