For Realtor.com lead follow up, first identify the product and what has already happened: a delivered inquiry needs a response, while a completed live transfer needs continuity. Preserve the property request, assign one accountable owner, check the permitted next action and record the actual outcome. Do not trigger another first-contact sequence simply because a second notification arrived.
This guide is a proposed operating procedure for U.S. agents and team leaders, not a fixed contact cadence or a promise of more closings. It combines documented product distinctions with a practical delivery-and-handoff test. It does not claim a Callion partnership or integration with Realtor.com.
Identify the product before choosing the next step
Realtor.com lists separate dashboard access for Connections Plus and ReadyConnect Concierge, describing the latter as live-transferred leads. Realtor.com dashboard directory That distinction matters operationally: a source label alone does not tell the receiving agent whether a conversation has already taken place. The directory is product documentation, not independent evidence of conversion lift.
Use the original notification and your account's product context to classify the record. If the product or transfer outcome is unclear, assign a reviewer instead of guessing. The table below is an editorially proposed decision aid, not a statement that Realtor.com applies these exact statuses.
| Observed situation | Verify before acting | Proposed next step |
|---|---|---|
| New inquiry delivered, no conversation recorded | Original request, property reference, assigned owner and approved channel | Owner addresses the request through an eligible channel |
| Live introduction completed | What was discussed and promised, who accepted responsibility | Continue from the conversation rather than repeat a generic introduction |
| Transfer attempted but outcome unclear | Whether anyone actually spoke with the prospect | Resolve the record before describing the lead as contacted |
| Notification appears to repeat an existing inquiry | Source reference, contact identity and earlier actions | Reconcile the events under one active owner |
| Prospect requests a later time | Agreed date, time zone, channel and owner | Record the agreed next step rather than restart intake |
| Prospect says the request is no longer relevant | Actual request and any stop instruction | Record the outcome and stop or route according to the approved process |
A delivered alert, answered call, qualified conversation and booked appointment should remain different evidence states. Avoid marking a lead contacted solely because a phone notification was accepted.
Test delivery before troubleshooting agent effort
If you use Follow Up Boss, begin with its current Realtor.com integration guide rather than assuming every Realtor.com product uses the same connection.
Follow Up Boss documents a Connections Plus API integration alongside required email parsing; its alternative email setup includes a Send Test step. Follow Up Boss integration instructions The guide also specifies enabling Lead Processing for its connected-email route. These are vendor-documented setup paths, not proof that your account is connected or that Callion participates in this integration.
Have an authorized account administrator perform the documented setup. Keep API credentials out of notes, shared spreadsheets and customer records. Use controlled test contact details, and make sure a delivery test cannot accidentally launch outreach to a real prospect.
For each route enabled in your account, inspect the receiving record. Saving a credential is not the end of the test. The following worksheet specifies evidence to capture; it does not assert that every source exposes all these fields.
| Test | Evidence to inspect | Do not call it passed when... |
|---|---|---|
| Controlled inquiry arrives | Source/product label, original request and receipt time | Only an email exists and nobody can find the working record |
| Owner receives the work | Assigned person and acknowledgment | An alert was sent but responsibility is unclaimed |
| Property context survives | Correct property reference or a clearly marked missing-context task | Agent must guess which property prompted the request |
| Existing inquiry receives another event | Prior conversation is visible and duplicate work is resolved | A second owner starts an unrelated first-contact sequence |
| Handoff is completed | Receiving agent, agreed next step and acceptance | A task was created with no accountable recipient |
| Failed delivery is investigated | Failure reference, resolution owner and retest result | Retrying is assumed to have fixed the record without inspection |
Reconciliation rules depend on your systems. Do not merge two people solely because they share a phone number, or discard a distinct new property request as noise. Preserve the source evidence and ask a reviewer when identity is ambiguous.
Continue the conversation that actually occurred
Write the next message from the observed state. The examples below are original wording suggestions for use only after the brokerage has established that the chosen contact is appropriate. They do not authorize automated calling, texting, late-night outreach or any particular number of attempts.
For a new property inquiry with no prior conversation:
Hi [name], this is [agent] with [brokerage], following up on your Realtor.com request about [property]. What would be most useful next: checking the current details or discussing a possible viewing?
For a completed introduction where the prospect already explained the request:
Thanks for speaking with me. I have your request for [specific next step]. I’ll [agreed action] and follow up [agreed timing]. Is there anything important I missed?
For an unclear transfer outcome, first review the available internal record. Do not send “great speaking with you” unless that conversation happened. Once context is resolved, use wording that accurately describes your own involvement.
If availability has not been verified, say you will check it. Do not imply that a viewing is booked, a property is still available or another agent has agreed to a handoff before those facts are confirmed.
Make the appointment handoff unambiguous
Record the appointment purpose, date, time zone, participants, location or meeting link and receiving agent. Keep proposed, confirmed, rescheduled, canceled and attended outcomes separate. A calendar entry is not evidence of attendance.
Google Calendar supports assigning a time zone to an event and displays events in each viewer's time zone. Google Calendar time-zone guidance This is calendar behavior, not a guarantee that a prospect has accepted an invitation. When arranging a conversation across time zones, confirm the intended local time in plain language and inspect the saved event.
Before closing the handoff, ask the receiving agent to confirm they have the request and can take the next step. If the lead is not ready for an appointment, record the agreed reason and next review task instead of creating a fictional booking.
For professional questions outside the responder's role, hand off to the appropriate person. This procedure does not decide consent, permitted contact hours, housing eligibility, financing or legal obligations; those require the brokerage's separately approved process.
Review exceptions, not just activity totals
A weekly delivery review can sample unanswered assignments, missing property context, duplicate-work incidents and unresolved transfer outcomes. Pick records from each enabled product or delivery route so a healthy route does not hide a broken one.
Keep the denominator clear when reporting results: all eligible inquiries, completed introductions and held appointments answer different questions. Use the lead conversion measurement guide for outcome definitions rather than counting every alert as a new prospect or every task as a successful contact.
For broader responsibilities, use the lead response ownership plan. The lead-source resource hub provides related reading. This Realtor.com-specific guide owns product identification and delivery-to-conversation continuity, not a universal portal script.
Start with one verified route and demonstrate the worksheet with controlled records. Expand only after the team can show who handles the exceptions. That is an acceptance test for your operating process, not evidence of a particular response speed or sales improvement.