SectorsReal Estate
Real Estate
Lead intake and routine tenant requests are frequent, time-sensitive, and often arrive outside office hours, which fits the same chat, API, and inbound-call pattern as the platform's other use cases.
Where it fits
- Lead intake questions follow a fixed, repeatable script, which is what a flow's branching and database writes are built for.
- Maintenance and tenant requests are routine and frequent enough that an inbound SIP-triggered flow can log and categorize them without a person picking up first.
- A Table database holds leads or maintenance tickets directly, with a real spreadsheet-style grid so staff can review and edit the same records a flow writes to.
What this looks like
- An IF node branching on the answers to a qualification script, writing qualified leads into a Table database as it goes.
- A SIP gateway node so tenants can call in and describe an issue; the flow can categorize the request and log it, but dispatching a contractor depends on a plugin action wired to whatever scheduling system you already use.
- SESSION_CONTEXT_ACTION nodes to carry a caller's answers across turns of the same call, so a multi-question intake doesn't reset between questions.