Start with the job
Why this workflow exists
Viewing notes stay in phones, notebooks, and inboxes until follow-up is late.
Agents miss useful context and buyers receive generic follow-up.
A property viewing is marked complete.
Evidence and assumptions
What this playbook assumes
Viewing notes stay in phones, notebooks, and inboxes until follow-up is late.
The real estate agent already has access to the source system and can approve the output.
AI does not make the final customer, candidate, property, campaign, or client-facing decision.
Last reviewed: 2026-08-05
AI workflow
Where AI helps, and where a person decides
The workflow is useful because each automation step ends at a named human checkpoint.
Capture viewing notes
Record buyer questions and signals while context is fresh.
- Input
- Agent notes or voice memo
- AI action
- Structure preferences, objections, and unanswered questions.
- Human checkpoint
- Agent corrects the note before it is saved.
- Output
- Structured viewing note
Draft follow-up
Write a relevant, respectful follow-up.
- Input
- Viewing note and property facts
- AI action
- Draft a message and suggest useful next information.
- Human checkpoint
- Agent approves and personalizes.
- Output
- Follow-up draft
Set next action
Make the next step visible.
- Input
- Approved follow-up
- AI action
- Suggest next date and task based on stated intent.
- Human checkpoint
- Agent confirms the action.
- Output
- CRM task
Choose with context
What should your team do next?
Answer three questions to find the most practical next step for your current system, capability, and strategic need.
Answer the questions to choose a path for this workflow.
Strengthen team capability
The team needs a consistent post-viewing routine with its current CRM.
Trade-off: Agents still own tone and next-step judgment.
Open the capability routeUse an existing tool
The CRM already creates follow-up from viewing activity.
Trade-off: Less control over note structure and message quality.
Check your current systemCreate a custom workflow
The agency has high viewing volume and a stable follow-up policy.
Trade-off: Needs reliable mobile capture and CRM integration.
Review the custom workflow routeRecommended next move
Start with the capability map below. It connects the selected workflow step to a focused resource and a concrete deliverable.
Open the capability routeKeep your current system if it can preserve source context, expose missing data, allow human editing, and keep observed facts separate from generated interpretation.
Follow Up Boss · Real estate lead and follow-up platform
Compare Follow Up Boss for this workflow
- Best when
- Your current system cannot preserve the required workflow inputs, controls, or review states.
- Avoid when
- Your existing system already satisfies the workflow requirements and keeps the data in one place.
- Why it fits
- Compare Follow Up Boss when the current system fails one of the workflow requirements.
- Limitation
- Provider defaults may not match your fields, permissions, or review policy.
- Trade-off
- Faster setup with less control over vendor-specific workflow behavior.
Related template or use case: Open provider guidance
Alternative: Use the automation feature in your current platform · Last checked 2026-08-05
Create a custom workflow when the process is differentiated, integration-heavy, or sensitive enough to require ownership of data boundaries, approvals, and maintenance.
Make · Automation layer
Create this workflow with Make
- Best when
- The workflow repeats often enough to justify visible automation and an owned handoff.
- Avoid when
- The workflow is still changing or the team has not agreed on source ownership and human approval.
- Why it fits
- Make can support the workflow's explicit handoffs before a custom backend is justified.
- Limitation
- The team still owns configuration, monitoring, and the final human checkpoint.
- Trade-off
- More control than a fixed product, with more setup and maintenance responsibility.
Related template or use case: Open provider guidance
We may earn a commission if you sign up through this link.Alternative: Use the automation feature in your current platform · Last checked 2026-08-05
Railway · Application and infrastructure layer
Create this workflow with Railway
- Best when
- The workflow repeats often enough to justify visible automation and an owned handoff.
- Avoid when
- The workflow is still changing or the team has not agreed on source ownership and human approval.
- Why it fits
- Railway can support the workflow's explicit handoffs before a custom backend is justified.
- Limitation
- The team still owns configuration, monitoring, and the final human checkpoint.
- Trade-off
- More control than a fixed product, with more setup and maintenance responsibility.
Alternative: Use the automation feature in your current platform · Last checked 2026-08-05
Capability map
What does your team need to operate this workflow?
Choose a step and your current level to see the shortest route to a useful deliverable.
AI follow-up drafting
The draft should reflect the viewing without making pressure or advice decisions.
Recommended learning route
Using AI in Make
Use the course foundation for drafting and task handoff, then keep agent approval explicit.
Ready-to-use artifact
Viewing note
This is the complete operating template for the workflow: input contract, runbook, automation handoff, human review, escalation, and a test case.
Workflow template
Open the complete operating runbook
The full Markdown stays out of the page until you ask for it. Open it when you are ready to adapt this workflow to your team.
What happens next
- Capture viewing notesStructure preferences, objections, and unanswered questions.
- Draft follow-upDraft a message and suggest useful next information.
- Set next actionSuggest next date and task based on stated intent.
Check before action
- Capture viewing notesAgent corrects the note before it is saved.
- Draft follow-upAgent approves and personalizes.
- Set next actionAgent confirms the action.
CRM task
Test the filled template on one real but non-sensitive example. Keep the source context and approval decision with the team that owns this workflow.
Implementation stack
What the workflow needs
Automation and AI usage
CRM subscription · Messaging fees
Explore the product angle
Ideas connected to this workflow
Use this workflow inside an agency, or explore product ideas built around the same operational problem.
SaaS WorkflowHospitality & Travel
Vacation Rental Owner Portal with Dynamic Pricing & Guest Messaging
A focused SaaS workflow for short-term rental hosts to manage multiple properties, sync calendars, apply dynamic pricing, automate guest messaging, and dispatch cleaning crews from one dashboard.
Internal ToolReal Estate
Real Estate Lead Pipeline CRM
A focused CRM for agents to qualify property inquiries, schedule the next contact, move opportunities through deal stages, and see overdue follow-ups.
Next workflows
Related playbooks
Real estateReal estate agencies
Listing draft and approval
Turn verified property facts into a listing draft while preserving source links and broker approval.
Real estateReal estate agencies
Lead response and qualification
Respond to inbound property leads quickly, collect missing context, and route the next action to an agent.