Notifications
Real-time in-app, browser and mobile notifications for the work your team is already doing in Solidlio, with per-person control over what arrives and when.
How Solidlio helps
Every event that needs a human writes one notification to the specific people it concerns — the queue’s members, the named approver, the assignee — and delivers it three ways at once: to an open event stream so the bell moves within the second, to the browser as a web push, and to the phone as a mobile push carrying the Android notification channel its urgency deserves. Each person decides which of 42 notification types they want, sets a quiet-hours window in their own time zone, and can mute everything for up to a week. A type switched off is never created; a notification held back by quiet hours is still waiting in the inbox.
Capabilities
| Capability | What it does |
|---|---|
| Notification centre | A paged inbox per portal with all/unread filtering, mark-read, mark-all-read and delete |
| Mobile push | Push notifications to every active iOS and Android install, with the app badge set to the live unread count |
| 42 per-type switches | Eight categories, served from the server’s own catalog so no switch exists for a notification nothing sends |
| Quiet hours | A daily window evaluated in the person’s IANA time zone, including windows that cross midnight |
| Mute | A stop on in-app and push delivery for 30 minutes to one week; nothing is lost |
| Queue-level control | Per ticket queue: notify on arrival, on SLA risk and breach, on a ticket left unassigned past its timeout |
Built for MSPs and their clients
Notifications are addressed to a person, and a person belongs to one side of the relationship. MSP staff are told about the queues and clients they service; client staff are told about their own tickets, changes and assets. Neither side can read the other’s inbox, and every read, acknowledgement and delete is matched on the notification id and the caller’s person id.
| Organization | MSP | |
|---|---|---|
| Who gets ticket alerts | Its own queue members and assignees | Its own queue members, plus shared queues its clients route into |
| SLA warnings | On its own queues | On every queue it services |
| Change approvals | Its own approvers and CAB members | Also notified when a change is escalated to it for sign-off |
| Co-management events | Invitation received, link accepted or declined, access ended | Request received, link accepted or declined, access ended |
| Preferences | Each person sets their own | Each person sets their own |
| Queue notification switches | Set by its own queue administrators | Set on the queues it owns |
How it works
- Something happens — a ticket is assigned, an SLA clock passes its warning threshold, a change reaches an approver, a warranty enters its last 30 days.
- Preferences are applied. If the recipient has that type switched off, nothing is created. If they are muted, or inside their quiet-hours window, the interruptive channels are skipped.
- The bell moves. The badge count, the dropdown and any open notification centre update without a refresh; a toast appears with the title and body.
- The person acts. Clicking opens the ticket, change, project or asset the notification is about, resolved against the portal they are in, and marks it read on the way.
Compliance and audit
Every notification is a durable row: recipient, type, title, body, structured payload, deep link, owning tenant, creation time, and the time it was read. That makes “who was told, and when did they open it” answerable after the fact — for an SLA dispute, a change-approval review, or a co-management consent decision.
Notification rows and preference rows are both covered by the platform’s GDPR erasure path and by the subject-data export, so a person’s notification history leaves with them.
Integrations
Subscriptions are stored per browser and removed automatically when the provider reports one as gone.
Push notifications — iOS and Android delivery for the Solidlio mobile app.
Plans and access
Availability depends on your plan, role and account permissions. Capacity limits and service terms apply. Compare current plans and integration requirements, or ask us about your setup.
The alert that arrives on the phone of the person who can still do something about it.