Real estate websites & follow-up
A daily follow-up review for real estate agents
A long follow-up list does not tell you what to do next. Start with unanswered questions, promises due today and enquiries that nobody owns. For each one, leave a clear next action—or a clear reason not to contact the person.
You can do this in a notebook, a spreadsheet or your existing CRM. The routine below is a suggested way to review your work, not a prescribed contact schedule or a tested automation.
Review the exceptions first
Look for four things: a new request without an owner, a commitment that is due or overdue, a record missing information needed for the next step, and a request to pause or stop contact. You do not need to send a message to everyone on the list.
Open the latest conversation before deciding. A reminder written last week may no longer fit a reply received yesterday. If you cannot tell what the person asked for, mark that uncertainty instead of guessing their needs.
Write one action that someone can actually finish
“Follow up” is not a complete task. “Confirm which property the buyer asked about” is. Give that task a named owner and a review date. If you work alone, the owner is you; a team also needs a backup when the assigned person is unavailable.
Keep the next-action date separate from the sales stage. “Review on Tuesday” tells you when to look again. It does not mean the person has booked a consultation or is ready to buy. Change the stage only when the relevant event has actually happened.
Work through three fictional enquiries
These invented situations show the decisions to make. They are not client records or examples of results from our service.
| Situation | Decision to record |
|---|---|
| A new buyer question has no assigned agent. | Missing: an owner and the property reference. Owner: the named duty agent, or the agreed backup. Next action: check the original enquiry for the property reference; if absent, clarify it through an appropriate, permitted reply. Review: today, before marking the question answered. Pause: do not start a generic sales sequence while the request and messaging permission are unclear. |
| A seller asked to speak after a particular date. | Missing: nothing if the request and agreed date are recorded. Owner: the listing agent handling that conversation. Next action: keep the agreed reminder; no new pitch today. Review: on the agreed date, checking for any newer request first. Stop: if the seller withdraws permission, stop the applicable messages and follow the agreed handling policy. |
| A returning contact wants to sell one home and buy another. | Missing: separate next steps for the two needs. Owner: a named agent for each action, with one person coordinating the handover. Next action: record the seller conversation and buyer question separately, without overwriting either. Review: at each agreed next-action date. Pause: check for conflicting messages before enabling follow-up for either need. |
Turn a vague reminder into a useful note
Take the first example. The list says “New buyer—follow up,” but no agent is assigned and the property is blank. Marking the task complete after sending a generic message would leave the original question unresolved.
A useful replacement note is: “Duty agent: check the original form for the property reference today. If it is missing, clarify which property the buyer means using an appropriate permitted reply. Keep the question open until the reference is known.”
If the original form contains the reference, update the note with what you found and set the next specific action. If it does not, leave it unknown. After any reply, record what changed and whether a further action was agreed. A sent message is an activity; an answered question is an outcome.
Pause, stop or hand over deliberately
A preferred contact method is not permission to send marketing. Before using messages or automation, check the applicable channel requirements and your agreed communication policy. Do not turn an opt-out into a reminder to try a different pitch or channel.
If a person asks you to wait, preserve that request and the agreed review date. If they ask to stop, stop the applicable messages and route any uncertain handling to the responsible person. A human taking over a conversation should also check whether scheduled messages need to be paused.
At the end of the review, each exception should have an owner, one specific action, a date to review it and any pause or stop instruction. “Waiting for information” is a valid state when you have recorded what is missing and who will check it.
Decide whether a software setup would help
Try the review manually before adding more automation. If the recurring problem is unclear responsibility, decide the ownership rule first. If the rule is clear but reminders or handovers keep getting lost, you have a concrete requirement to discuss with your setup provider.
In HighLevel, contact fields belong to a person and opportunity fields belong to a particular deal. Its custom-field documentation explains that distinction; it does not make this review an installed workflow. Account behavior and any proposed automation still need separate testing.
Use our real estate GoHighLevel setup brief to turn the decisions into requirements. If you want help with a setup, tell us about your lead sources and the follow-up you need. Share requirements, not private customer records.