When should you use it?
- Leads message at all hours and wait for an agent
- Your listings are stored somewhere searchable with photos
- Agents lose leads when they're busy showing homes
Not for: Negotiating price or giving legal or mortgage advice; Firms without a calendar the assistant can check
What do you need, and what do you get?
You need
- A chat channel such as Telegram or WhatsApp
- A searchable property database with images
- Agent calendars and a CRM
- Voice-note transcription
You get
- Contact details captured before anything else
- Qualified leads with budget, area, type and size
- Booked viewings with confirmation emails and CRM records
How does it work, step by step?
- Capture contact firstAsk for name, email and phone before answering in depth, so no lead is lost mid-chat.
- Qualify in four questionsPrice range, area, kind of home and number of bedrooms are enough to search.
- Search by meaningMatch the request to listings in your knowledge base and send the top results with photos.
- Book on live availabilityCheck the agent's calendar, book the slot, and email a confirmation with property details and the agent's contact.
- Handle voice notesTranscribe them and treat them like text.
- Log everythingWrite each lead and conversation outcome to the CRM as it happens.
The prompt
Our own prompt, inspired by Chibugo (@__chibugo) 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 {assistant_name}, the property assistant for {agency}. First ask for name, email and phone. Then ask budget, preferred area, property type and bedrooms. Search listings only with the tool result {listings}; show up to three with photos and one line each. To book, offer slots only from {agent_calendar}, confirm the time back, then send a confirmation with address and the agent's contact. Hand off to a person for price negotiation, mortgage or legal questions. Log every lead with status.
Inspired by Chibugo (@__chibugo): Built an AI property assistant for a luxury real estate company. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Asking for contact details before helping can feel abrupt; explain why and keep it short.
- Listing data must be current, or the assistant will show homes that are already under offer.
Our take
The author's line that speed to lead wins the client is the reason this pattern earns its keep. In property, an inquiry that waits an hour often goes to whoever answered first. Erica's order of operations is sensible: secure contact details, qualify quickly, show real listings, then book against a real calendar. Two pieces need more care than the demo suggests. First, the property knowledge base has to be updated whenever listings change status, or the assistant will confidently offer homes that are gone. Second, confirmations should go out only after the calendar write succeeds, with the agent notified at the same moment. Write a short list of questions the assistant must hand to a person, like price negotiation, mortgage questions or legal terms. For a luxury firm, tone matters, so review a week of transcripts with the team before going fully live. Voice-note support is a smart inclusion; many buyers prefer it, and transcription makes those leads searchable.
Where the time goes back: Speed to lead no longer depends on an agent being free, and the CRM updates itself.
FAQ
Why Telegram?
Who handles the viewing?
Source and credit
Inspired by Chibugo (@__chibugo). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Built an AI property assistant for a luxury real estate company
- Creator
- Chibugo (@__chibugo)
- Published on
- X
- Original date
- Mar 9, 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.