Preview boundary
This capability is not presented as generally available.
CommunicationsPreview
Connect an operational conversation to the work behind it.
A preview concept for classifying stakeholder messages, attaching context, and routing the next step for review.
Communications conceptPreview
Grounded in product evidence
- User-approved preview boundary
- Illustrative communication workflow
- No claim that Chat is live
The operational problem
Resident, owner, and vendor messages often arrive without the records, procedure, or ownership needed to act consistently.
Operating model
A bounded path from input to visible work.
The exact systems, permissions, exceptions, and recovery behavior are confirmed during workflow discovery.
- 01
Receive a message through an approved intake path.
- 02
Classify the operational request.
- 03
Attach relevant property context.
- 04
Route a proposed next step to a person for review.
Operational controls
Keep scope, review, and evidence visible.
Outbound review
The concept keeps a person in control of consequential communication.
Channel validation
Every channel, permission, and delivery contract requires implementation-specific validation.
Feature boundaries
What this page does—and does not—promise.
Is Communications generally available?+
No. It is explicitly presented as a preview concept in this release.
Which communication channels are supported?+
No public channel-availability claim is made until product and engineering approve the exact contracts.
Can it send messages automatically?+
The preview story places human review before outbound action; exact behavior remains subject to validation.
One clear next step
Start with one operation worth making repeatable.
Bring one workflow and the systems it touches. We’ll separate what is available, what requires configuration, and what remains a preview.
Book an operations demo