Watching lists every minute is not sustainable. EQLEM notifications bring important events to the people who need them: a push on mobile, a live update in the web session. The goal is not noise; it is delivering action-needed signals to the right person. Pending approvals, critical stock, service assignments or sync failures reach you straight away.
Notifications should respect permissions and scope: another branch’s stock alert should not flood you. That is why the notification model sits on the same backbone as authorization and multi-company.
Who is it for?
Field teams get Push on mobile devices. Office users receive live updates in the web session. Managers want exception and approval alerts. Service and CRM teams need assignment / SLA signals. IT does not want critical integration failures to stay silent.
How it works
An event occurs (new assignment, status change, threshold breach, message). The system delivers a notification to the relevant user or role. Push on mobile, a live channel and a notification centre on web, working together. Clicking a notification opens the related record or list; a navigation shortcut, not a sticky note.
Which events go to whom is shaped by module and setup. CRM service requests, critical stock levels, and approval queues are typical candidates. User message logs and system messages can be monitored in company management. To avoid notification storms, event priority and role targeting matter; not every record change pings everyone.
In limited offline mobile scenarios (SQLite persist), sync and notification catch up when connectivity returns; that must not be confused with fully disconnected real-time. Mobile push and the live web channel are ready today.
Benefits
Response time shrinks: queues become visible when they form, not when someone notices. Dependence on email inboxes drops. Field teams act without returning to the office. Management catches exceptions via notifications alongside the dashboard. Support hears fewer “it sat in the system and nobody saw it” complaints.
Correct targeting controls noise. Wrong targeting does the opposite; so start with a small critical event set at setup.
Relation to modules and products
CRM (assignment, service, outreach signals), inventory (critical levels), sales/approval flows, and integration error states are common producers. Platform Web and Mobile are where notifications appear. Notifications drop you into a list or document screen. System sync failures can alert IT/operations. Together with the dashboard, you get a pull + push visibility model.
FAQ
Is Push required? Push is a strong complement for mobile use; web users work with the live channel and the notification centre. Device permissions depend on the user.
Does every event create a notification? No; and it should not. Start with a critical set, then expand.
Can a notification open a record outside my permissions? Access remains permission-based. Notifications should route to records you are allowed to see.
Is there email notification? CRM outreach and campaign channels are separate. Operational real-time alerts go through mobile push and the live web channel; email is evaluated per scenario.
Next step
Pick at most five critical events per role. Try Free to enable mobile + web notifications; narrow targeting if noise grows. Keep record quality with document entry discipline.