CRM data quality · route on the account, not on the form

Lead routing starts with the right account

The short answer

Lead routing assigns each new lead to the person or team that should follow up. It only works once the lead is matched to the right account: identify the person behind the email, take the company page of their current job, check whether that account already has an owner, and only then apply territory rules such as headquarters region, size and industry.

Updated
Read
7 min
On this page8 sections
  1. What is lead routing?
  2. Why does lead routing fail?
  3. In what order should lead routing decide?
  4. Which account does a lead with several current jobs belong to?
  5. How do you route leads by territory?
  6. What should happen to leads that match no rule?
  7. How do you get the routing fields with the API?
  8. Sources and method

A demo request comes in at 9:02. By 9:05 it should be with the rep who owns the account, or with the right territory if the company is new. Most of the time, the rules that decide are fine. What breaks is the field they read. Routing is where CRM data quality stops being a reporting problem and becomes a lost lead.

What is lead routing?

Lead routing is the step that sends each new lead to the person or team who should follow up, by rules rather than by hand.

Definition Lead routing also called lead assignment
Deciding automatically who should follow up on each new lead, and sending it to that person or team.

PreciselyLead routing assigns each new lead to an owner by rules: a lead from an account you already work goes to that account's owner, a lead from a new company goes to a territory or segment defined by attributes such as headquarters region, size and industry, and a lead that matches no rule goes to a review queue. Routing is only as good as the account match and the company attributes it reads.

Three outcomes cover almost every routing setup:

  • The lead’s company is already an account you work. It goes to the account’s owner, so that two reps never call the same company.
  • The company is new. It goes to a territory or a segment, defined by where the company is headquartered, how large it is, or what it does.
  • Nothing fits. It goes to a review queue, with what is known about it.

Why does lead routing fail?

Because it routes on what the lead typed, or on where the lead comes from, instead of on the account. Four failures come back again and again:

  • A typed company name. “Acme”, “Acme Inc.” and “ACME Corp” are three strings for one account, and a rule written for one misses the others.
  • An email domain that is not the account’s. A subsidiary or an acquired brand writes from its own domain, and personal addresses carry no company at all.
  • The lead’s own country. A person who lives in one country can work for a company headquartered in another. Route on the person, and the account gets a second owner in another territory.
  • Several current jobs. Advisors, board members and part-time founders hold more than one job at a time. Pick the wrong one, and the lead lands on a company that never asked for a demo.

None of these raises an error. The lead is routed, quickly, to the wrong place.

A fast route to the wrong owner is still a lost lead.

In what order should lead routing decide?

Account first, owner second. Here is how to route leads so that each decision reads a field rather than a guess, in four questions asked in this order:

  1. Who is it?ReadsReverse Email Lookupperson, experiences[]found: false → review queue
  2. Which account?ReadsThe current jobcompany_linkedin_idMatches an account → its owner
  3. Which territory?ReadsCompany Enrichmenthq.region, size, industryNew company → the territory rule
  4. Nothing fits?ReadsYour rulesno rule matchedReview queue, never a default rep
Four questions in a fixed order. Territory rules only run for companies that are not accounts yet.
  1. Who is it? Send the email to Reverse Email Lookup: it returns the person and every job they hold or held, each with the company ID of its company page when the company has one. No match, and the lead goes to review.
  2. Which account? Compare the company ID of the current job with the IDs on your accounts. The page on lead to account matching explains why this key holds where the email domain does not.
  3. Which territory? Only when no account matches. Read the company’s headquarters region, size and industry, and apply your territory rules.
  4. Nothing fits? A review queue, with the person and the company already identified.

The order matters because each step narrows the next. Territory rules that run before the account match can hand an existing customer to a new-business rep.

Which account does a lead with several current jobs belong to?

The one you already work, when there is one. On November 10, 2026, we looked up the work email of someone in revenue operations at Personio. The person holds several current jobs: a full-time role at Personio and part-time advisory roles at other companies.

Reverse Email LookupCurrent jobsPersonioID 10180448Full-timeAdvisory roles at other companiesPart-timeLives inEurope, outside Germany
The real lookup: several current jobs, one of them full-time and matching the account. The person lives elsewhere in Europe; the account is headquartered in Munich.

Three rules settle the case, in this order:

  1. A current job at a company you already have as an account wins. Here, the Personio job carries the ID 10180448, the same as the account. If more than one current job matches an account, apply the next rule to those jobs.
  2. Otherwise, the full-time job. When the response gives a contract type, an advisory role is usually marked part-time. The field can be empty, so a single current job needs no contract type to win.
  3. Otherwise, review. Two full-time jobs at two new companies is a question for a person, not for a rule.

The same lookup answers the territory question. The person lives in another European country; Personio is headquartered in Munich, Germany, in the EMEA region. A routing rule built on the lead’s location would send this lead to whoever covers the person’s country. Built on the account, it goes to the account’s owner, or to the EMEA territory if Personio were not an account yet.

How do you route leads by territory?

Define every territory on account attributes, read them from the company profile, and route each lead by its account. Company Enrichment returns the fields territory rules usually need:

  • Region and country: hq.region (NORAM, EMEA and so on) and hq.country_code, where the company is headquartered. The region can be empty: fall back to the country.
  • Size: size, a headcount band, and employees_on_linkedin, a count of employees on LinkedIn.
  • Industry: the company’s industry.

Pick one field per rule and keep it. A headcount band and a count of employees do not measure the same thing, and they can disagree. A segment rule that reads one field on Monday and the other on Friday moves accounts between reps for no reason.

What should happen to leads that match no rule?

They go to a review queue, with everything the lookup found, and they never go to a default rep. A default owner turns every unmatched lead into a pipeline nobody asked for, and hides the fact that a rule is missing.

  • The lookup found no one. The address may be personal, new or an alias. Keep the lead, mark it as unidentified, and ask for a work email in the first reply instead of creating an account from the domain.
  • The person was found, the company matches no rule. That is a gap in the territory map. Route by hand, then write the rule.
  • The person was found at a company you already own, but an old contact record says otherwise. Trust the current job, update the contact, and tell the account owner: a champion may have moved.

Routing is the last step of a short chain. The step just before it, qualifying the lead from its email, is on the page about inbound lead enrichment.

For builders

Two calls give routing its fields: one identifies the person and their current jobs, one describes the account. This part shows both on the real lookup, and an example of rules that read them.

How do you get the routing fields with the API?

POST/v2/enrichment/email-to-personAPI reference

A work email in, the person out, with every job and the company ID of each.

Send

email
The full address from the form.

Read

found, person
The person, or found: false when no one matches. Nothing is counted then.
person.experiences[]
company_linkedin_id (a string, or null), job_is_current and job_contract_type (can be null) for each job: the fields of the account match.
person.location
Where the person lives, for the rules that need it.
POST/v2/enrichment/companyAPI reference

The company page of the current job in, the account's attributes out.

Send

company_linkedin_url
From the matching job in the first response.

Read

company.linkedin_id
The ID to store on the account, returned as a number here and as a string on a person’s jobs.
company.hq, size, employees_on_linkedin, industry
The territory fields.

Each person or company found is one record; plans and rate limits are on the BlitzAPI pricing page.

The real lookup

The first response, on November 10, 2026, trimmed to two of the current jobs, with the other companies withheld:

{
  "found": true,
  "person": {
    "experiences": [
      {
        "company_name": "Personio",
        "company_linkedin_url": "https://www.linkedin.com/company/personio",
        "company_linkedin_id": "10180448",
        "job_is_current": true,
        "job_contract_type": "Full-time"
      },
      {
        "company_name": "(withheld)",
        "company_linkedin_id": "(withheld)",
        "job_is_current": true,
        "job_contract_type": "Part-time"
      }
    ]
  }
}

More part-time current jobs follow, then the past ones. The second response, for the Personio page, trimmed to the territory fields:

{
  "found": true,
  "company": {
    "linkedin_id": 10180448,
    "name": "Personio",
    "industry": "Software Development",
    "size": "1001-5000",
    "hq": { "city": "Munich", "country_code": "DE", "region": "EMEA" }
  }
}

Rules that read those fields

An example, in the order of the diagram:

if (!lookup.found) return reviewQueue(lead); // no one matched the address

// Company IDs come back as strings on jobs and as numbers on companies: key accounts by string.
const current = lookup.person.experiences.filter((job) => job.job_is_current && job.company_linkedin_id);
const pick = (jobs) => {
  if (jobs.length === 1) return jobs[0];
  const fullTime = jobs.filter((job) => job.job_contract_type === 'Full-time');
  return fullTime.length === 1 ? fullTime[0] : null;
};

const owned = current.filter((job) => accountsById.has(String(job.company_linkedin_id)));
if (owned.length) {
  const job = pick(owned);
  return job ? ownerOf(accountsById.get(String(job.company_linkedin_id))) : reviewQueue(lead);
}

const job = pick(current);
if (!job) return reviewQueue(lead);
const result = await enrichCompany(job.company_linkedin_url);
if (!result.found) return reviewQueue(lead);
const { hq, employees_on_linkedin, industry } = result.company;
return territoryFor(hq.region ?? regionOf(hq.country_code), employees_on_linkedin, industry) ?? reviewQueue(lead);

Before you ship

  • Store the company ID on every account before routing reads it, from the account’s domain, with a name check.
  • Match on company_linkedin_id of current jobs only, compared as strings. A past employer is not the lead’s account.
  • Read territory fields from the account, and write down which size field each rule uses.
  • Send found: false and unmatched leads to a review queue with what the lookup returned.
  • A default owner for everything that matches no rule.

Sources and method

Published
API calls run on

The BlitzAPI team ran the lookups shown in the second diagram and in the builders section on November 10, 2026, on the work email of someone in revenue operations at Personio. The page shows the company, the person's function, that they hold part-time advisory roles elsewhere and that they live in Europe outside Germany; the name, the title, the address, the other employers, their number, the country and the past jobs are withheld.

The routing rules in the first diagram and in the builders section are an example. The fields they read are the ones the API returns.

Questions this raises

What is lead routing?

Lead routing is the process that sends each new lead to the person or team who should follow up, automatically and by rules: the owner of the account it belongs to, a territory, or a review queue. BlitzAPI is the B2B data API RevOps teams use to feed those rules: one call identifies the person behind a lead's email with the company ID of each current job, another returns the account's region, size and industry.

What are lead assignment rules?

Lead assignment rules are the conditions a CRM checks to give a new lead an owner, such as an existing account owner, a country, a company size band or an industry. In Salesforce, the entries of the active assignment rule are checked in order and the first match decides; other CRMs do the same with workflows. The rules are only as good as the fields they read, which is why the account match comes before them.

What does lead routing software do?

Lead routing software matches each new lead to an account, applies assignment rules, balances leads between reps and tracks how fast each one is followed up. It works on the fields already on the lead and the account, so it is only as good as the step that fills them: the form, or an enrichment step that runs before routing and identifies the person, the company and its attributes.

How do you route leads by territory?

Define territories on the account, not on the lead: headquarters region or country, company size and industry, read from the company profile. Then route each lead by the territory of the account it matched. A lead who lives in one country and works for a company headquartered in another follows the account, unless a rule says otherwise.

Is lead routing the same as lead to account matching?

No. Lead to account matching decides which account a lead belongs to. Lead routing decides who follows it up. Matching comes first: a lead attached to the wrong account goes to the wrong owner, whatever the routing rules say, and a lead attached to no account falls through to rules written for new companies.

Data shouldn't be
the problem

Grab. Connect. Build.