How to Route Identified Accounts to Sales

A visitor identification tool tells you which companies are on your site. That only pays off when the right rep hears about the right account while the visit still matters. This playbook covers what happens after the match, from ownership and qualification rules to alerts, follow-up deadlines and measurement.

This applies once a visitor identification tool is live and syncing to HubSpot or Salesforce, with reps set up as users in each system. Routing quality depends on clean ownership data in the CRM. No rule can fix an account with a wrong or missing owner.

How To Route Identified Accounts To Sales, Step By Step

Routing identified accounts to sales works when every matched company passes the same gates in order (a fit check, an owner lookup in the CRM, an alert to that owner and a follow-up deadline), because Harvard Business Review research in 2011 found most companies are not responding nearly fast enough to online leads.

Website visitor identification changes one thing about lead routing. A form fill is a raised hand. An identified account has not asked to talk to anyone, so relevance matters more than speed alone. A rep who calls every visitor quickly, with nothing specific to say, spends the account's attention for nothing.

The workflow runs in eight steps. Each step later in this playbook names the permission or plan it needs in HubSpot, Salesforce, Warmly, Leadfeeder and Slack.

• Connect the identification tool to the CRM so matched companies sync as records
• Define the fit and intent gates that decide which accounts reach a rep
• Look up the existing CRM owner of the account, a contact at it or an open deal
• Apply territory or named-account rules to accounts with no owner
• Round robin the rest within a pool of eligible reps
• Name one fallback rep who receives anything no rule catches
• Alert the owner with pages viewed, the trigger and a follow-up deadline
• Review unassigned and fallback accounts every week

Step 1 assumes the tool is already live. Tag setup and consent banners belong to installing a visitor identification tool, so this playbook starts once a match exists.

The order matters more than any single rule. Owner lookup comes before territory rules, because an account that already has a rep should never be handed to a stranger. Round robin comes after rules, because it is a tie-breaker, not a strategy. The fallback rep comes last, because HubSpot and Warmly both leave accounts with nobody when no rep is eligible.

Steps 2 to 4 hold most of the judgement, and the next three sections cover them. Steps 5 to 7 are mostly configuration, covered system by system further down. Step 8 is the one teams skip, and it is the step that shows which accounts fell through.

Who Should Own An Identified Account?

An identified account should go to the rep who already owns it in the CRM, and only accounts with no owner should fall through to territory rules, then a round-robin pool, then a named fallback rep, which is the order Lead Routing in Warmly checks them in.

Use this hierarchy as the decision rule:

1. Existing owner. The CRM owner of the account, of a contact at it or of an open opportunity.
2. Named-account or territory rules. For unowned accounts that match a target list, segment or region.
3. Round-robin pool. For unowned accounts that no rule claims, spread across eligible reps.
4. Named fallback rep. For anything left, so no account sits with nobody.

Account state decides who the existing owner should be in the first place:

Warmly shows owner-first logic in practice. It first identifies the visitor by email or domain, and a visitor it cannot identify goes to the fallback pool. It then checks CRM owner tiers in turn (the Account or Company owner, the Contact owner, the Lead owner in Salesforce, the Opportunity or Deal owner and any custom owner field) and stops at the first eligible owner. Only then does it evaluate segment rules from the top down, where the first matching rule wins.

Round robin in Warmly picks the rep with the lowest round-robin count. A visitor routed in the previous 24 hours keeps the same rep if that rep is available, and unavailable reps are skipped.

Round robin is not neutral. HubSpot's rotation action assigns only users with paid sales or service seats, and when no user is eligible, no owner is assigned. Warmly leaves nothing to assign when a rule matches but has no reps and no fallback reps. Both cases end the same way, with an interested account that no rep hears about.

Whether the owner is an SDR or an account executive is a team choice, not a system setting. A common split follows account state. Net-new accounts go to SDRs who qualify them, while target accounts and open deals go straight to the AE who holds the relationship.

What Qualification Rules Decide Which Accounts Reach Sales?

Only accounts that match your ideal customer profile and show a buying signal, such as a pricing-page visit, should reach a rep, since 73% of B2B buyers actively avoid suppliers who send irrelevant outreach in Gartner's 2025 survey of 632 buyers.

Qualification works in three layers, and an account must pass all three. Fit asks whether the company could buy. Intent asks whether it is looking now. Exclusions remove accounts that should never reach a new-business rep, whatever their score.

The tools set what you can filter on. Warmly alert conditions can check website domain, page path, UTM parameters and visit location, and can be limited to segments such as SDR-owned accounts or closed-lost deals. Warmly does not route leads that match a blocklist or data-quality exclusion segment, so exclusions become a segment you maintain rather than a one-off filter. Leadfeeder handles the split with custom feeds, one per team or region.

If your ICP is still a paragraph in a strategy deck, first turn your ICP into account filters, then write routing rules against those fields.

Treat a vendor's combined fit-and-intent score as a claim, not a rule. Warmly, for example, lists a surge score among its routing inputs. Before routing on any score, ask which signals feed it and whether reps can see them on the record. A score nobody can explain is a score reps stop trusting.

How Fast Should Sales Follow Up On An Identified Account?

Set the follow-up deadline by signal tier, with the hottest identified accounts answered within the same working hour and colder matches batched into a daily digest, because 67% of B2B buyers prefer a rep-free experience in Gartner's 2026 survey of 646 buyers, and a late, generic touch gives them no reason to talk.

The tiers below are Growth Tribune's rule of thumb, not a benchmark. Adjust the deadlines to your team's capacity, but keep the gap between tiers.

Real-time alerts are only as fast as identification. Warmly's "Lands on a page" trigger fires in real time with company information only. Its "After full identification completes" trigger is not real time and can take a few minutes or up to an hour. Start the hot-tier clock when the alert arrives, not when the visit began.

Speed without relevance fails. A buyer who prefers to research alone will ignore a fast message that only says you noticed the visit. The first touch should name what the account looked at and offer something useful about it. That is why the alert payload matters as much as the deadline.

How To Set Up Account Routing In HubSpot And Salesforce

In HubSpot, the Rotate record to owner workflow action needs Sales Hub or Service Hub Professional or Enterprise and assigns only users with paid seats, while in Salesforce lead assignment rules route leads, not accounts, and Enterprise Territory Management places accounts in territories rather than naming an owner.

HubSpot

Role in routing: HubSpot is where ownership lives for teams that run it, so it should hold the owner lookup and the rotation, with the identification tool feeding it records.

Owner logic: The Rotate record to owner action distributes records equally within a selected team or between specified users. An option to overwrite an existing owner exists, and leaving it off keeps owner-first routing intact. Only one object can be rotated at a time, and changing owners resets the assignment counts. Away users can be skipped with "Assign to available users only".

Alert delivery: The "Send a Slack notification" workflow action can go to selected users, channels or the existing record owner, with action buttons and @mentions.

Permissions and plan: Workflows and the rotation action need Sales Hub or Service Hub Professional or Enterprise. Rotation assigns only users with paid sales or service seats. Core and view-only seats, users who have not accepted their invite and deactivated users are left out.

Limitation: If no user is eligible to rotate to, no owner is assigned. If the HubSpot owner property syncs to Salesforce, HubSpot says the action may not work as expected.

Salesforce

Role in routing: Salesforce routes leads with assignment rules and organises accounts with territories, so teams that sync identified companies as accounts need a separate way to name an owner.

Owner logic: Lead assignment rules evaluate entries in order and stop at the first match. Only one lead assignment rule can be active at a time. A lead that matches no entry goes to the default Web-to-Lead owner, or to the administrator running an import.

Permissions and plan: Creating or changing assignment rules needs the Customize Application permission. Enterprise Territory Management is available in Performance and Developer Editions, and in Enterprise and Unlimited Editions with Sales.

Limitation: Lead and case assignment rules do not assign account records. Territory account assignment rules place accounts in territories, not with a named owner. An account that matches several territories on one branch goes to the lowest matching territory, and with several local rules an account must match all of them.

The common mistake is expecting lead assignment rules to route identified accounts. They will not. If the identification tool creates accounts in Salesforce, decide whether territory membership sets the owner or whether the identification tool reads the account owner field and routes from there.

How To Route Identified Accounts In Warmly And Leadfeeder

Warmly can route an identified account automatically, checking the CRM owner first and then segment rules from the top down, while the documented assignment in Leadfeeder (formerly Dealfront) is a manual Assign action, with custom feeds that send each team's accounts to its own Slack channel.

Warmly

Role in routing: Warmly states that routing can be configured by territory mapping, account owner, website activity, chat engagement, surge score, industry and company size, with notifications in Slack and Microsoft Teams.

Owner logic: Warmly checks CRM owner tiers first and stops at an eligible owner. Segment rules then run from the top down, where the first matching rule wins, followed by fallback reps. Round robin picks the rep with the lowest count and skips unavailable reps.

Alert delivery: Slack alerts post to public channels, one channel per alert, and can @mention the rep a Lead Routing rule picks.

Permissions and plan: The CRM integration must be connected and syncing, and reps must already be Warmly users. Routes are created under Settings > Lead Routing. Lead routing, Slack alerts, CRM sync and webhook integrations are listed on the AI Web-Deanonymization plan.

Limitation: Leads stay unassigned when identification data is insufficient, though routing can be re-evaluated later. A matched rule with no reps and no fallback reps leaves nothing to assign, which is why Warmly recommends configuring at least one fallback rep.

Warmly spend depends on contract shape more than on seats. Plans are sold through sales on annual or quarterly terms with a monthly credit allowance. The GTM Signals Package and Warm Experiences are priced separately, and the AI 24/7 Video Chat Agent is sold through sales. Budget for the add-ons your routing design needs, not only the base plan.

On June 30, 2026, Warmly announced an agreement to be acquired by HubSpot. Warmly says customers' contracts, pricing, account teams, product and integrations are unchanged for now. Teams still choosing an identification tool for this job can weigh the trade-offs in the RB2B vs Warmly comparison.

Leadfeeder

Role in routing: Leadfeeder identifies companies and offers two-way sync with HubSpot, Salesforce and Pipedrive, so for most teams the CRM holds the routing logic after sync.

Owner logic: Assignment is manual. A user opens a company, clicks Assign and picks an assignee, with an optional comment. The assignee gets an email notification. Only users who have accepted their Leadfeeder invitation appear in the list, and teams that do not want emails can tag companies and build a custom feed per tag instead.

Alert delivery: The Slack integration posts newly identified companies to any public or private channel, forwards different custom feeds to different channels by team or region, and sends a personal Slack notification when a company is assigned to you.

Permissions and plan: CRM sync and real-time alerts start on the Discover plan, and CRM automations start on Activate. Paid tiers are priced by the number of companies identified, and Activate and Scale add credits.

Limitation: Assignment in Leadfeeder is a manual step, so at volume the routing logic belongs in team-level custom feeds or in the CRM's own rules after sync.

Leadfeeder spend grows with the number of companies identified, so tight exclusion rules keep the bill and the alert volume down together.

Dealfront rebranded as Leadfeeder on March 24, 2026, as a brand change rather than a contract change. Subscriptions, pricing, integrations and data carried over, logins moved to the Leadfeeder app, and the module formerly called Leadfeeder is now Website Visitors.

How To Send Identified Account Alerts To Slack

Send each identified account alert to the person who owns the account, and check Slack permissions first, because Warmly posts only to public channels with one channel per alert, while HubSpot reaches a private channel only after its app is added to it.

A useful alert carries five things:

• Account. Company name, industry, size and country, so the rep can judge fit at a glance.
• Owner. The rep, @mentioned, so the alert reaches a person rather than a channel.
• Pages viewed. The pricing, comparison or product pages behind the signal.
• Trigger. Which rule fired, and the UTM source when there is one.
• Deadline. The follow-up time from the account's signal tier.

{{owner_mention}} {{account_name}} is on the site now
Tier {{signal_tier}} · follow up by {{deadline}}
Pages viewed {{pages_viewed}}
Trigger {{trigger_rule}} · source {{utm_source}}
Fit {{industry}} · {{company_size}} · {{country}}
Open the record {{crm_record_link}}

Each tool reaches Slack in a different way:

Mentions need matching accounts on both sides. Warmly can only @mention users who are in the Slack workspace, and HubSpot lists only users who have mapped their email addresses.

Slack Workflow Builder And Webhooks

Role in routing: Slack is the delivery layer, not the router. It should receive an owner decision made in the CRM or the identification tool and put it in front of that owner.

Alert delivery: Any tool that can send a POST request can start a webhook-triggered workflow, which then posts to a channel or a person with a "Send a message" step. Posting to a channel needs posting permission in it.

Permissions and plan: Workflow Builder and webhook workflows are on paid plans. All Full Members can create webhook workflows by default, and owners and admins can restrict this. Any member can install an app by default, but Workspace Owners can turn on app approval, and restricted apps cannot be installed or requested. Warmly's installer must be a Slack Admin or have permission to install apps, or setup fails with an Unauthorized error.

Limitation: A webhook takes up to 20 variables with no nested JSON, and the workflow fails if a variable is missing from the request. It accepts one request per second. Anyone with the request URL can start the workflow, so keep the URL secret.

One busy shared channel buries alerts. Mention the owner on hot alerts, and send cooler tiers to a digest channel. HubSpot's Slack notifications cover mentions, form submissions and task assignments on all plans once the app is connected, so a CRM task with a deadline can carry the warm tier without another channel.

How To Measure Whether Account Routing Works

Account routing works when the time from identification to first touch falls and the share of accounts that land with a fallback rep or no owner shrinks, so track those two numbers weekly before counting meetings. Meetings come later and lag any routing fix.

The no-owner count is not theoretical. HubSpot assigns no owner when no user is eligible to rotate to. Warmly leaves leads unassigned when identification data is insufficient, or when a matched rule has no reps and no fallback reps. Both show up in the weekly count long before anyone notices a missed account.

Decision rule: When the fallback share is high, fix ownership data in the CRM before tuning rules. A rule set cannot route to the right owner when the owner field is wrong or empty. When ownership is clean but time to first touch stays long, look at alert delivery and the tier deadlines instead.

Is Routing Identified Visitors Compliant With GDPR?

Routing a company-level match raises few privacy questions, but once a tool names a person, the UK ICO says it will constitute personal data even if they are acting in their business capacity, so person-level routing needs a lawful basis and an opt-out.

The ICO's B2B guidance also covers email. The PECR electronic-mail marketing rule does not apply to corporate subscribers, though sole traders and some partnerships are treated differently. Senders must still not disguise their identity and must give a valid opt-out address.

In routing terms, keep company-level and person-level matches on separate paths. A company match can go to the owner as an account alert. A named person should reach a rep with the context needed to apply your lawful basis and honour opt-outs. For the wider picture, see what website visitor identification is and what the law allows.

Frequently Asked Questions

Sources