Overview
Most things that go wrong in a business were known by somebody, somewhere, in time to act — but the person who could act was never told. A credit limit was passed. A shipment slipped. An approval sat unread for a week.
Nama ERP’s notification system closes that gap. It watches events as they happen, decides who needs to know based on the record itself, and reaches them through the channel they actually read — in-app, email, SMS or WhatsApp.
Features
Triggered by real events, not a nightly report
The system detects business events as they occur: a record created, updated or deleted; an approval approved, rejected or returned; a status change to draft, cancelled or revised; a print; even a processing failure. When an event fires, rules are matched against the entity type, the kind of change, any additional conditions you set, and a priority order — so the right rule wins when several could apply.
Recipients worked out from the record
The hardest part of any alerting system is deciding who to tell. Nama ERP resolves recipients several ways, and they can be combined:
- From a field on the record — the salesperson on the invoice, the manager on the request. The recipient follows the data instead of being hard-coded.
- From a query — any rule you can express against the database.
- By role or position — everyone who holds a responsibility, not a list of names that goes stale.
- Explicitly — when a fixed recipient is genuinely the right answer.
Delegation is handled for you. If someone has a stand-in for a period, the stand-in is added to the recipient list automatically — so notifications do not quietly pile up in the inbox of somebody on leave.
Four channels, one rule
The same notification definition can deliver in-app, by email, by SMS, or over WhatsApp. Messages are built from templates that carry the record’s own data, so an alert arrives with the document number, the customer and the amount in it — enough to act on without opening the system.
SMS and WhatsApp are configured centrally in Global Configuration, with support for regional providers including SMS Misr in Egypt and Taqnyat in Saudi Arabia.
Where it fits
Notifications carry the news; approval cycles carry the decision; Entity Flows carry the action. A rule that says tell the credit controller when this customer passes their limit is a notification. A rule that says do not let the order save at all is a flow. Most businesses need both.
Read the full notifications documentation, including SMS and WhatsApp setup.
