Communication
Follow-up patterns
Abode's communication model works when follow-up is visible inside the record that matters. The product is strongest when the team can see the next action without reconstructing history from inboxes, texts, or phone calls.
High-value use cases
Collections, maintenance approvals, renewals, vendor scheduling
Audience control
Owners, tenants, vendors, and internal staff do not share one feed
Operational goal
Next action over message volume
On this page
Audience routing patterns
The same message tone and evidence requirements do not apply to every audience.
| Audience | Typical message type | What should be visible later |
|---|---|---|
| Tenants | Balance reminders, maintenance updates, lease follow-up | Timestamped delivery and linked property / tenancy |
| Vendors | Quote requests, schedule confirmations, completion updates | Status changes, notes, and attached cost context |
| Owners | Performance updates, statements, exceptions | Summary visibility and report attachments |
| Internal staff | Approvals, escalations, reassignment | Responsibility and next-step clarity |
Rules worth enforcing
These conventions keep the communication layer useful at scale.
- Do not use a general message thread when a record-specific thread already exists.
- Treat communication about money as part of the accounting record, not just as outreach.
- Treat communication about work completion as part of the maintenance record, not as a separate approval chain.
- When in doubt, optimize for what the next operator needs to understand without asking for context.
What breaks first
Detached communication fails during handoff. The message may exist, but the context, promise, and next action do not survive team changes unless they are anchored to the operational record.