Push and email notifications to owners: how to configure them without overload

Push and email do not do the same job

A push notification is immediate and visible, ideal for events that need short-term attention: an urgent notice, a fault in a shared service, a reminder for an imminent owners' meeting. It is ephemeral, though: if the owner does not open it right away, it tends to get lost among the phone's other notifications. Email, by contrast, stays in the inbox and suits messages the recipient must be able to find and keep, such as the alert about a new document or the summary of a payment deadline.

The practical rule is simple: push draws attention, email leaves a consultable trace. Many events deserve both, but not all of them. Blurring the two channels, sending every message as push or entrusting email even with alerts that need an immediate reaction, reduces the effectiveness of both.

Mapping events to channels

Before enabling notifications it helps to decide, event by event, which channel makes sense. A reasoned mapping avoids both information gaps and background noise. Here is a starting outline to adapt to the individual condominium:

• New document in the reserved area: email, with a discreet push if the document is relevant to everyone.
• Upcoming payment deadline: reminder email, with a same-day push only if the internal communication rules provide for it.
• Urgent notice about a shared service, for example a water or elevator outage: immediate push, followed by an email summarising duration and reason.
• Owners' meeting notice: the legally valid channel required by Article 66 of the implementing provisions of the Italian Civil Code, with push and email only as an additional reminder, never as a replacement.
• Individual message, for example a personal payment reminder: the channel reserved to the single owner, never on the board or in bulk sends, out of respect for the GDPR.

Calibrating frequency to avoid noise

Overload almost always comes from repetition. Three reminders for the same deadline, a notification for every minor change to a document, an alert every time the administrator updates a case: the owner quickly learns those notifications require no action and turns them off. Once the channel is silenced, even the important alert will no longer get through.

It is better to group minor updates into a periodic message and reserve the single alert for events that genuinely change something for the recipient. If the platform allows it, a weekly or fortnightly digest of what has been published cuts the number of sends without taking information away from those who want it.

Leaving owners in control of their preferences

A good notification system does not impose the same channel on everyone. Those living away will prefer email, those always in the building may be fine with push, some owners will want both to miss nothing. Letting each person choose their channels and frequency increases the chance the alert is actually read, because it arrives in the way that person said they prefer.

Outside this freedom remain the communications the law requires in a qualified form: the meeting notice and the acts that must guarantee proof of receipt follow the forms set by the rules and do not depend on notification preferences, which govern the day-to-day informational channel.

Checking that the alert arrived

Configuring notifications is not enough: you need to verify they reached the recipients. A delivery or read receipt, when the platform offers it, helps the administrator distinguish between those who were informed and those who were not, a useful element in disputes over ongoing operational matters. This receipt does not carry the same evidentiary value as the formal notices required by law, but it documents diligence in spreading the information.

In AmministraPro, push and email notifications are integrated with the condominium's board, documents and deadlines, so the administrator picks the right channels for each event and verifies who received and read every alert. The available features are described on the features page at /funzioni, while the plans and their limits can be compared at /prezzi.

Frequently asked questions