What actually happens in the first hour after an immigration inquiry comes in?
A prospect fills out a form, usually from a Meta ad, sometimes from a Google search for "EB-5 lawyer" or "NIW attorney near me." At that point they are still comparing three or four firms. Intent has a shelf life, and it decays fast. Contact within five minutes beats contact within thirty by a wide margin in almost every legal intake study, because the prospect is still sitting on the page, still in decision mode, still open to a firm that answers now instead of tomorrow.
What most firms miss is that the clock doesn't start when the form submits. It starts earlier, when the ad targets the wrong audience or the case type is unclear on the landing page, and the intake team spends the first ten minutes figuring out whether this is even a case the firm takes. That's ten minutes lost before a human ever picks up the phone, and no amount of intake-team hustle recovers it.
There's also a second clock most firms never track: the gap between when a prospect submits and when someone internally decides who should call them back. In firms running EB-5, NIW, and H-1B through one shared queue, that decision alone can eat the entire five-minute window.
Why "fast" isn't the same as "qualified"
Fast contact with an unqualified prospect wastes the fastest resource a firm has: attorney or paralegal time on the phone. A caller asking about asylum status when the firm only handles EB-5 and NIW gets the same five-minute callback as a real prospect, and it costs the same intake hour. Multiply that across a month of inbound and the math gets ugly fast.
This is the trap in most speed-to-lead advice. It treats every inbound the same, as if a form submission is a form submission regardless of what's behind it. Immigration law doesn't work that way. Case types have different qualification bars, different documentation requirements, and wildly different consult-to-signed ratios. A firm running EB-5, NIW, MBGC, and H-1B out of one shared intake queue is optimizing speed for a queue that shouldn't exist as one queue in the first place.
Speed without qualification also creates a morale problem inside the intake team. Callers get good at answering fast and bad at closing, because most of what they're answering fast was never going to close.
What is a qualification layer, and how is it different from a script?
A qualification layer is a set of questions and routing rules that run before a human callback, not during one. It's not a phone script an intake coordinator reads off a sheet after picking up. It's a system, usually a short form or an automated flow, that separates a genuine EB-5 investor inquiry with capital ready from someone who typed "green card lawyer" into Google at midnight with no capital and no timeline.
CaseFlow, the installation DR built for exactly this problem, routes inbound by case type before the phone ever rings. Speed still matters inside that system. It just applies to prospects who've already cleared the qualification bar, so the five-minute callback goes to someone worth calling in five minutes, not someone who needed a different firm entirely.
The difference shows up in what the intake team actually does all day. Instead of triaging blind, they're working a queue that's already sorted by case type and by likelihood to sign, and the callback speed inside that sorted queue is what actually moves signed cases.
The numbers: cost per signed case before and after qualification
Across 1,391 signed cases, that immigration firm's cost per signed case dropped from $2,372 to $1,064 after case type separation and a qualification layer went in ahead of intake speed. That's not a cost-per-lead number, and the distinction matters more than it sounds like it should. Cost per lead was never the metric that mattered here. A firm can drop CPL to nothing and still lose money if the leads underneath it don't convert to retainers.
The same firm signed 825 cases in 2025, up 78% year over year, while spend efficiency improved rather than degraded under the added volume. Returns measured across three separate periods came in at 6.39x, 8.0x, and 8.6x. Those numbers don't blend into one figure, on purpose. Blending three different periods into a single average erases exactly the trend that matters here: the ratio kept climbing as the qualification layer matured and the intake team got better at working a sorted queue.
Case type separation and a qualification layer, installed ahead of intake speed.
How does a 55% consult rate change intake staffing?
Once qualification runs ahead of contact, 55% of qualified inquiries convert to booked consults. That number changes how a firm staffs intake, and it changes the conversation with the managing partner about headcount. Instead of a large team fielding a high volume of unqualified calls and burning out on rejection, a smaller team can handle a filtered queue where better than half the calls turn into consults worth showing up for.
Firms that skip this step usually solve the wrong problem when consult numbers look weak. They hire more intake staff to answer faster, when the actual bottleneck is that half the queue was never going to sign regardless of how fast the phone got answered. More staff on a bad queue is more expensive failure, not a fix.
Does speed to lead matter equally across EB-5, NIW, MBGC, and H-1B?
No, and treating it as if it does is where most firms lose the case type battle before it even starts. EB-5 investors compare firms on structure, fund performance, and track record over days, sometimes weeks, not minutes. Speed helps but doesn't decide it. NIW and MBGC prospects move faster and are noticeably more price-sensitive around the initial consult fee. H-1B inquiries spike seasonally around cap season and often come from employers rather than individuals, which changes who actually needs to be on the first call and what they need to hear.
A single intake script, answered fast, applied identically to all four case types, produces mediocre results across all four. Case type separation means the qualification questions differ before callback speed even becomes relevant to the outcome.
Fixing speed on top of a broken filter just means the wrong prospects get answered faster.
What breaks when case type separation doesn't exist?
Ad spend, intake time, and attorney hours all get pooled against a blended average that hides which case type is actually working and which is quietly draining the budget. A firm might see an overall cost per signed case that looks acceptable while EB-5 is bleeding budget and NIW is outperforming underneath it, invisible inside the blend. Pooled campaigns and pooled intake queues both hide that split, and neither gets fixed until someone pulls the data apart by case type.
Special Ad Category compliance on Meta adds another layer that most firms underestimate. Campaigns already run within legal restrictions on how immigration-related audiences can be targeted. Pooling case types on top of that restriction compounds the inefficiency instead of simplifying anything, because the platform is already limiting precision and pooling removes what precision is left.
What should a firm build first, speed or filtering?
Filtering first, then speed inside the filter. A five-minute callback to an unqualified prospect is still a wasted five minutes, no matter how proud the intake team is of hitting that number. A qualification layer that routes the right case type to the right intake path, followed by a genuinely fast callback, is what moved the numbers above from $2,372 to $1,064 per signed case.
Firms with fast response times and flat signed-case growth are almost always missing the qualification step, not the speed step. Fixing speed on top of a broken filter just means the wrong prospects get answered faster.