Objective vendor comparison
Units-Master vs. casavi
Modern communication portal for tenants and owners.
Executive Summary
casavi is an established communication portal with strong ticketing and mature tenant and owner apps. Workflow automation is manual; telephony AI is sourced from the third-party MANGBL.AI.
Feature comparison in detail
| Feature | ⚡ Units-Master | casavi |
|---|---|---|
| Process Ticketing | Built-in | Built-in |
| Visual Workflow Engine | Built-in | Not available |
| Voice AI (Phone) | Built-in | External vendor |
| In-App AI Chat | Built-in | External vendor |
| In-App Team Chat | Built-in | Partial |
| Owner / Tenant Portal | In development | Built-in |
| Auditor Portal | In development | Built-in |
| Accounting & Reports | In development | External vendor |
| GoBD / BAO Archiving | Built-in | External vendor |
| Service Directory | Built-in | Built-in |
| Banking / SEPA & EBICS | Not available | External vendor |
| WEG Voting & Assembly | Not available | Built-in |
| Meter & Heating DB | Not available | External vendor |
Legend
- Built-in
- Fully part of the vendor's own product, developed and maintained in-house. No extra contract, no data sync, one support line.
- In development
- Not yet usable, but on the active engineering roadmap with a confirmed release window. Relevant for multi-month rollouts that can plan around it.
- External vendor
- Delivered by a separate vendor via integration, add-on or sync. Expect additional licence fees, a second support relationship, and data flowing across two systems.
- Partial
- The feature technically exists, but only at checkbox level: enough to tick the requirement, rarely enough to solve the underlying day-to-day workflow.
- Not available
- Not part of the product. No integration, no roadmap commitment — the workflow has to happen outside the platform.
Strengths of casavi
- Mature native portals for tenants, owners and auditors
- Native service relay catalog for tradespeople
- Native WEG voting module
Weaknesses of casavi
- No visual workflow builder — tickets remain passive inboxes
- Voice AI only via 3P (MANGBL.AI), no deep process integration
- Accounting outsourced (Domus, WohnData) — no end-to-end process flow
Operational differences
01
Process-driven workflows instead of static inboxes
Every ticket in Units-Master triggers an executable, multi-step Standard Operating Procedure (SOP) — no manual tag assignment, no ping-pong between staff members.
02
Native voice AI agent, not a third-party tool
Inbound phone calls are handled entirely by the native voice AI agent: emergency dispatch, intake and ticket creation — autonomously, 24/7.
03
In-app copilot Werner AI: contextual and action-capable
Werner AI is not a generic chatbot. It knows property history, summarises units, prepares accounting data and executes actions directly.
04
Embedded service directory, wired into workflows
The /directory connects local tradespeople, plumbers, HVAC technicians and auditors directly to the automated ticket workflows — no media breaks, no manual coordination.
When each fits
Choose Units-Master when…
- You want tickets that trigger processes — not just an inbox
- Telephony should be handled autonomously by your own software, not a third-party tool
Choose casavi when…
- Your primary need is tenant communication via a portal app
- You already have working bookkeeping you do not want to replace
Last reviewed and updated: 15 August 2026
All information without guarantee. Feature scope may change through product updates from the vendors listed.