Lead Claim Windows: How Portal Leads Actually Get Assigned

Forty seven percent of online property inquiries are never answered by anyone. That is from Mike DelPrete’s 2024 secret shopping study of 25 US brokerages, and almost every one of those leads had been routed to a named agent. The routing worked. The claiming did not. This is the configuration layer behind my real estate coaching.

What a claim window actually is

A claim window is a countdown attached to a single lead and a single agent. The system assigns the lead, starts a timer, and if that agent does not press accept before the timer expires, the lead moves on to the next agent, the next group, or a pond. Nothing about the window measures how fast anyone talks to the consumer. It measures how fast somebody presses a button.

That distinction sounds pedantic until you look at what teams report. A dashboard showing a two minute median claim time and a 96 percent claim rate can sit on top of a pipeline where a third of those leads were never called. Claiming is free and takes one tap. Working the lead is the expensive part, and the claim window does not touch it.

There is a second distinction that matters more. Speed to lead is a target you choose. A claim window is a rule the platform enforces on you. You can decide you want a five minute first response. But if the portal gives your agent 30 seconds to pick up a ringing phone, your target is irrelevant to whether you got the lead at all. The philosophy of fast response is covered in depth in my guide to real estate lead routing and speed to lead. This article is about the mechanics underneath it.

Three things happen inside a claim window, and teams usually only think about the first. The lead gets offered. The clock runs. And on expiry, something specific happens that you configured months ago and probably cannot recite from memory. That third step is where leads disappear, because the fallback is very often a pond nobody watches or an account owner who is on a listing appointment.

What the ranking guides on this topic leave out

I read the pages currently ranking for lead routing and claim window terms before writing this. They agree with each other to a suspicious degree. Set a window of two minutes for portal leads. Use round robin. Hold your team accountable. Almost none of them states a single documented claim window from an actual platform, and none states the one legal constraint that overrides every routing rule you write.

The errors are specific and repeated. One widely cited vendor page describes the classic MIT lead response study as showing a hundredfold advantage at five minutes versus one hour. The study compared five minutes to thirty minutes. Another invents a requirement to refresh consent every ninety days, which has never been a rule anywhere. A third quotes a per call penalty figure that was superseded years ago and never updated.

The gap that matters most is the legal one. Lead routing decides who calls, and it also decides when the automated text fires. Federal law restricts telephone solicitation to the hours between 8 a.m. and 9 p.m. measured at the location of the person being called. Not one of the ranking guides on lead routing connects those two facts, and at least one major CRM measures that window from the wrong clock by default.

So this guide does three things the others do not. It quotes the claim windows the platforms publish in their own documentation, with the mechanic each one actually uses. It computes the worst case time to assignment your cascade produces, which is usually many times longer than the number you set. And it shows where routing and calling hours collide, because that collision is currently generating litigation.

The claim windows the portals actually document

Start here, because this is the layer you do not control. Portal programs set their own acceptance mechanics, publish them in help centers and broker FAQs rather than in marketing material, and change them without telling agents. Below is what is currently documented, with the mechanic each one uses, because the mechanics differ far more than the durations do.

Notice what that table does to the standard advice. The two fastest programs do not have a claim button at all in the usual sense. They put a live human on the phone and the acceptance is the phone call. The slowest published window is two full hours. That is roughly a hundred and twenty times longer than the five minute rule everyone repeats, and it comes from a national franchise brand.

Zillow: thirty seconds, and it is a phone call

Zillow’s in-app connections documentation states the mechanic plainly. When a shopper requests to connect, the agent receives a call and has roughly 30 seconds to accept it. If the agent misses that window, Zillow’s help center says the system will hang up and retry the call through the standard connection flow.

Read that again, because it invalidates a large amount of published advice. There is no five minute response target on a Zillow live connection. There is no CRM claim button in the loop. There is a ringing phone and half a minute. Whether your agent has the volume up is a more consequential setting than any routing rule in your CRM.

Zillow’s own first party data supports why they built it that way. The company has said home shoppers are three times more likely to transact when they are connected live. Its May 2021 announcement of in-app connections reported connecting agents 45 percent faster with a 7 percent higher appointment rate. Those are vendor figures about a vendor product, so weigh them accordingly, but the design intent is unambiguous.

The paid program has also changed name and terms. What agents still call Flex now appears under the Zillow Preferred branding. The success fee runs from 15 to 40 percent of logged gross commission income depending on zip code and sale price. Seller originated connection transactions are charged at 40 percent, and the schedule can change on fifteen days’ notice. If you are budgeting against a number you memorized two years ago, re-read your current agreement.

The performance standards are where routing quietly becomes a compliance problem. Zillow measures answer rate and appointment rate over three months, and show rate over six months. It also measures customer satisfaction across your twenty most recent responses, and CRM usage against a target of roughly five updates per connection. Participating partner agents are also required to have and use a Follow Up Boss account, with a sixty day compliance window. Zillow owns Follow Up Boss, which is worth knowing when you evaluate CRM options for a real estate team.

Realtor.com ReadyConnect Concierge, formerly Opcity

ReadyConnect Concierge works on the opposite principle. Rather than routing the raw lead to you, realtor.com’s concierge team contacts the consumer first. The program materials state the concierge reaches out within ten seconds of the online inquiry, operating from 8 a.m. to 9 p.m. in the consumer’s local time, 365 days a year.

Your window opens after that. The concierge qualifies the consumer and then attempts a live transfer to an agent. The first agent to take the connection gets exclusive access to that consumer. Agents who engage later get shared access, which in practice means you are now competing with whoever answered first and has already had a conversation.

Realtor.com does not publish the referral percentage in its public agent materials, which is unusual and worth naming. Brokerage disclosures fill part of the gap. The Real Brokerage has stated publicly that the fee varies from 30 to 38 percent of the earned commission. Treat any single number you see quoted as an example rather than a rate card, and get your own agreement in writing before you model the economics.

The operational consequence for routing is simple and often missed. Because the concierge already spoke to the consumer, your first contact is not a cold call, it is a handoff, and the consumer expects continuity. Sending that person into a generic new lead drip that opens with an introduction they already received reads as though nobody is paying attention. Route concierge transfers into their own sequence.

RE/MAX MAXTech: the 120 minute window nobody cites

The single most detailed public document on real estate claim windows is a broker FAQ for the RE/MAX MAXTech lead concierge program. I have not seen it referenced in a single guide on this topic. It spells out the whole cascade, the hours, the fees, and the eligibility test, in a level of detail no CRM vendor publishes.

For leads on RE/MAX listings, the listing agent gets 120 minutes to accept, 24 hours a day. Miss it and the lead routes to the concierge team, after which the listing agent receives a second 120 minute window, this time at a 30 percent referral fee. A listing agent who declines still owes the 30 percent if another agent closes the deal, which is a detail worth reading twice.

For leads on non RE/MAX listings, the window is again 120 minutes, but it only runs between 8 a.m. and 8 p.m. in the agent’s time zone. Leads that arrive outside those hours are sent the next morning at 8 a.m. with a fresh clock. An inquiry at 9:15 p.m. on Friday therefore sits until Saturday morning by design.

Distribution begins as a round robin and then migrates to a weighted system that favors agents who convert. The cascade runs from opted-in agents, to highly engaged agents in the office who have not opted in, and then outward to a thirty mile radius. The document even defines engagement: an agent who has logged in on at least five separate days in the past thirty days and taken an action on a contact.

Two more numbers from the same document. The concierges themselves respond in as little as 90 seconds, and they call consumers between 8 a.m. and 9 p.m. in the lead’s time zone. Note the inconsistency, because it is instructive: acceptance is measured in the agent’s time zone and calling is measured in the consumer’s. That is not sloppiness, it is the difference between a business rule and a legal one, and the next section is about the second kind.

$7 System

The Lead-Flow Activation System

The routing rules, first contact scripts, and follow up workflows I run on portal leads, in a format you can copy in an afternoon.

Get instant access ›

What your CRM actually supports, from the official documentation

Vendors describe routing in marketing language and specify it in help centers. Those two descriptions do not always match. What follows comes from each platform’s own documentation, and I have marked the gaps rather than filling them with guesses. A documented limit and an undocumented one are different problems.

Three details in that table deserve more than a row. Follow Up Boss caps the timed claim at thirty minutes, which means a team that wants a two hour window to match RE/MAX cannot build it with the timer alone. Sierra offers the lead to one agent at a time rather than blasting it, so its window is inherently sequential. And HubSpot, which many teams inherit from a marketing department, has no claim concept at all.

BoldTrail hides the most consequential instruction in a help article rather than in the settings screen. Its documentation tells administrators to multiply the chosen number of minutes by the number of agents in the routing list, because the timeout applies to each agent in turn. Set thirty minutes across six agents and you have configured a three hour worst case, not a thirty minute one.

Sierra frames its Actionable Window as compliance rather than convenience, advising admins to set it between 8:00 a.m. and 9:00 p.m. to remain compliant with messaging regulations. The documentation does not specify whose time zone that window is measured in, which is exactly the ambiguity the next section is about. Sierra also auto-appends opt out language to outbound texts, which is a genuinely good default.

Follow Up Boss adds one small mechanical detail with an outsized failure rate. Agents must tap the push notification to claim, not swipe it away. On a phone in a pocket, a swipe is the more likely gesture, and it produces a silent miss that looks in the data like an agent who ignored the lead.

Cascade math: the worst case nobody computes

Here is the arithmetic that changes how teams configure this. A claim window is not the time to assignment. It is the time per hop. Total time to assignment is the window multiplied by the number of hops before somebody accepts, plus any overnight pause your platform or your law imposes.

Take a common configuration. Six agents in the rotation, a thirty minute window each, one fallback group of three more, and an overnight pause from 9 p.m. to 8 a.m. A lead that nobody accepts enters at 7 p.m. and works through four hops before the pause. It resumes at 8 a.m. and finishes the remaining five hops by roughly 10:30 a.m. Total elapsed time from inquiry to final assignment: over fifteen hours.

Nobody configured fifteen hours. Somebody configured thirty minutes, nine times, with a night in the middle. The number on the settings screen and the number the consumer experiences are related only by multiplication, and the multiplication happens where nobody is looking.

Run your own numbers before you argue with the result. The most common reaction is that the cascade never actually goes that deep, and that is usually true on weekday afternoons and false at 9 p.m. on a Sunday in December. Worst case matters because worst case is when your least attentive coverage meets your most impatient consumer.

There are three ways to shorten it, and only one of them is a setting. Reduce the number of hops by removing agents who do not claim, which is a personnel decision. Shorten the per hop window, which trades thoroughness for speed. Or put a human backstop at hop two rather than hop nine, so that the cascade is a short list ending in somebody accountable rather than a long list ending in a pond.

One more caution about ponds. A pond is not a fallback, it is a holding tank, and it only works if somebody is paid to fish. If your cascade terminates in an unwatched pond, your effective worst case is not fifteen hours, it is however long until a quarterly cleanup. Keeping that from happening is the same discipline as ordinary CRM hygiene with pipelines and smart lists.

Free eBook

The Real Estate Kickstart eBook

The systems I used to close 800 homes, written for agents who want a pipeline that does not depend on luck.

Get the eBook ›

The quiet hours time zone trap

This is the part no competing article on lead routing covers, and it is currently generating lawsuits. The federal rule is short enough to quote in full. Under 47 C.F.R. section 64.1200(c)(1), no person or entity shall initiate any telephone solicitation to a residential telephone subscriber before the hour of 8 a.m. or after 9 p.m., local time at the called party’s location.

Two clauses do the work. The FCC treats text messages as calls, so your automated new lead text is covered. And the hours are measured at the called party’s location, not yours, not your brokerage’s, and not the server’s. Cell phones can qualify as residential lines, which removes the exception most agents assume protects them.

Now set that against a CRM default. Follow Up Boss states in its own documentation that text messages will not be sent between 9 p.m. and 8 a.m. in the assigned agent’s local time. That is a sensible sounding setting and it is measured from the wrong clock. A Virginia agent whose routing assigns a California lead at 8:05 a.m. Eastern is texting a Californian at 5:05 a.m.

The exposure is not theoretical. Roughly 480 quiet hours cases and demand letters were filed in the year following November 2024. As of late November 2025, a single firm, the Law Offices of Jibrael Hindi, accounted for 456 of them. That is a concentrated, industrialized filing pattern aimed at exactly this defect.

The regulatory picture is genuinely unsettled, and anyone telling you otherwise is selling something. The FCC sought comment in Public Notice DA-25-216A1 on whether messages sent with consent are exempt from the quiet hours rule. It also asked whether a number’s area code and exchange can be presumed to show the called party’s location. Comments closed in April 2025 and the Commission had not ruled as of this writing.

One district court has offered relief on a related question. In King v. Bon Charge, decided in the District of Delaware in April 2026, the court held that voluntarily providing your phone number can constitute prior express invitation or permission. That is one district court, it is not binding nationally, and building your routing policy on it would be optimistic.

The practical fix costs nothing and takes an afternoon. Set your messaging quiet hours from the lead’s time zone rather than the agent’s if your platform allows it. If it does not, narrow the sending window to a range that is safe everywhere you accept leads, which for the continental United States means starting at 11 a.m. Eastern and stopping at 9 p.m. Pacific converted to your own clock. Losing three morning hours is cheaper than one filing.

States that are stricter than the federal rule

Federal quiet hours are a floor, not a ceiling. Several states have mini statutes that narrow the window further. A few of them apply regardless of consent, which defeats the usual assumption that a signed opt in solves everything.

Verify the state rules against current statutory text before you rely on this table, because mini statutes are amended more often than the federal rule and compendiums go stale quickly. The point of the table is not the specific hours, it is that a single national sending window configured from your own time zone cannot be correct in all of them simultaneously.

Two federal changes are worth knowing because they cut in opposite directions. The one to one consent rule that was scheduled to reshape lead buying never took effect. The Eleventh Circuit vacated it in Insurance Marketing Coalition Ltd. v. FCC in January 2025, and the FCC formally removed the language in September 2025. If a vendor is still selling you a product to solve one to one consent, ask what it is solving.

The established business relationship windows are the other one, and they are shorter than most agents think. The regulation gives you eighteen months from a purchase or transaction, but only three months from an inquiry or application. A portal lead who inquires and never transacts gives you a ninety day window, not a year and a half.

Stop words, revocation, and the ten business day clock

The FCC’s revocation order took effect on April 11, 2025, and it changed the operational rules for every automated sequence a routing system triggers. A consumer may revoke consent by any reasonable means. Seven words are treated as per se revocation wherever they appear in a reply: stop, quit, end, revoke, opt out, cancel, and unsubscribe.

You then have ten business days to honor it, and the burden of proving that consent existed sits with you, not with the consumer. That burden is why routing and record keeping are the same problem. If a lead moved through four agents in a cascade, you need to be able to show which one had consent and when.

One piece of that order has been repeatedly delayed. The revoke all provision treats a revocation as applying across your messaging rather than to a single campaign. It was waived to April 11, 2026 and then extended to January 31, 2027 by an order issued in January 2026. Plan for it to arrive rather than for it to disappear.

The penalty structure explains the filing volume. A private action under the TCPA carries $500 per violation, trebled to $1,500 for a willful violation, with no attorneys’ fees available. Multiply $1,500 by an automated sequence that fired six times before anybody noticed and you have the arithmetic that supports a plaintiff’s practice.

Fair housing belongs in this section too, for a reason that is not obvious. HUD’s May 2024 guidance on digital advertising says the Fair Housing Act applies to housing decisions regardless of who makes them and what technology is used. It also raises the prospect of liability for third party tools. Geographic routing is an algorithm that assigns consumers to agents by where they live, so it is worth being able to explain why your territories are drawn the way they are.

How deduplication quietly kills your round robin

This is the failure that produces the most confused conversations in team meetings, because the routing rule is working correctly and the outcome is still wrong. Follow Up Boss deduplicates contacts when the email address matches, or when the phone number matches together with first and last name. That is a reasonable rule and it has a consequence nobody reads the manual for.

When an existing contact submits a new inquiry, Follow Up Boss documentation states that the original source of the lead will not be changed. The lead will not be reassigned to another agent. Lead flow rules do not re-fire. The person who first touched that contact owns them permanently unless somebody intervenes by hand.

Follow Up Boss offers an agent-owned lead duplication power-up that changes this behavior, and other platforms handle repeat inquiries differently. The action item is the same regardless of platform: find out what yours does with a returning contact, and decide deliberately whether re-inquiry should re-route. There is a defensible argument for either answer. There is no defensible argument for not knowing.

The related question teams argue about, simultaneous claims, turns out to be a non-issue technically. Follow Up Boss resolves it server-side and tells the loser the lead has already been claimed. Sierra resolves it by who answers the phone. BoldTrail gives it to the first acceptor. Every real dispute I have seen is a post-claim dispute, meaning a lead was claimed and then not worked, and that is a team agreement problem rather than a software problem.

A routing matrix by source

Different sources arrive with different mechanics, different expectations, and different legal footing, so routing them identically guarantees that some of them are handled badly. Here is how I separate them. The windows below are business decisions, not platform limits, and they assume the platform constraints from the earlier sections are already respected.

The last row is the one to think hardest about. Aged and purchased lists carry consent questions you cannot answer from the file. Since the one to one consent rule was vacated, that market has become less rather than more regulated. If you buy leads, my breakdown of buying leads from Zillow, realtor.com, and Opcity covers what you are actually purchasing in each program.

The open house row deserves a mention because of how badly it performs in the field. DelPrete’s secret shopping found that 42 percent of open houses never asked for contact information at all, and of the 58 percent that did, roughly a third never followed up. Combined, about 62 percent of open house visitors received no follow up whatsoever. There is no routing rule that fixes a lead you never captured.

Measuring the gap between claimed and worked

Most routing dashboards measure the easy thing. Claim rate and time to claim are both trivially instrumented and both describe button presses. The number that predicts revenue is the gap between leads claimed and leads actually worked, and almost nobody reports it because it requires defining what working a lead means.

Borrow the definition from the 2007 lead response research rather than inventing one: a call that connects with a live person and lasts a defined minimum number of seconds. Pick your threshold, thirty seconds is reasonable, and hold it constant. Anything shorter is a dial, not a contact, and counting dials as contacts is how teams convince themselves the problem is lead quality.

Exclude your automated messages from the contact count entirely. Follow Up Boss fires the initial lead flow text from the assigned agent’s number on lead creation. An untouched lead can therefore show outbound activity within seconds while no human has looked at it. If your reporting counts that as first contact, your first contact metric is measuring your automation, not your team.

Report the median, not the average, and report them together the first time so the team sees why. DelPrete’s 2024 study found a median response of 39 minutes against an average of 8 hours and 17 minutes across the same dataset. The average is nearly thirteen times the median because a handful of leads answered days later drag it upward. The median tells you about your process, the spread tells you about your outliers.

Then add the number that neither statistic contains. Report the percentage of leads never contacted at all as a separate line, because a median cannot see them. Forty seven percent never contacted with a 39 minute median for everyone else is a completely different business from 5 percent never contacted with a two hour median. The two look similar on any dashboard that reports only averages. For what those numbers should look like downstream, see my real estate lead conversion benchmarks.

What the response time evidence actually says

Since almost every claim window recommendation is justified by the same handful of studies, it is worth stating what those studies found and what they did not. The philosophy of responding fast is covered in my article on the five minute rule with scripts and automations. What follows is the citation check.

The foundational study is the Lead Response Management research by Dr. James Oldroyd, then a fellow at MIT Sloan, with Dave Elkington of InsideSales.com. It ran in 2007 across six companies, more than 15,000 leads and over 100,000 call attempts. It found roughly a hundredfold higher odds of contact and twenty one times higher odds of qualifying at five minutes compared with thirty minutes, not compared with an hour.

The study also included a caveat that gets stripped from every summary of it. In its own words, it did not address close ratios. It measured contact and qualification, which are upstream of revenue. Anyone citing it as proof that faster response produces more closings is citing something the authors explicitly declined to claim.

The Harvard Business Review audit from March 2011 is the second pillar. Its researchers submitted inquiries to 2,241 US companies. They found 37 percent responded within an hour, 23 percent never responded at all, and an average first response of 42 hours among those who did respond. The widely circulated 47 hour version of that figure is a misquote.

The most useful numbers for our industry are also the newest. Mike DelPrete’s August 2024 secret shopping covered more than 100 inquiries across 25-plus US brokerages. It found 47 percent of online property inquiries ignored entirely, a median response of 39 minutes, and an average of 8 hours 17 minutes. That is real estate specific, recent, and methodologically transparent, which is more than can be said for most figures in this space.

What I could not verify is worth listing too. The claim that 78 percent of customers buy from the company that responds first has no traceable primary source. Neither does the 391 percent first minute conversion figure. Vendor pages reporting response test results without publishing their methodology are marketing, not evidence, and I have not used them here.

A one hour audit of your own routing

You can find most of what is broken in a single sitting, and you do not need a consultant to do it. Open your CRM settings alongside your last thirty days of leads and work through the following in order, writing the answers down rather than trusting your memory of how you set it up.

First, list every routing rule that is currently active, including the ones somebody built for a campaign that ended in 2024. Stale rules are the most common cause of leads landing on former team members. Then, for each rule, write down what happens when the window expires, and keep asking that question until the answer is a named human rather than another group.

Second, find your messaging quiet hours setting and determine whose clock it uses. If the answer is the agent’s time zone and you accept leads from other states, you have found something worth fixing this week. Send yourself a test lead with an out of state number after 8 p.m. your time and see what goes out.

Third, count the hops. Multiply your window by the number of agents in the longest cascade, add your overnight pause, and compare that number with what you believed it was. Most teams are out by an order of magnitude. Fix it by shortening the list, not by shortening the timer, because a two minute window across twelve agents is still twenty four minutes and a worse experience for the agent.

Fourth, pull twenty claimed leads at random from last month and check whether each one received a human call within your stated standard. Do not check whether a text went out. Check for a conversation. The percentage you find is your real number, and it is usually the first honest look a team has had at its own follow up.

Fifth, test the failure path deliberately. Submit a lead through your own website at 9 p.m. on a Saturday and let it run untouched through the entire cascade. Whatever happens to that lead is what happens to a real consumer, and watching it once teaches more than reading any settings screen. Then rebuild the sequence that follows using a proper lead follow up system.

Training Library

Systems for agents who want to scale

Routing, follow up, conversion, and team building, taught by someone still doing the work.

Browse the store ›

Questions teams actually ask about claim windows

How long should a claim window be?

Shorter than you think and applied to fewer agents than you think. For website and paid leads, five to fifteen minutes per agent across a rotation of no more than three is a defensible setting. The duration matters far less than the number of hops, because total time to assignment is duration multiplied by hops. A fifteen minute window across three agents is a 45 minute worst case. A two minute window across twenty agents is worse.

What is the claim window on a Zillow lead?

For an in-app live connection it is about 30 seconds, and it is a phone call rather than a button in your CRM. Zillow’s documentation says that if the agent does not accept in that window, the system hangs up and retries through the standard connection flow. Any advice telling you to respond to a Zillow live connection within five minutes is describing a mechanic that does not exist.

Does realtor.com publish a claim window?

Not in the way portals are usually described. ReadyConnect Concierge has its own team contact the consumer within roughly ten seconds of the inquiry, operating 8 a.m. to 9 p.m. in the consumer’s local time, and your opportunity is the live transfer that follows. The first agent to engage gets exclusive access and later agents get shared access.

Can I set a two hour claim window in Follow Up Boss?

Not with the timed claim feature alone. Follow Up Boss caps the timed claim window at 30 minutes. You can chain up to two fallback groups before the lead defaults to the account owner, so a longer total cascade is possible. But no single agent can hold a lead for two hours on the timer.

Why does my round robin favor one agent?

Usually deduplication rather than bias. When a returning contact submits a new inquiry, many systems keep the original source and the original owner, so lead flow rules never re-fire. Every repeat inquiry from anyone that agent ever touched routes back to him automatically while new names split evenly. Check whether your platform offers a setting that re-routes re-inquiries.

What happens if two agents claim the same lead at once?

The platform resolves it and it is rarely a real problem. Follow Up Boss handles it server-side and tells the second agent the lead has already been claimed. Sierra resolves it by who answers the phone. BoldTrail gives it to the first acceptor. The disputes worth your attention are post-claim, where a lead was claimed and then never worked.

Do I need to worry about calling hours if I only send texts?

Yes, and texts are where most of the current exposure sits. The FCC treats text messages as calls for this purpose, and the quiet hours rule in 47 C.F.R. section 64.1200(c)(1) restricts contact to between 8 a.m. and 9 p.m. measured at the called party’s location. Automated first-contact texts triggered by routing are exactly the kind of message being litigated.

Whose time zone governs quiet hours?

The consumer’s. The regulation says local time at the called party’s location. This matters because at least one major real estate CRM applies its quiet hours using the assigned agent’s local time instead. A lead in a different time zone can then receive an automated text hours before the permitted window opens.

Is a lead pond a valid fallback?

Only if somebody is responsible for working it on a schedule. A pond with no owner is a place leads go to stop existing. If your cascade terminates in an unwatched pond, the practical worst case is not your configured window multiplied by your agent count. It is however long until somebody remembers the pond exists.

How do I measure routing without fooling myself?

Report three numbers side by side: median time to first human conversation, ninetieth percentile time, and the percentage of leads never contacted at all. Exclude automated texts from the contact definition. Averages hide the tail and claim rates measure button presses, so a team can post excellent numbers on both while half the pipeline goes unworked.

Should re-inquiries reset the claim window?

It depends on how long the gap was and how your team handles ownership, but the decision should be explicit. A consumer who inquired eight months ago and returns is behaving like a new lead. A consumer who submitted three forms in one afternoon is not. Most platforms default to preserving the original owner, so if you want different behavior you have to build it.

What is an established business relationship worth?

Less time than most agents assume. The regulation allows eighteen months from a purchase or transaction, but only three months from an inquiry or application. A portal lead who filled out a form and never transacted gives you roughly ninety days of that footing, and a do not call registration is honored indefinitely regardless.

Educational content only, not legal, tax, or financial advice. Telephone consumer protection rules, state mini statutes, and portal program terms change frequently and vary by jurisdiction. Verify current requirements with qualified counsel before configuring automated outreach. Platform features and fee schedules described here reflect published documentation available at the time of writing and are subject to change by the vendors.