End-to-End Autonomous Tenant Communication
Run resident communication from intake through action, verified delivery, and durable outcome, with autonomy set per message.
Context-rich execution
Messages and follow-up actions use the actual unit, issue, policy, and workflow state.
Workflow-aware updates
Maintenance and collection status changes generate accurate resident messages.
Consistent voice
Formality and vocabulary match the operator's own writing.
Channel coverage
Email, SMS, and portal actions run from the same workflow state.
Variable autonomy
Each message can run automatically, run and notify, hold for approval, or remain human-only.
Auto-send tiers
Factual confirmations and status updates run on their own.
Commitment gates
Offers, fee decisions, and terms use the configured autonomy mode with context attached.
Required human path
Defined high-impact actions and messages requiring licensed authority route to a qualified person.
Availability and approval rules
Connect your property systems, payments, and communication channels. Available actions depend on your providers, permissions, and workspace rules.
Eligible workflows can run automatically, notify you, wait for approval, or stay human-only. High-Impact Actions defined in the Terms require qualified human review and explicit approval. Legal, safety, licensing, and provider requirements still apply.
Workflow availability, input formats, outputs, permissions, retention, and integrations depend on the enabled workspace configuration and connected source systems.
Where execution meets governance
The end-to-end autonomy model for tenant communication is explained in the tenant communication guide.
Connected workflows
Renewal, collection, and maintenance workflows all feed the same communication layer.
Frequently asked questions
Will residents know they're talking to AI?
Disclosure and tone requirements should match your policy; the workflow is configurable to it.
Can every message require review?
Yes. A workspace can hold every message for approval, or allow eligible messages to run automatically or run and notify.
What about emergency communication?
Safety-critical events follow the configured emergency process and route to the responsible person or service with full context.