Communication
Operational messaging
Communication in Abode is valuable because it stays attached to the operational object: a work order, a lease, a property, or a scoped audience. That makes follow-up auditable instead of leaving it trapped in personal inboxes.
Channels
Announcements, email integrations, in-record threads, portal messaging
Best fit
Collections, maintenance coordination, renewals, owner updates
Failure mode to avoid
Detached outreach without record context
Interactive example
Channel selection preview
Choose the message surface based on the record that needs follow-up, not based on who happens to be online.
Broad audience
Best when everyone needs the same update and no single record owns the conversation.
Use the right communication surface
Different message types belong in different parts of the product.
| Need | Best surface | Why |
|---|---|---|
| Portfolio-wide notice | Announcements | Broad audience, low record specificity |
| Maintenance coordination | Work-order thread | Status, approvals, attachments, and vendor context stay attached |
| Lease follow-up | Lease or applicant context | Offers, questions, and document state remain visible to the team |
| Owner visibility | Owner portal statements and updates | External visibility without broad dashboard access |
Keep the conversation anchored
The point is not just message delivery. It is preserving the next action and the evidence trail.
- If the message is about a job, keep it on the work order.
- If the message is about a lease or balance, keep it with the resident and lease context.
- If the message is informational and broad, use announcements instead of private one-off outreach.
Message history should help the next operator
The goal is fewer dropped handoffs and fewer hidden commitments.