Real Estate Technology / Lead Management
Does Your IDX Website Route Leads to the Right Place? A Real Estate Lead-Path Test
A website can look polished, show the right listings, and still lose a serious prospect between the form and your next conversation. The issue may be in lead routing: how an inquiry moves from the website or IDX form into your CRM and to the person expected to respond.
This guide is for agents who want to check that handoff. Team admins can use it to test routing rules across agents, offices, and lead sources. A solo agent can skip the team-assignment checks and focus on whether the right contact details, source, and inquiry context reach the CRM and create a clear next step.
If you are still choosing a platform, start with Choosing a Real Estate Website and IDX Platform: What to Check Before You Switch.
Research checked November 7, 2026 · Research-based guidance; no hands-on product testing claimed.
What a successful lead path should do
For each test inquiry, check that the system:
- Captures the submission. The form displays a success message and the website or IDX account records the inquiry.
- Delivers it to the intended CRM. The contact appears without someone forwarding an email or copying details by hand.
- Preserves useful context. The record includes the original source and, where supported, the form, listing, property address, buyer or seller intent, or relevant website activity.
- Assigns one clear owner. The responsible agent or team is visible, and the lead is not sitting unassigned or assigned twice.
- Alerts the right person. The assigned agent receives the notification through a channel your team actually monitors.
- Creates the next step. The right follow-up task or process starts, and someone knows who is expected to act.
“Arrived in the CRM” is only one checkpoint. The lead path works when the right person can see what the prospect asked about and knows what to do next.
Prepare a safe test
Have the website or CRM admin run the test if your team has one. A solo agent can run it personally. Bring in your website or IDX vendor if you cannot see the connection settings or lead records.
Before submitting anything, tell the team when the test is happening so no one calls or messages the test lead. Use an email address and phone number you control, label the contact clearly as a test, and avoid real client information. If possible, test in a staging environment. If you must use the live site, route the test to a safe test owner or prevent the test from triggering customer-facing messages without changing the normal workflow for real leads.
Afterward, mark or remove test records in both the website/IDX system and CRM so they do not create duplicates or distort source reports. Also clear any test tasks or automation activity that would confuse the team later.
Before you start, write down the expected result for each test. For example: “A buyer asking about this listing should appear in Follow Up Boss with the website source and property address, be assigned to the right agent, trigger an alert, and create a follow-up task.”
Run these five lead-path tests
| Test | Submit from | Distinctive detail to inspect |
|---|---|---|
| Buyer registration | IDX registration or save-a-listing form | Saved listing or search context |
| Listing inquiry | A specific property's “request information” form | Property address or listing identifier |
| General contact | Main website contact form | Form or page source |
| Seller inquiry | Home valuation or seller form, if available | Tagged or typed as a seller |
| Returning lead | Repeat a test submission with the same test contact | Existing record behavior |
If you have multiple offices, teams, territories, or source-based rules, repeat the routing checks for each setup that matters. Test on mobile too if the mobile forms differ from desktop.
Check one returning lead separately
Use the same test email or phone number for a second inquiry and see whether it updates the existing contact or creates another record. Check whether the new inquiry is visible and whether the original assignment and source remain as expected. Follow Up Boss’s help page says a matching existing contact is updated with the new inquiry, while its original lead source and assignment remain unchanged. That is the documented behavior for Follow Up Boss; check your own CRM’s duplicate settings and test record before relying on the same behavior elsewhere. Follow Up Boss: How lead inquiries are handled.
Follow the test from the form to the CRM
1. Confirm the form displayed a success message
A thank-you message only shows that the form displayed a success message; it does not prove the CRM received the inquiry. Record the time, page, and form you used, plus the test identifier. Check the website or IDX lead manager as well as the CRM.
2. Find the record in the CRM
Search using the exact test email or phone number. Confirm that the record appears once, with the expected name and contact details. If it is missing, check the website or IDX lead manager and any integration status or activity log your vendor provides before submitting more tests.
3. Check the source and inquiry details
Look beyond the contact’s name and email. Can you tell which form created the inquiry? Does the record show the source, listing, property address, saved search, or page activity your team relies on? A label such as “Website” may be too broad to help with reporting or a useful first response.
What reaches your CRM depends on the particular connection, so inspect your own test record. As of November 7, 2026, Follow Up Boss lists AgentFire under API-integrated websites and says its connection can sync buyer/seller type, tags, assigned agent, and website activity. Follow Up Boss’s IDX integration page describes the AgentFire connection. The same page lists iHomefinder under Basic Integrations and says that connection sends a new lead’s name, email, and phone. See Follow Up Boss’s iHomefinder entry. These descriptions refer to the documented connection into Follow Up Boss, not a universal comparison of the two products or every available iHomefinder workflow. Confirm the connection type and data fields used in your own account.
4. Verify who gets the lead
Confirm that the expected agent is assigned, not just copied on a notification. Test cases where assignment depends on geography, lead source, listing agent, property type, or round robin. Also check what happens if the assigned agent is unavailable: does the lead wait in a queue, get rerouted, or sit unassigned, and who gets notified?
Routing can be set up in both the website/IDX system and CRM. AgentFire’s Lead Manager instructions describe routing by a visitor’s site action or by the page/source that generated a lead. AgentFire: Lead Manager routing options. Follow Up Boss calls its source-based assignment settings Lead Flow rules: rules that decide which agent receives a lead from a particular source. Its support page says a lead provider can assign a lead directly, in which case that provider’s assignment bypasses Follow Up Boss’s Lead Flow rules. If you want Follow Up Boss to assign the lead instead, its instructions say to turn off the provider-side routing rule. Follow Up Boss: Direct team lead routing by lead providers.
Make sure you know which system makes the final assignment, and test the actual result rather than assuming that the CRM rule always wins.
5. Confirm the alert and next action
Ask the assigned agent what alert they received and when. Check email, text, push, or desktop notification settings, then verify that the expected follow-up task or process starts. A CRM record can be easy to miss if it does not trigger an alert or appear in the agent’s normal work queue.
Follow Up Boss says a new lead is assigned according to that source’s Lead Flow rules; the assigned agent can be notified by email, text, push, or desktop; and an inquiry can trigger an automatic text or an action plan. An action plan is a preset sequence of follow-up steps. For an existing lead, a new inquiry can also trigger an automation, such as an email and a task. These features depend on your settings, so check the workflow in your test account. Follow Up Boss: How lead inquiries are handled.
What to do when a test fails
Use the failure point to narrow the search:
- The form displays success, but the website/IDX lead manager has no record: check the form’s submission settings and required fields.
- The website/IDX manager has the lead, but the CRM does not: check the connection, credentials (such as an API key), email forwarding, and field matching. Field matching means checking how the website’s form fields, such as name, email, and source, line up with the CRM’s fields.
- The CRM record is missing context: ask which details the connection sends and whether a different connection type or form setup can send the fields you need.
- The record has no owner or the wrong agent: inspect the routing rules in both systems. Check which system makes the final assignment and whether a provider-side rule is taking priority.
- The agent receives no alert or follow-up does not start: review notification preferences, source-specific follow-up settings, and the conditions that determine whether an automation starts. If an automated text or email only runs for contacts marked as eligible to receive it, verify the test contact’s settings; do not change those settings just to force a test message.
- A returning lead looks wrong: use the returning-lead check above to review duplicate matching, source history, and assignment behavior.
When you contact support, include the submission time, test email or identifier, page/form used, what you expected, what actually happened, and a screenshot of the relevant record or status. Start with the website/IDX vendor if the lead never appears in its lead manager; contact CRM support if it arrives there but fails to transfer, assign, notify, or start follow-up. Ask your admin to check both systems if the point of failure is unclear.
Keep the test on your calendar
As a practical default, repeat the test after any website, IDX, CRM, form, routing, or notification change, and once every quarter even if nothing changed. A solo agent can test one buyer inquiry and one seller inquiry if both forms are in use. Teams should include the routing cases most likely to fail, such as a new lead source, a new territory, or an unavailable agent.
Related ATG guides and reviews
For platform details, see the AgentFire review and iHomefinder review. For CRM selection and follow-up workflows, browse ATG’s real estate CRM guide and the Follow Up Boss review. If you are considering a redesign or IDX switch, return to the website and IDX platform guide.
Editorial note
Vendor documentation checked November 7, 2026. ATG has not hands-on tested these integrations or inspected an agent’s website or CRM account. This research-based checklist describes a way to test your own setup; connection behavior can vary by plan, connection type, account settings, and vendor updates.