When should you use it?
- Your sales team handles property leads over WhatsApp
- You want CRM fields to change as conversations happen
- Declined visits are rarely followed up
Not for: Teams without a maintained property database; Sending unsolicited WhatsApp messages to people who never contacted you
What do you need, and what do you get?
You need
- An Airtable base of leads and properties with image URLs
- WhatsApp Business API access
- Google Calendar and Gmail
You get
- Lead records updated during each chat
- Site visits booked without conflicts and HTML confirmations
- One follow-up per declined lead on the scheduled day
How does it work, step by step?
- Model the lead recordInclude contact, budget, location, type, timeline, requirements, welcome flag, visit state, the follow-up due date and whether it was sent.
- Welcome only onceCheck the welcome flag before greeting, and set it as soon as the first message goes out.
- Send real photosIdentify the exact property first, then fetch its stored image links rather than letting the model produce any.
- Book with conflict checksCheck the calendar before confirming a visit and update status to Scheduled.
- Schedule the follow-upOn a decline, set status Declined and schedule the follow-up for 48 hours later.
- Run follow-ups separatelyEach morning, message leads whose follow-up is due and unsent, then mark them sent.
The prompt
Our own prompt, inspired by u/Jazzlike_Power_6197 on r/aiagents and written to work in ChatGPT, Claude and n8n. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You are the sales assistant for {developer}. Lead record: {lead_record}. If welcome_sent is false, greet once and tell me to set it true. Answer only from {property_data}. When asked for photos, first return the exact property_name so the system can fetch its images; never write image links yourself. To book a visit, check {calendar} for conflicts, then confirm and set visit_status to Scheduled. If the lead declines, set visit_status to Declined and follow_up_date to two days from today. Output any field changes as JSON after each reply.
Inspired by u/Jazzlike_Power_6197 on r/aiagents: I built an AI real estate sales assistant that books site visits, sends emails, follows up, and updates the CRM automatically.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- WhatsApp sends webhooks for delivery and read receipts too; he had to filter them out after the bot replied to itself in a loop.
- Getting the agent to call several tools and still return the exact structured output took him a lot of debugging.
Our take
Small state flags carry this build. A welcome flag, a visit status, a follow-up date and a follow-up-sent field are enough to make a chatbot behave like a careful salesperson: it doesn't repeat itself, it remembers outcomes, and it follows up exactly once. That's a pattern you can reuse in any WhatsApp sales flow. The image rule is just as good. By fetching photos from the property record only after the property is identified, the author removed a whole class of embarrassing mistakes. His two debugging stories are the practical warnings: filter WhatsApp status events or you'll get loops, and expect effort to make tool calls and structured output agree. Keep the daily follow-up job separate and idempotent, as he did. Before launching, confirm your WhatsApp templates are approved for business-initiated messages, and write down which questions about price, legal terms or financing go to a human. Review a sample of conversations each week to catch drift.
Where the time goes back: Status changes, bookings and follow-ups happen inside the conversation instead of in a separate admin pass.
FAQ
Why three workflows?
How does it avoid wrong images?
Source and credit
Inspired by u/Jazzlike_Power_6197 on r/aiagents. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I built an AI real estate sales assistant that books site visits, sends emails, follows up, and updates the CRM automatically.
- Creator
- u/Jazzlike_Power_6197 on r/aiagents
- Published on
- Original date
- Jun 28, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.