Notification package
The bill is issued — how does the resident hear about it?
Four channels
- EmailCarries the document
- SMSHighest reach
- Browser notificationFor panel users
- Mobile app pushiOS and Android
Channels
Four channels, one send
The unit-specific link to the cost allocation statement goes out by email, from your corporate sender address and in a template built around your brand. The document itself can be attached.
- Unit-specific statement link
- Corporate sender address and template
- Open and invalid-address reporting
SMS
It reaches the resident who never opens their email. The message body is editable per project rather than fixed, and the link is shortened before sending.
- Per-project message template
- Shortened unit link
- Operator delivery status
Browser notification
Instant alerts for people working in the panel: the reading round finished, a modem dropped, a period was closed, a work order is awaiting approval. The page does not need to stay open.
- Reading and modem alerts
- Work order and approval reminders
- Permission per device
Mobile app push
A push notification landing in the resident app. It appears on the lock screen when a bill is issued, when the payment date approaches, or when there is an announcement for the building.
- Billing and payment reminders
- Building and block announcements
- Quiet hours and notification preferences
Mobile app
In the resident's pocket, under your brand
The resident sees their own unit
The app shows the cost allocation statement for their unit, consumption history period by period, and the payment due date. No panel account is needed — unit-specific access is enough.
- Statement with the full breakdown
- Consumption history by period
- Due date and status
Push at the right moment
The notification lands the moment a bill is issued, and a reminder follows as the due date approaches. Management can also send announcements at block or project level.
- Billing notification
- Payment reminder
- Announcements from management
Published under your brand
The app is built with your name, logo and corporate colours and published on the App Store and Google Play through your own developer account. Your residents download your app.
- App Store and Google Play
- Your name and corporate identity
- Your own developer account
The field team works there too
Reading tasks, barcode meter matching and photo evidence run in the same app. The technician signs in with their own account and sees only their own tasks.
- Reading tasks and index entry
- Offline operation
- Photo-backed fault reports
Taken together with self-hosted deployment, the whole stack becomes yours: the panel opens under your name, documents carry your identity, and the app is published from your developer account. The resident only ever sees your brand.
Delivery management
Who was reached, and who was not
Closing the period sends it
Where automatic notification is enabled on a project, sending starts on the selected channels the moment the period is closed. There is no separate job to run.
Consent is held per channel
Only the channels a person has consented to are used. Consent status and its change history are recorded, which matters for data protection.
Delivery report with reasons
After sending, one report shows who was reached on which channel and, where delivery failed, why: no number, invalid email, consent withdrawn, app not installed.
Missing contact filter
Records without a phone number or email are collected in a separate list; closing that list before the period close raises your reach rate.
Template management
Email and SMS bodies are editable per project. Corporate signature, contact details and payment instructions live in the template.
Resending
Sending can be repeated for records that were not reached; no duplicate notification is created and every attempt is written to the report.
Flow
From period close to delivery report
Automatic notification is enabled on the project and channels are selected.
Phone numbers, email addresses and consent flags are completed on contact records.
Email and SMS templates are adapted to your corporate identity.
The period is closed.
Notifications go out on the selected channels to people who have consented.
The delivery report is produced; failures are listed with a reason and can be resent.
At a glance
- Channels
- Email · SMS · browser notification · mobile app
- Trigger
- Period close (automatic) or manual send
- Consent
- Per channel, held on the contact record
- Report
- Delivery report with reasons, by person and channel
- Mobile app
- iOS and Android; published under your brand
- Package
- Notification package is priced separately, per channel
Frequently asked questions
What people ask about notifications
Do residents have to install the app?
No. The app is an additional channel; residents who do not install it receive the same notification by email and SMS, and the unit-specific link opens in a browser. The app is an advantage for residents who want consumption history and instant notifications.
Is the app published under our brand?
Yes. The app is built with your name, logo and corporate colours and published on the App Store and Google Play through your own developer account. Your residents download your app.
How is SMS charged?
SMS carries an operator cost and is charged separately within the notification package. How many messages went out and how many were delivered appears in the delivery report.
Will someone who has not consented receive a notification?
No. Only channels a person has consented to are used, and consent status and its history are recorded. A channel without consent appears in the delivery report with that reason.
Is the notification package mandatory?
No. It is a separate package; without it you print cost allocation statements as a posting list and distribute them by hand. The package can be added later.