--- title: "Real estate lead routing rules for your team website" description: "Define who receives seller and buyer website inquiries. Write agent eligibility, rule priority, absence coverage, and assignment tests for your site." canonical: "https://scalewithsearch.com/articles/multi-agent-website-lead-routing-rules" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Real estate lead routing: rules for a multi-agent website For your multi-agent website, define who receives each seller or buyer inquiry before accepting the forms. Write the eligible recipients, rule priority, absence coverage, and conflict handling. Require a received test inquiry and an explanation of its assignment. Real estate lead routing assigns incoming inquiries using rules. Lofty's documentation describes conditions such as source and location, followed by an assignment method. Its rules operate within company, office, or personal ownership scopes. [Lofty's lead-routing guide](https://help.lofty.com/hc/en-us/articles/360055177831-Lead-Routing-How-to-set-up-lead-routing-rules). Use the proposed worksheets below with your website builder and contact-system administrator. Agree on the policy before configuring it. Leave unsupported behavior marked unresolved until someone demonstrates it in your setup. ## Start with the website page and the visitor's request Inventory your seller page, buyer page, agent profiles, property pages, and general contact page. Give each form a stable name. Record its page address and the request it invites. For a seller inquiry, distinguish the property the visitor wants to sell from the page they were reading. Ask for location only where your assignment policy needs it. Keep an unknown location visible for review. For a buyer inquiry, distinguish a property question from a general search request. Require the property reference to arrive with the question. Avoid choosing the recipient from the page title alone. For an agent profile, decide whether the form requests that agent specifically. Make the button and contact wording match your decision. If another teammate may answer, explain that coverage in the approved page copy. Specify these inputs in the brief: | Input | Source to confirm | Decision it supports | | --- | --- | --- | | Inquiry purpose | Visitor's seller, buyer, or general-contact choice | Which service group may receive it | | Requested agent | Explicit visitor choice or the approved profile form | Whether a named-agent rule applies | | Property reference | Validated property-page record | Whether an approved property rule applies | | Service area | Submitted property location or confirmed property record | Which recipients cover the requested area | | Returning contact | Contact system's documented identity check | Whether existing ownership needs consideration | | Source page and form | Validated website context | Which page produced this inquiry | Ask the builder to verify page and agent references on the receiving server. MDN explains that hidden form values remain visible and editable through browser tools. A hidden agent identifier cannot establish a trusted assignment by itself. [MDN's hidden-input guidance](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input/hidden). Keep advertising-source labels separate from assignment permission. Require the rule to use the approved service request and validated context. ## Write an agent eligibility matrix Before selecting a recipient, define who may handle the request. Use a row for each agent or receiving group. Have the responsible team member confirm every entry. This is a proposed matrix. Fill it with your own approved roster rather than assuming your software contains every field. | Roster field | Question to settle | Result when unresolved | | --- | --- | --- | | Membership | Is this recipient still part of the intended team? | Exclude from automatic selection pending review | | Inquiry role | May this recipient handle seller, buyer, or both requests? | Send the request to the designated reviewer | | Service area | Which areas has the team approved for this recipient? | Review an unmatched area before assigning it | | Coverage hours | When does this recipient accept new website inquiries? | Use the agreed absence route | | Temporary availability | Who records leave or suspended coverage? | Keep the recipient out of the available pool | | Receiving access | Can this recipient open the destination and reply? | Keep assignment unaccepted until demonstrated | | Backup | Who covers an unavailable named recipient? | Escalate to the responsible reviewer | Keep temporary coverage separate from permanent contact ownership. For your policy, require approval before an absence changes the person responsible for an existing relationship. Availability behavior needs a product check. Lofty documents working hours and vacation exclusions for agent routing. It describes moving to another applicable rule or the default when every recipient is outside working hours. [Lofty's working-hours guidance](https://help.lofty.com/hc/en-us/articles/360055177831-Lead-Routing-How-to-set-up-lead-routing-rules). Ask your administrator to demonstrate the equivalent behavior in your account. If it needs manual coverage, name that person in the brief. ## Set rule priority and a path for conflicting requests Write an ordered decision table. Treat this proposed order as a starting point for team approval, rather than an industry requirement. | Priority | Condition | Proposed action | | --- | --- | --- | | Conflict review | A returning contact requests someone other than the recorded owner | Preserve ownership and send the new request to the designated reviewer | | Existing relationship | A confirmed returning contact has an approved owner, with no conflicting request | Deliver to that owner or the approved temporary coverage route | | Named agent | A new contact explicitly requests an eligible agent | Assign the inquiry to that agent | | Approved property rule | A new property inquiry has no named request | Use the recipient approved for that property's website inquiries | | Service and area | A general seller or buyer request matches an eligible group | Apply the agreed distribution method within that group | | No match | The request lacks usable routing data or has no eligible recipient | Deliver to a monitored review destination | Require a decision on each overlap. If a returning buyer asks a property question, decide whether existing ownership takes priority. If a new visitor requests an agent who is unavailable, specify the backup and the wording the visitor sees. Keep the property-page recipient explicit. Require a verified assignment in your brief. Check whether an agent displayed beside a listing is your team's approved recipient. Rule order can change the result in documented systems. Lofty evaluates rules from top to bottom and stops at the first match. A broad rule above a specific rule would capture a request that matches both. [Lofty's rule-order documentation](https://help.lofty.com/hc/en-us/articles/360055177831-Lead-Routing-How-to-set-up-lead-routing-rules). Ask for a demonstration of an inquiry that matches overlapping rules. Require the saved reason to identify which rule won. For profile forms, confirm the receiving scope too. Lofty distinguishes personal website leads from company website leads and offers different routing choices for company sources. [Lofty's ownership-scope documentation](https://help.lofty.com/hc/en-us/articles/4407645128347-Personal-Office-Team-and-Company-Lead-Routing). ## Keep repeat inquiries distinct from duplicate delivery Specify how your contact system identifies a returning person. HubSpot, for example, uses email to deduplicate contacts. A form submission matching an existing contact's email adds information to that contact. [HubSpot's deduplication documentation](https://knowledge.hubspot.com/records/deduplication-of-records). Ask for the documented rule used by your actual connection. Require a separate decision for a new question from that person. Preserve the question, its source page, and the approved owner. For acceptance testing, distinguish a repeated delivery of the same submission from a later inquiry by the same contact. Require the maintainer to demonstrate both. Ask repeated delivery to retain one assignment, while a later question remains available as new inquiry history. If the visitor uses changed contact details, require the agreed identity-review path. Do not infer identity from a matching name alone in your proposed policy. ## Define absence coverage and missed-response handling Name the destination for an inquiry that cannot be assigned immediately. Give that destination a responsible person and an absence backup. Require a visible pending status until someone takes responsibility. Set response hours and a response target your team approves. Define when the clock starts. State whether overnight hours count. Specify what evidence qualifies as a personal response. Keep automatic acknowledgment, recipient notification, and personal reply as separate checks. Require the administrator to demonstrate each event your response rule depends on. For a missed target, choose an alert, manual review, or supported reassignment. Confirm the chosen capability before placing it in public wording. If reassignment is approved, require an ownership check before moving the inquiry. Specify who receives notice of the handoff. Preserve the original question and any reply history. For an existing contact, use the approved coverage decision before changing permanent ownership. ## Require an assignment record you can inspect Ask the maintainer how you will answer a later assignment question. Request the submission reference, form, validated page context, matched rule, assigned recipient, and assignment time. Include the rule version or dated policy used for the decision. For reviewed conflicts, save the reviewer and reason. For a later handoff, preserve the previous recipient and the new assignment. Lofty documents routing logs that show the result of each evaluated rule and where the lead matched. That is a product-specific example of evidence you can request. [Lofty's routing-log documentation](https://help.lofty.com/hc/en-us/articles/360033311952-Lead-Routing-Logs). Ask the provider to show the available history and retention limits. If the requested record needs a separate implementation, leave it outside accepted scope until confirmed. ## Test assignment through the website before accepting it Use a preview or agreed test environment with contact details you control. Tell the receiving team which messages are tests. Write the expected recipient before each submission. These are proposed acceptance cases. They are not results from a tested installation. | Website test | Evidence to require | | --- | --- | | New seller asks about representation | Seller request, service area, eligible recipient, and winning rule | | New buyer asks about a property | Correct property reference, question, and approved recipient | | New visitor requests an agent on a profile | Named request preserved and assigned under the approved profile rule | | Returning contact submits a new question | Existing ownership handled as agreed and new question retained | | Returning contact requests a different agent | Conflict visible for review, with no silent ownership change | | Named recipient is unavailable | Approved coverage destination and truthful visitor message | | Request matches specific and general rules | Agreed priority wins, with a saved explanation | | Location is missing or outside approved coverage | Inquiry reaches the monitored review destination | | Same submission is delivered again | One assignment under the agreed duplicate-delivery rule | | Inquiries arrive together | Each retains its own assignment and complete question | | Agent leaves the team | Removed recipient receives no new inquiry | | Delivery fails after submission | Failure visible to the named maintainer and recovery demonstrated | Inspect the received record and the recipient's working view. Confirm that the assigned person can reply. Keep a mismatch open until the repaired route passes again. Retain the matrix, decision table, conflict policy, and test evidence in the website handoff. Repeat affected checks after roster, form, or rule changes. ## Specify multi-agent inquiry routing checks The routing matrix defines eligibility, ordered assignment rules, and unresolved conflicts. Bring the supported connection request to [whole website fix: multi-agent routing](/for/real-estate). The whole website fix requires CRM integration to be confirmed in scope. [multi-agent routing, published scope, checked 2026.10.14](https://scalewithsearch.com/work). - [Test the seller inquiry path on your real estate website](/articles/seller-inquiry-path-agent-website) - [Real estate CRM and website: map forms to contact records](/articles/real-estate-crm-and-website) - [Check your real estate website in 30 minutes](/articles/real-estate-website-audit) ## Related: Real estate - [Test the seller inquiry path on your real estate website](/articles/seller-inquiry-path-agent-website) - [Real estate CRM and website: map forms to contact records](/articles/real-estate-crm-and-website) - [Check your real estate website in 30 minutes](/articles/real-estate-website-audit) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```