How does Sonar model multi-dwelling properties?

Sonar models the building hierarchy: properties contain units, units have residents, and contracts cover both, so every workflow respects the structure instead of flattening it.

Can Sonar bill the property and the resident differently?

Yes. Bulk-rate contracts bill the property for base service while retail-rate upgrades bill individual units, kept straight in one ledger with embedded payments for both.

How does Sonar handle move-ins and move-outs?

Move-in workflows fire the install, billing start, and welcome comms, and move-out workflows handle disconnect, final bill, and equipment recovery, with property-manager notifications at each step.

Can support tell a property manager from a resident?

Yes. Property managers and residents are linked on the record, so support routes context by relationship type whether the call comes from the contract holder or the unit.

Sonar 2026 · Issue 04 · For MDU specialists

MDU

Property by property. Unit by unit.

Multi-dwelling unit installs, property manager relationships, and resident churn handled in one platform.

Book a meeting Watch the Platform Tour

Location Tools

AccountsNetwork SitesInventory LocationsVehiclesCustom Overlays

▢

△

MapSatellite

Why MDU is a different game

Two customers per building. One ISP software for both.

Two customers, one record.

The property manager signs the contract. The resident calls support. Generic CRMs can't model both relationships in one place.

Move-in, move-out churn.

Apartment units cycle every 12 to 24 months. Each turn is an install plus a disconnect plus a new customer.

Bulk vs retail pricing.

One contract bills the property at bulk rates. Individual units pay retail upgrades. The ledger has to keep both straight.

Capabilities for MDU operators

Building-aware operations.
From contract to resident.

Sonar models the building hierarchy: properties contain units, units have residents, contracts cover both. Every workflow respects that structure.

Property and unit hierarchy as a first-class concept.

Map every building to its address, every unit to its building, every resident to its unit. Service area mapping shows coverage at the building level.

Building hierarchy with address validation
Unit-level subscriber records
Coverage maps at building granularity

Location & Buildings’s flow

From property contract to wired unit

01
Property mapped
Building added with address validation and unit count.
Location Tools
02
Units provisioned
Each unit gets its own service record under the building.
Accounts
03
Resident added
New tenant linked to a unit, billing and support contact captured.
Accounts
04
Service activated
Unit-level provisioning fires when the resident moves in.
Network & IPAM

A documentary photograph that captures the operational reality behind Sonar's MDU module.

Field reality · MDU

Two customers, one record.

Frequently asked

Common questions about mdu.

How does Sonar model multi-dwelling properties?: Sonar models the building hierarchy: properties contain units, units have residents, and contracts cover both, so every workflow respects the structure instead of flattening it.
Can Sonar bill the property and the resident differently?: Yes. Bulk-rate contracts bill the property for base service while retail-rate upgrades bill individual units, kept straight in one ledger with embedded payments for both.
How does Sonar handle move-ins and move-outs?: Move-in workflows fire the install, billing start, and welcome comms, and move-out workflows handle disconnect, final bill, and equipment recovery, with property-manager notifications at each step.
Can support tell a property manager from a resident?: Yes. Property managers and residents are linked on the record, so support routes context by relationship type whether the call comes from the contract holder or the unit.

Explore related