Implementation playbook
The workflow details buyers need before a demo.
Resolve the practical workflow details before routing callers: what the agent says first, which fields it captures, when it stops, where the record goes, and which plan shape usually fits.
Sample call flow
- Separate tenant maintenance, owner inquiry, leasing lead, vendor call, emergency, and billing intent immediately.
- Identify property, tenant, issue, urgency, and access details
- Route emergencies immediately
- Create a ticket or callback for routine issues
- Confirm the next step, repeat any commitment made to the caller, and write a reviewable summary for the team.
Qualification fields
- Caller role, property address, unit, issue type, access permission, photos note, urgency, and callback number
- Lease or owner context where available, language preference, and after-hours escalation status
- Outcome label, next action, transcript link where allowed, owner, due window, and failed-write status
Human handoff rules
- Transfer flooding, lockout, heat, safety, security, angry tenant, and owner escalation calls
- Create maintenance tickets or callbacks for non-urgent issues
- Transfer or create a callback when the caller asks for a person or the agent is uncertain.
Do not automate
- Do not provide legal advice, lease interpretation, payment commitments, or emergency instructions outside approved scripts
- Do not share tenant or owner data without identity checks
- Do not continue automation when approved knowledge, consent, destination access, or fallback ownership is missing.
Stack handoff
- Property management ticketing, CRM, maintenance board, Teams or Slack escalation, vendor dispatch note
- Structured call summary with intent, urgency, caller details, next action, and review status
Plan fit
- Growth for tenant intake and callback routing
- Scale for multi-property emergency routing and vendor workflows
- Enterprise for custom PMS integrations and stricter access controls