Most of what changes in Nizam from month to month is small enough that it doesn't warrant a launch announcement on its own — a setting here, a refinement there. But small doesn't mean unimportant, and a few things have either shipped recently or simply never gotten the explanation they deserved. This is a roundup of three of them: complex-wide notification controls, a real explainer on the Advance Wallet, and a proper look at how much is actually built into SOS.
Take Control of Your Community's Notification Noise
Every automated reminder Nizam sends exists for a good reason — unpaid dues need chasing, complaints need following up on, attendance needs tracking, calendar events need not being forgotten. But "exists for a good reason" and "every community wants it, all the time, exactly the way it's configured by default" aren't the same thing. Some committees want every nudge possible going out to residents. Others find a constant stream of automated pings starts to feel like noise rather than help, and would rather rely on their own judgment for some of it.
Complex admins can now toggle four categories of reminders on or off, complex-wide, from Settings:
- Outstanding Dues Reminders — automated nudges to residents with unpaid maintenance bills.
- Complaints Reminders — follow-up notifications on open, unresolved complaints.
- Attendance Reminders — prompts related to staff or event attendance tracking.
- Calendar Event Reminders — heads-up notifications ahead of scheduled community events.
All four are on by default, because for most communities, more reminders means better compliance and fewer things falling through the cracks. But the decision of how much automated messaging a community receives shouldn't be made once, permanently, by whoever built the software. It's the admin's community, and now it's the admin's call — turn any of the four off if it's not serving your building, without losing the other three.
The Advance Wallet, Properly Explained
This one isn't new, but it's underexplained almost everywhere else on the site, and it's one of the more genuinely useful pieces of the billing system once people understand what it actually does.
The Advance Wallet lets a resident pre-pay into a running balance tied to their specific unit — not a vague credit with the complex in general, but a balance attached to that unit specifically. The part that makes it worth explaining properly is what happens next: as future maintenance bills are generated for that unit, the wallet balance is automatically applied against them. A resident doesn't have to remember to use the balance, request that it be applied, or track it themselves. The bill comes due, the wallet covers what it can, and whatever's left (if anything) is what actually needs to be paid.
Pay once, in a quiet month, and forget about maintenance for the next three. The wallet remembers so the resident doesn't have to.
The benefit runs in both directions. For residents, it means being able to pay ahead when it's convenient — after a bonus, before a trip, whenever cash flow allows — instead of being locked into a strict monthly rhythm. For committees, it means more predictable collections: a portion of next month's dues may already be sitting in wallets before the bill is even generated, which smooths out the usual scramble of chasing payments right after each billing cycle. Nobody needs to reconcile it manually — it's simply how the wallet is designed to behave the moment a new bill exists.
See the Advance Wallet in action
Two months free, no credit card, set up in an afternoon.
Start Free — 2 Months on UsJust How Capable the SOS System Already Is
We've written before about what SOS looks like in a real emergency, but the story format skips past a lot of the deliberate design underneath it. SOS isn't a single generic panic button — it's a system with real thought behind both ends of the alert.
Triage starts the moment the button is pressed
Rather than sending a single undifferentiated "help" signal, SOS asks what kind of emergency this is, with dedicated categories: Medical, Security Threat, Fire/Smoke, Lift Stuck, Violence/Harassment, and Other. That category travels with the alert, so the people responding know what they're walking into before they arrive — a guard heading toward a reported fire behaves differently than one heading toward a medical emergency, and knowing which one it is before arriving matters.
A deliberate pause against accidental triggers
An emergency button that's too easy to trigger by accident is worse than useless — it trains everyone, including the people responding, to treat alerts as probably-nothing. SOS requires a deliberate 2-second press-and-hold rather than a single tap, specifically to filter out an accidental brush against the screen while still being fast enough that a real emergency loses nothing meaningful in the delay.
What happens on the receiving end
An alert that arrives quietly is an alert that might not arrive in time. SOS notifications go out on a dedicated push channel built to bypass Do-Not-Disturb settings, so a muted phone doesn't silently swallow an emergency. On the receiving device, it's a full-screen alert with a synthesized siren sound and continuous vibration — designed to be genuinely hard to miss, not a small banner easily dismissed with a swipe. It stays on screen and can only be dismissed with an explicit acknowledgment, not an accidental tap, so there's no ambiguity about whether someone actually saw it.
The trigger, and everyone else
One detail that's easy to overlook: the person who triggers the SOS doesn't get the alert themselves — they already know there's an emergency, they're the one having it. Everyone else in the complex who should be notified gets the full alert, siren, vibration, and category included.
None of this is new — it's been part of Nizam for a while. But it's exactly the kind of detail that's easy to undersell in a features list and only really shows its value when you understand how deliberately each piece was built, from the categories down to the vibration pattern.