Lead to account matching that sends inbound leads to account owners.

Lead to account matching is the check that links a new lead to an account already in your CRM, usually by email domain and company name. When it finds one, the lead goes to the rep who owns that account. Without it, a lead from a customer or an open deal lands in a round robin, and two reps call the same company.

Matching is the first step of account-based routing: match the lead to its account, route by territory or segment, rotate inside the team, then hand what is left to a fallback owner. Our lead routing software comparison covers the tools for the whole stack; this page covers the first step.

• Matched, owner active: the lead goes straight to the account owner.
• Matched, owner gone: the account's owner has left or been deactivated, so the lead needs a fallback.
• No match: a new company, so the lead goes to territory rules or a round robin.
• Nothing to match on: a personal email and an empty company field leave no clue, so the fallback decides.

In Cleanlist AI the Route inbound to owners agent runs the match on every new inbound lead, sets the owner in Salesforce or HubSpot and DMs the rep. You describe the job to Clu once, and routing costs no credits.

The Standard Account Matching Rule is the rule Salesforce duplicate management uses to find duplicate accounts. It is active by default, and the Standard Account Duplicate Rule uses it to warn a user who starts creating an account that already exists, with the alert "Use one of these records?". By default the user can still save the record.

A record counts as a duplicate when one of these pairs matches: name and billing street, name with city and state, name and ZIP, name and phone, website and phone, or website and billing street. Accurate matches need an account name and a city or ZIP code on the record.

It compares accounts with other accounts, for example when someone starts to create one. Giving a new lead to the right owner is a separate job.

Salesforce's own lead to account matching is the Matched Leads component on account pages. It lists the leads that match an account, best matches first, and lets a user convert them without leaving the account. The Standard Matching Rule for Leads on Accounts fills it, and that rule is activated with the purchase of Account Engagement Advanced or Premium edition.

The rule matches a lead's company name together with its street, city and state, ZIP or phone, or the domain of the lead's email against the account's website, ignoring widely used domains such as gmail.com and yahoo.com. An account with no website is matched through the email domains of its most recently stamped contacts.

Matching is a separate job in Salesforce because a lead keeps its company as text and has no link to its account until it is converted, which creates an account, a contact and optionally an opportunity, or updates existing ones with the same names. Until then, lead assignment rules can only read the lead's own fields.

HubSpot matches by association. With the setting Create and associate companies with contacts turned on, HubSpot links each contact to the company whose domain matches the contact's email, and creates the company when none exists. With Assign company owner to contact by default, a contact's owner follows the owner of its primary company. Both settings are on every HubSpot plan.

• Personal email addresses: for a gmail.com address HubSpot checks the contact's Website URL instead, and associates nothing when that is empty.
• Existing associations stay: a contact already linked to a company with another domain keeps that link.
• New companies: when nothing matches, HubSpot creates a company, and it advises against the setting with its Salesforce integration because of duplicate companies.
• Owner sync: it follows the primary company only, doesn't update existing records retroactively, and leaves a manually chosen contact owner alone.

For leads with no match, HubSpot's Rotate record to owner workflow action spreads records evenly across chosen users or a team. It needs Sales Hub or Service Hub Professional or Enterprise, and every user in the rotation needs a paid Professional or Enterprise seat. Round robin, load balanced and random distribution are offered for leads (in beta) and tickets. For most other records HubSpot rotates one at a time, so a burst of new records can take longer to clear.

On HubSpot the agent starts from new contacts, treats the contact's company as its account, and otherwise finds an existing company by domain and name. It never creates a company to make a match.

Good matching tries the strongest signal first and refuses to guess. Match the email domain against the account's website, fall back to the company name with legal suffixes stripped, skip personal email domains, and send the lead to a fallback owner when a name fits more than one account. A wrong match hands the lead to a rep who doesn't own the relationship.

An account without a website in Salesforce, or a company domain in HubSpot, can only match on its name, so filling those fields routes more leads to the right owner.

Salesforce assigns new leads with lead assignment rules. One rule is active at a time. Salesforce checks its entries in order, and the first entry a lead matches assigns it to a user or a queue. A lead that matches no entry goes to the default Web-to-Lead owner, or to the administrator running the import.

• Entries: each entry holds up to 25 filter criteria, or a formula that returns true or false.
• Catch-all: Salesforce suggests a last entry with no criteria, so nothing falls through.
• Sources: rules assign leads entered by hand, from Web-to-Lead forms and from the Data Import Wizard.

What does round robin mean in business?

Round robin hands each new lead to the next person in a fixed rotation, so everyone gets the same number before the cycle starts again. Salesforce's own help builds it from an Autonumber lead number, a formula field such as MOD(VALUE(Lead_Number__c), 3) + 1 for three reps, and one assignment rule entry per rep. When the team changes, the formula and the entries change with it.

Owner assignment in the agent

Five kinds of tool do the job. The CRM's own features cover simple cases. Matching and routing apps add fuzzy matching, hierarchies and capacity rules for Salesforce. Assignment apps rotate leads fairly. Form routing tools route the form fill and book the meeting. Agents match each new lead, set the owner and tell the rep where they already work.

Where Cleanlist AI fits: the agent does the match, the owner change and the DM on Salesforce or HubSpot, from a CRM trigger every 30 minutes or a webhook within seconds. It doesn't book meetings, climb account hierarchies or balance capacity across reps. For pricing on Chili Piper, LeanData, RevenueHero and Default, see our lead routing software comparison; to score leads before they are routed, see the lead qualification agent.

Routing costs no credits: the CRM trigger, the sync with its owner assignment and the Slack DM are all free. If you add an Enrich step, a verified work email costs 1 credit and a phone number 10, charged only when one is found. Research and qualification are charged in credits per lead; the pricing page lists the current rates.

Running the agent needs Pro (from $89 a seat a month, $67 billed annually), which includes 5 active agents across the workspace, or Enterprise for unlimited agents. The 14-day Pro trial lets you build the agent and review its play; testing it and turning it on need a paid plan.

Every agent Clu builds carries two limits you set: records per run, and a credit limit counted across all its runs in a rolling 24 hours (or per day, week or month on a schedule). When it is reached, runs stop until the window resets.