Which inbound leads deserve a call in five minutes?

Inbound lead qualification is the job of deciding, at the moment a lead arrives, which ones earn a call inside minutes and which ones can wait. The problem is that most qualification frameworks were built for a conversation, not a form submission. BANT asks for budget, authority, need and a timeline. None of those four things exist yet when someone has just clicked submit. What exists is the form itself: which fields it asked, what the visitor typed, and where they came from.

What is inbound lead qualification?

Inbound lead qualification is deciding how urgently, and by whom, an inbound form submission should be followed up, based only on information available at the moment it arrives. It is a narrower job than sales qualification in general. MQL vs SQL is about which team owns a lead after marketing has worked it. BANT vs MEDDIC vs MEDDPICC is about what a rep needs to confirm before forecasting a deal. Both assume time has passed and a conversation has happened. Inbound qualification runs before either.

That's a real constraint, not a lesser version of the same problem. You cannot ask a form submission whether the visitor has budget authority. You can ask it what page they were on, what they typed into a free-text field, whether their email domain matches a company, and what they picked from a dropdown. The method has to be built from that list, not from the list a rep would use on a call.

Why treating every submission the same is the default failure

Most routing setups have exactly one rule: a new lead gets an owner, and the owner gets a notification. HubSpot's default lead properties include a Lead Source field, set automatically at creation, and a Lead Owner field that inherits from the primary contact or company. Neither field says anything about whether this particular submission is worth a five-minute response or a same-week one. The routing logic most teams actually run stops at "assigned," not "prioritised."

The fix is not more data. It's using the data that is already sitting in the form and treating it as three separate questions instead of one blended guess.

The three signals that exist before you know anything else

1. 1.
   Intent: what they actually asked for

   Not every conversion event means the same thing. "Book a demo," "talk to sales," "contact us" and "download the guide" are different requests wearing the same submit button. The form type is the strongest intent signal you have, and it costs nothing to read: it's already a property on the record. It fails as a signal if your forms don't distinguish request types, meaning every conversion path on the site, from a pricing page and from a blog post, writes to the same generic "Contact form" bucket. If that's true, the fix is upstream of qualification: separate the forms before you try to tier what they produce.

2. 2.
   Fit: who they are, without waiting for enrichment

   Fit is demographic, not behavioural: company size, job title, industry, and whether the submitted email is on a business domain or a free one (gmail.com, outlook.com, yahoo.com). All of it can sit on the form itself as a required field or a dropdown, so it's available the second the form posts, with no enrichment call and no delay. HubSpot's own lead-scoring tool names this split explicitly: it builds "fit scores" from property values like job title, company size and annual revenue, kept separate from "engagement scores," which track actions like visiting a page or opening an email. It fails if fit is inferred rather than asked. A guess based on the domain in the email address is a weak proxy for company size; a required dropdown on the form itself is not.

3. 3.
   Timing: the field almost nobody adds

   Older qualification frameworks call this the "T" in BANT, and it's usually the one skipped on inbound forms because it feels presumptuous to ask a stranger when they want to buy. It isn't. A single dropdown ("Right away," "This quarter," "Just researching") turns a flat pile of form fills into an ordered list, and it costs one extra field. It fails if the only timing signal you have is how recently the form arrived. Recency tells you when they filled it in, not when they intend to act.

Turning three signals into tiers, worked

Take two submissions arriving the same afternoon. Neither has talked to a rep yet, so neither has given you anything beyond what the form captured.

Submission A answers all three questions the form is capable of asking, and every answer points the same direction. Submission B answers none of them, because the download form never asked and a personal email address gives you nothing to check fit against. Neither submission has been "read" by a human yet. The tiering decision is made entirely from fields that existed before either lead was opened.

A workable tier structure, stated with its own failing condition per tier:

The point of writing it this way is that a rep or an automation can check each cell against the submission and get the same answer every time. A tier with no stated failing condition is not a rule, it's a description of what a good lead usually looks like, and "usually" is exactly what lets two reps disagree about the same submission.

Why speed only matters once the tier is decided

The research behind the "call in five minutes" advice is real, and it's specific about what it measured. The 2007 Lead Response Management study found that leads first called within 5 minutes had 21 times the odds of being qualified, compared with leads first called at 30 minutes, across phone-dial data from six companies. The study doesn't break its dataset down by form type or intent level, but every lead in it was already getting a phone call, which is closer to a tier 1 or 2 submission than a newsletter signup nobody calls at all. Applying a five-minute SLA to every form on your site burns rep time on tier 3 and 4 submissions the study gives no reason to think would benefit the same way. The full research trail, including where the 21x figure comes from and what a realistic response-time target looks like across company sizes, is in speed to lead.

Where this method breaks

Three honest failure modes, because a tiering rule that never admits a false positive is not being tested.

A real buyer uses a personal email. Founders and small-company buyers sometimes run their business email through Gmail. A rule that tiers purely on domain type will under-rank a genuine tier-1 lead. The fix is not to drop the signal, it's to never let email domain be the only fit input; pair it with the company-size dropdown so one weak signal doesn't carry the whole decision alone.

A competitor or a student fills the highest-intent form. "Book a demo" from a competitor's domain, or a research request from a .edu address, will pass every intent and fit check you've built if those checks stop at domain and company size. This is what a job-title field and a short required "what are you evaluating this for" field catch, and it's why tier 1 should still route to a human rather than an autobooked calendar slot with no review step.

Timing answers are self-reported and can be wrong. Someone picks "this quarter" because it sounds active, not because a budget cycle actually supports it. Timing is useful for ordering a queue, not for guaranteeing a close. Treat it as a tiebreaker between two submissions that already matched on intent and fit, not as a standalone qualifier.

The tools that act on this at the moment a form posts

Naming the fields is half the job. The other half is a system that reads them the second the form submits, rather than a rep opening a CRM view once an hour.

• HubSpot workflows can branch on form-field values the instant a submission comes in, and its lead-scoring tool builds separate fit and engagement scores from exactly the property types described above, combining them into one score you can route on.
• Salesforce lead assignment rules evaluate a new lead against ordered rule entries and assign it to a user or queue the moment it's created; if no rule matches, it falls to a default owner rather than sitting unowned.
• Calendly routing forms can branch on any question on the form, including HubSpot form fields synced into Calendly, sending a tier-1 visitor straight to a rep's live calendar and a lower-tier visitor to a different page entirely.
• Chili Piper's Concierge Router reads a webform submission and puts the right rep's calendar in front of the visitor within seconds, which is the mechanism that makes a "call now" tier actually mean now rather than "next time someone checks the queue."

None of these tools decide what counts as tier 1. That's still the method above. What they remove is the gap between the tier being decided and someone acting on it, which is the same gap that speed to lead measures in hours across most companies.

What to check in your own forms this week

Read the form type on your last 20 submissions. If more than half say the same generic label regardless of which page or CTA produced them, your intent signal doesn't exist yet, no matter how the leads get routed afterward.

Check whether your highest-intent form asks for company size. If it doesn't, you're inferring fit from the email domain alone, which is a proxy, not a field.

Ask what happens to a submission with no fit data at all. If the honest answer is "it gets the same notification as everything else," you don't have four tiers, you have one, and the fastest response time in the world is being spent on the wrong quarter of your leads.

This is the same enforcement problem as pipeline stage exit criteria: a rule that lives in a rep's head instead of a required field is a rule that stops being applied within a quarter, and who's allowed to change the routing logic matters as much as what the logic says.

If you want a second pair of eyes on your own setup, Salestruct runs a free diagnostic.