Who Owns the 4:47 p.m. Inquiry? A Lead-Routing Blueprint

Lead routing is the set of rules that decides, the moment an inquiry arrives, who owns it and what happens next. A working setup captures the inquiry into the CRM, enriches it, qualifies it, assigns an owner by fit and territory, starts follow-up on a clock, and keeps the source attached through to the invoice. No step waits for someone to check an inbox.

An inquiry arrives at 4:47 p.m. on a Thursday. Who owns it?

In most growing B2B companies, the honest answer is “whoever checks the inbox.” The form lands in a shared mailbox. Someone copies it into the CRM, looks up the company, and emails a partner to take it. The first reply goes out the next day. By the end of the quarter, nobody can say which channel produced the deal.

This blueprint replaces that chain with seven steps you can implement in the CRM you already own. Each step is small. Together they turn the CRM from a filing cabinet into the thing that runs the process.

What does lead routing look like today?

Here is the illustrative sequence most B2B teams will recognize:

• Day 1. The website form arrives in a shared inbox.
• Day 1. Someone copies it into the CRM by hand.
• Day 1. The company is looked up, and a partner is emailed to take it.
• Day 2. The first reply goes out.
• Later. Nobody can say which channel produced it.

And after a build:

• 00:00 Website inquiry captured.
• 00:02 Company data enriched.
• 00:04 Inquiry qualified and routed by fit and territory.
• 00:06 CRM record created, owner assigned.
• 00:07 Follow-up starts; source stays attached to invoice.

The difference is not effort. It is where the decisions live. In the first sequence they live in people’s heads. In the second they live in rules.

Before you start: what do you need in place?

You need three things, and you probably have them already:

• A CRM that your team logs into daily. HubSpot, Salesforce, and Pipedrive all work.
• A website form or intake point you control.
• One page, written down, that says what a good-fit customer looks like.

That third item matters more than any tool. If “qualified” means three different things to three people, no routing rule will fix it.

Step 1: How do you capture every inquiry as a record?

Send every inbound source straight into the CRM. Do not let any of them start life in an inbox.

• Website forms post directly to the CRM, not to email.
• Chat, referral, and event leads go through the same intake form or import.
• Each record is created or updated. Match on email and company domain so repeat inquiries do not create duplicates.

Check: submit a test inquiry. It should appear in the CRM with no human touching it.

Step 2: How do you enrich the record automatically?

Add the context a rep would otherwise look up by hand.

• Company name, size band, industry, and location from the email domain.
• The page or campaign the inquiry came from.
• Any existing record: past deals, open tickets, current customer status.

Enrichment should fill fields your reps actually use. If nobody reads a field, do not collect it. Enrichment your reps do not trust is worse than none, because it trains them to ignore the record.

Step 3: How do you qualify without a meeting?

Turn the one-page fit definition into rules.

1. Write the three to five criteria that separate a good-fit inquiry from a poor one. Examples: industry, company size band, service requested, region.
2. Map each criterion to a field that Steps 1 and 2 fill.
3. Assign each inquiry to one of three buckets: fit, maybe, or not a fit.

Keep the logic deterministic. Qualification needs to give the same answer every time for the same inputs. AI can help read a free-text “tell us about your project” field and propose a category. The rule, not the model, makes the final call.

Step 4: How do you route by fit and territory?

Give every bucket an owner and a rule. No inquiry should be unowned for even a minute.

Bucket	Owner rule	First action
Fit, known territory	Territory owner	Personal reply and a proposed call time
Fit, no territory match	Round-robin across senior reps	Same as above
Maybe	Named reviewer	Review within the business day
Not a fit	No owner; polite automated reply	Offer a useful resource, then close
Existing customer	Account owner	Route to account, not to new business

Ownership rules that change by territory and deal size are normal. Write them down, then encode them. If a rule cannot be written down, it is a judgment call, and judgment calls belong in the Maybe bucket.

Step 5: How do you start follow-up on a clock?

Assigning an owner is not the same as responding. Start a timer at assignment.

1. Send an immediate confirmation to the inquirer so they know a person will follow up.
2. Create a task for the owner with a due time: the same business hour for fit inquiries.
3. If the task is not completed by its due time, notify the owner and a backup.
4. If it is still open after a second interval, reassign it.

The 4:47 p.m. inquiry now has an owner at 4:47 and an escalation path if the owner has already left for the day. That is the whole point of a service-level agreement: the system notices, so people do not have to.

Step 6: How do you catch deals that stall?

Most leaks happen after the first reply, not before it.

• Define a maximum age for each deal stage.
• When a deal exceeds that age with no activity, flag it to the owner.
• Review flagged deals in the weekly pipeline meeting, by exception.

Stage definitions matter here. If “contacted” and “qualified” overlap, stalled-deal alerts become noise. Tighten the stages first, then set the timers.

Step 7: How do you keep the source through to the invoice?

Capture the source once, at Step 1, and never overwrite it.

• Store first-touch source and campaign on the contact and copy them to the deal.
• Keep later touches as separate fields, so first touch is never lost.
• When the deal closes and invoices, the source travels with it.

Now marketing can see what became revenue, not just what became a form fill. Budget can follow closed deals instead of clicks.

Why not just configure HubSpot harder?

Sometimes that is the answer. Configure the platform if your sales process fits how it wants to work. Plenty do.

The platform usually struggles in four places:

• Lifecycle stages that cross three systems, such as a CRM, a proposal tool, and billing.
• Ownership rules that change by territory and deal size.
• Enrichment your reps actually trust.
• Attribution that survives from first touch to invoice.

We build the part the platform will not do on its own, and we will tell you plainly when the platform is enough.

What does this look like in a real firm?

Illustrative: a composite scenario, not a client result.

A 12-person professional-services firm gets steady inbound inquiries from the site, referrals, and events. Today someone copies each form into the CRM, looks up the company, and emails a partner to take it. First replies land the next day, and nobody can say which channel produced last quarter’s revenue.

After a build, every inquiry creates or updates the CRM record, is enriched and routed by fit and territory, starts a same-hour follow-up, flags itself when it stalls, and keeps its source attached from first touch to invoice.

What are cold inquiries costing you?

Use your own numbers, not a benchmark.

Count the qualified inquiries that went cold last month. Multiply by your close rate on inquiries you do work. Multiply by your average first-year deal value.

That is the monthly revenue lost to slow replies. The B2B systems page runs the same arithmetic, and the CRM trust diagnostic walks through the symptoms.

FAQ