Notifications

The problem

The things that go wrong in an MSP go wrong quietly. A ticket lands in a queue at 4:55pm and nobody looks until morning. An SLA clock runs out while the person who could have stopped it is in someone else’s ticket. A change sits waiting on an approval that its approver never knew about. The usual fix is to email everyone about everything, which lasts about three weeks — until people build a rule that files it all away, and the one message that mattered is filed with the rest.

What Solidlio does about it

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

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.

How it works

1. 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.
2. 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.
3. 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.
4. 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.

Editions

Notifications are not tier-gated.

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.