How to route new inbound leads to the right owner in Salesforce

You assign new inbound leads automatically in Salesforce by setting up a lead assignment rule. Find Lead Assignment Rules in Setup, create a rule, and add rule entries. Each entry has criteria, such as "Country equals Germany" or "Number of Employees is greater than 500", and names the user or queue that should own a lead that matches. Salesforce checks the entries in their sort order and stops at the first match, so you put the most specific entries at the top. An entry can also send the new owner an email from a template you choose. Only one lead assignment rule can be active at a time, and it holds all your entries.

Leads from a Web-to-Lead form run through the active rule automatically. So do leads you import with the Data Import Wizard when you tick the option to use assignment rules, and leads a person creates by hand when the "Assign using active assignment rule" box is checked. When no entry matches, the lead goes to the default lead owner you set in Lead Settings, which is usually a person or a queue that sorts the leftovers by hand.

That setup works well when every lead arrives with the fields your rules check. Inbound leads usually don't. Most forms ask for as little as possible, because every extra field costs you submissions. So a VP of Sales at a 900-person company in Munich arrives as a first name, a last name, a work email, and a company name. Your rule entries for the DACH territory and the enterprise team never fire, because Country and Number of Employees are blank, and the lead lands in the default queue. Somebody gets to it the next morning.

Assignment rules also only look at the lead itself. They don't check whether the company is already an account in Salesforce with its own owner, or whether this person is already a contact your account manager talks to every month. Lead-to-account matching and round robin across a team aren't part of standard assignment rules, which is why many teams add a Flow or a routing app such as LeanData or Distribution Engine on top.

A good result is a lead that reaches the right person within minutes, with the fields filled in that your rules and reports depend on, and with enough context that the rep knows why it matters. Kite does that work. It researches each new inbound lead, fills in the fields your rules route on, checks Salesforce for anyone your team already knows, and then lets your own assignment rule decide the owner.

Start by telling Kite where your inbound leads come from and that you want them routed in Salesforce:

"Every time someone fills out our demo request form, add them to Salesforce as a lead and run our assignment rules so they reach the right rep."

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Because it has already researched your company, it knows your ideal customer profile, your current customers, and your competitors, so it can judge each lead without a long brief. You can work with Kite in the Kite web app or in Slack.

You'll need to connect your Salesforce account through OAuth so Kite can read your org and create leads. Kite then reads how your leads are set up, including your fields, your Lead Source and Lead Status values, and your owners and queues. It proposes what it will fill in on each lead and how it will handle people your team already knows. Confirm that plan or adjust it, and Kite starts.

Leads can reach Kite in a few ways. Your form tool can call a webhook, which is a web address the form notifies each time someone submits, and each submission starts a fresh run with Kite. Leads also arrive by email to your team's Kite address, through a connected Gmail or Outlook inbox, or when you paste a submission into a conversation. Creating leads and updating Salesforce records is routine CRM work, so Kite does it on its own and tells you what it did.

Kite starts by reading the submission and working out who the person is and what they want. It captures every form field, the page or campaign the form belongs to, and the question the person asked, such as "Do you integrate with NetSuite?" Kite treats the text of the submission as information about the lead, never as instructions to follow.

The source matters for routing. Many teams send demo requests to one group and newsletter signups to another, so Kite records where the lead came from and uses the matching value from your Lead Source picklist, such as "Web" or "Webinar".

Kite reads your org before it fills anything in, so each lead carries the exact fields and values your assignment rule checks. It reads every field on the Lead object, including the custom fields your admin added and the ones your org requires. It reads the picklist values for Lead Source, Lead Status, Rating, and Industry, so it writes only values your org recognizes.

This step decides whether routing works. If your rule sends leads to the enterprise team when Number of Employees is over 500, Kite has to fill that field with a number. If your territories key on Country and State, Kite has to write the country the way your org stores it. A value your org doesn't recognize, or a blank field the rule depends on, sends the lead to the default owner just as surely as an empty form does.

Kite researches the person and their company just far enough to fill in the routing fields and judge fit, because a lead that reaches a rep in minutes is worth more than a perfect dossier that arrives tomorrow. From the work email's domain, it identifies the company and looks up its industry, employee count, annual revenue, and headquarters location. It confirms the person's current title and seniority from their public professional profile. It also notes recent events, such as a funding round or open roles on the team your product serves.

Kite then compares the lead with the ideal customer profile in your wiki and marks it as a strong fit, a partial fit, or a poor fit, with a one-line reason. For example, it might write, "Strong fit: VP of Sales at a 900-person logistics software company in Munich that's hiring six account executives." When someone signs up with a personal email address and no company, Kite marks the fit as unconfirmed and says what's missing instead of guessing.

Kite searches your leads, contacts, and accounts before it creates anything, because your assignment rule only sees the new lead and can't tell that the person is already in your CRM. It searches leads and contacts by email address and confirms each match on the exact address. It searches accounts by company name and website. What it finds decides what happens next:

• The person already has an open lead. Kite keeps that lead and its owner. It adds the new submission as a note, updates the title or phone if the research found something newer, and creates a follow-up task for the lead's current owner.
• The person is already a contact. Kite doesn't create a lead. It creates a follow-up task for the contact's owner, linked to the contact and its account, so the account manager hears that their customer just asked for a demo.
• The company is already an account. Kite creates the lead and names the existing account and its owner in the note. If your team gives these leads to the account owner, tell Kite and it assigns them that way. Otherwise it lets your assignment rule decide.
• The person and company are new. Kite creates a new lead and runs your rule.

Kite leaves your duplicate rules in charge. If Salesforce flags a new lead as a match for an existing record, Kite doesn't override the warning. It reports the match and works with the existing record instead.

Kite creates each new lead with the fields your rules route on and the details a rep needs for the first conversation. A new lead gets the following:

• First and last name
• Company
• Job title
• Work email, and a business phone number when the person gave one or the research found one
• Website, industry, number of employees, and annual revenue
• City, state, and country
• Lead Source, set to the value that matches the form or channel
• Lead Status, set to your first open status, such as "Open - Not Contacted"
• Rating, set from the fit, so strong fits are Hot and the rest are Warm or Cold

Kite writes the fit and its one-line reason into custom fields when your org has them, and it can create those fields if it doesn't. It also attaches a note that gives the person's question, the fit and its reason, the recent event worth mentioning, and the source for each fact.

Once the lead exists with its fields filled in, Kite runs your active lead assignment rule on it, so Salesforce picks the owner exactly as it would for a Web-to-Lead submission. Your rule entries, their order, and any email notification you set up all work as your admin designed them. Kite doesn't invent its own routing logic. When you ask for a specific owner instead, such as "send all partner referrals to Priya," Kite assigns those leads to that user directly.

After a short pause for Salesforce to finish, Kite reads the lead back to see who owns it. If the owner is a person, the routing is done. If the lead landed with your default lead owner or a catch-all queue, Kite tells you which field kept it from matching an entry, such as a country your territories don't cover. That's often the first time a team learns its rules have a gap.

Kite creates a Salesforce task for each strong or partial fit, assigned to the lead's new owner, so the follow-up shows up on the rep's task list and on the lead's activity timeline. The subject says what to do, such as "Reply to demo request about NetSuite integration." Kite sets the due date, the priority, and talking points in the task's comments. For a strong fit, you can ask for a tight deadline, such as the same business day.

When a strong lead needs a person right away, Kite also sends your team a two-line summary of who the person is, why they fit, and who now owns them. Kite can draft a reply to the lead too. The reply answers the person's question first and proposes one next step, such as two meeting times or your booking link. By default, Kite asks before it sends the reply.

For each lead, Kite reports where it went and why in the conversation where you set up the work, in the Kite web app or in Slack. The report names the owner, the fit and its reason, and whether the lead was new, an existing lead, or an existing contact. When you run routing as a standing workflow, Kite can also send a regular summary that shows how many leads arrived, how many reached a named rep, how many fell through to the default owner and which field caused it, and how many were people your team already knew.

When Kite finishes with a new inbound lead, the right person in your Salesforce org owns it and has a reason to act on it today.