Eight records between an inquiry and an accountable handoff
These definitions make the operational state behind a real-estate AI workflow visible. They describe what a custom implementation should preserve; they do not claim that the public PropBot demo has a live CRM, calendar, messaging or property-data connection.
Inquiry source
Preserve where a lead inquiry entered the operation before CRM routing or attribution.
Read definition →Operational recordContact permission
Document the source and scope of permission before automated email, SMS, WhatsApp or voice follow-up.
Read definition →Operational recordQualification profile
Define the explicit buyer or renter requirements collected before a human handoff.
Read definition →Operational recordProperty source record
Keep listing facts, source identity and freshness visible to chat, CRM and scheduling workflows.
Read definition →Operational recordShowing request
Separate a prospect request from a calendar-confirmed property showing.
Read definition →Operational recordCRM owner
Make the person or team accountable for the next lead action visible after automation routes it.
Read definition →Operational recordHuman escalation
Capture why an automated conversation stopped and which accountable person received the context.
Read definition →Operational recordFollow-up stop condition
Define the event that must pause or end automated lead messages.
Read definition →