# Dwelon features

> Governed agentic operating layer for proactive property operations across leasing, rent collection, maintenance, tenant communication, renewals, approvals, and operational evidence.

Human page: https://dwelon.com/features
Last reviewed: 2026-08-06

## Summary

One operating layer for finding exceptions, applying workspace policy, coordinating the next action, and preserving a reviewable record.

## Governed operating loop

Dwelon connects the signal, decision, execution, and review stages so work does not disappear between separate tools.

1. **Detect the exception.** Renewal windows, delinquency, maintenance SLA risk, and policy deadlines become prioritized work.
2. **Choose the permitted action.** Workspace policy determines what can run, what needs approval, and what must be blocked.
3. **Preserve the receipt.** The outcome, evidence, and operator intervention remain available for follow-up and audit.

## Observe → Act → Verify

| Stage | Meaning |
| --- | --- |
| Observe | Bring portfolio, resident, lease, ledger, and work-order context into one operating view. |
| Act | Route routine work through policy-aware automation and hold consequential actions for review. |
| Verify | Follow execution status, inspect evidence, and recover from exceptions without losing context. |

## Feature themes

### Proactive command center
Review risk signals, due work, and approvals before opening individual records.
Stage: Prioritize

### Policy-aware automation
Set approval boundaries and retain a clear reason when an action is held or blocked.
Stage: Govern

### Leasing and renewal orchestration
Coordinate lead follow-up, applications, lease packets, and upcoming renewal decisions.
Stage: Convert

### Maintenance operations engine
Triage requests, monitor service targets, coordinate vendors, and keep residents informed.
Stage: Resolve

### Auditable execution history
Inspect the action, policy decision, evidence, and outcome from a shared record.
Stage: Explain

### Scenario-driven reliability
Exercise operating scenarios before expanding autonomy across a portfolio.
Stage: Validate

## Product scope notes

- The operating surface draws on a structured catalog of more than 300 named operating actions, classified by autonomy tier before execution.
- Automation is policy-aware, not unbounded.
- Human approval remains part of the product for consequential work.
- Availability depends on integrations, portfolio data, provider readiness, and operator policy.

## Related docs

- https://dwelon.com/ai/use-cases.md
- https://dwelon.com/ai/governance.md
- https://dwelon.com/ai/faq.md
- https://dwelon.com/blog/agentic-ai-landlord-platform