Skip to content

Email & Push Notifications

Alerts for assignments, approvals, overdue work, low stock and condition breaches, delivered to the in-app inbox, the phone, email and, where set up, WhatsApp.

Updated

Find it: The bell icon in the header opens My Notifications. Admins manage rules under Notifications in the Admin group of the sidebar (tabs Rules and Logs); WhatsApp is under Admin → WhatsApp; the email provider is under Settings → Email.

Notification settings screen with notification rules and an in-app inbox of recent alerts.

Sound familiar?

  • "Did anyone see that urgent ticket?"
  • "I was on the floor. I didn't see the email until hours later."
  • "Nobody told me the calibration on that gauge expired last week."

OpexMX sends two kinds of notifications. Personal alerts go straight to the person involved: the technician a ticket is assigned to, the approver of a workflow step, the shift taking over. Rule-based alerts cover plant-wide conditions, like low stock or overdue PM, and go to the recipients an admin picks, by email or push.


Channels

ChannelHow it reaches people
In-app inboxEvery push notification is stored. The bell shows the unread count; My Notifications lists them with All and Unread tabs and Mark all as read
Live in the browserAn open web app gets new notifications instantly, without a refresh
OpexMX Field appPhone notifications even when the app is closed (Android). A corrective ticket assigned to you rings a siren
EmailSent through the provider set in Settings → Email: Cloudflare Email Service, your own SMTP server, or disabled
WhatsAppOnly for work orders raised through WhatsApp, see below

Personal Alerts

These are sent automatically to the people involved. No rule is needed.

EventWho gets it
Ticket assigned or reassignedThe assignees (siren in the Field app for corrective tickets)
Ticket status or priority changed, new commentThe ticket's assignees
Someone @-mentions you in a commentYou
Ticket breaches its SLAThe assignee, or admins and managers when nobody is assigned. Checked hourly
PM occurrence assigned to you, PM completedThe assignee
Checklist overdueThe assignee
Workflow approval requested, step escalated to you, request approved or rejectedThe approver or the requester
Training assigned, training waiting for approval, recertification dueThe trainee or the approver
Purchase order submitted, approved, issued or closedThe person who raised the linked purchase request
New safety observationAdmins, managers and safety officers
Shift handover posted, handover acknowledgedThe incoming shift, then the author
Vibration alert from a sensorAdmins and managers (can be switched off per sensor)
Low stockAdmins and managers (in-app), plus the rule below

Rule-Based Alerts

A rule ties a code that OpexMX checks to a channel (Email or Push Notification) and a list of recipients. Disable a rule and that alert stops; switch its type and the same alert arrives on the other channel.

Rule codeWhen it firesCreated by default
parts-low-stockWeekday check for parts below minimum stockYes (email)
maintenance-overdueHourly check for PM occurrences that became overdueYes (email)
pdm-degradation-alertAn asset's predicted condition crosses its degradation thresholdYes (push)
pdm-anomaly-alertA multivariate anomaly on an assetYes (push)
purchase-request-createdA new purchase request, to procurementYes (email)
purchase-request-statusA request is approved, in progress, completed or cancelled, to the requesterYes (email)
calibration-dueWeekday check for calibrations due within 7 daysNo. Without a rule, admins and managers get a push; add a rule to choose the channel and recipients
qualification-expiryWeekday check for qualifications expiring within 30 days, sent to the holderNo. Add a rule with this code to turn it on

In Notifications:

  • Rules tab: create, edit, enable or disable rules, choose recipients, and press Test to send the alert to yourself.
  • Logs tab: every dispatch with rule, recipient, status and error, filterable by rule.

Webhook delivery failures also alert admins, in-app and by email, at most once per webhook every 6 hours. See API & Integrations.

WhatsApp

WhatsApp in OpexMX is a two-way channel for reporting and closing work, not a copy of every notification:

  1. A technician describes a problem in a WhatsApp group bound to OpexMX, or in a direct message to the bot, with text, a voice note or a photo. Voice notes are transcribed and photos are read.
  2. The AI assistant creates the work order and replies in Indonesian with the WO number.
  3. OpexMX assigns it to an on-shift technician, ranked by past outcomes, and sends that person a WhatsApp message with the WO number, title and asset.
  4. When the job is done, the technician writes "selesai" (or "done"). After a confirmation, the ticket is closed and the bot asks up to two follow-up questions: what broke and which parts were used.

Assignments made in the web or Field app are not sent over WhatsApp; they use the inbox, push and the siren.

Setting it up

WhatsApp has to be enabled for your organization first (server configuration by OpexCG, or by your IT team on-premise), and the AI assistant must be configured. It runs on one of two connections:

Cloud APILinked device
What it isMeta's official WhatsApp Business Cloud APIA dedicated WhatsApp number linked by scanning a QR code, like WhatsApp Web
SetupMeta Business account and a verified business numberAdmin → WhatsApp → Link a device, then scan with the phone that owns the number
Messages outside 24 hoursSent with an approved template, or held until the person next messages the botSent any time, paced to look like a person typing
RiskNoneUnofficial. WhatsApp can restrict or ban the number at any time. Use a spare number, never a personal or business-critical one

Under Admin → WhatsApp admins see the connection status, the WhatsApp Groups bound to OpexMX (reset an invite link, or delete a binding), and Phone Mappings: numbers the bot doesn't recognise wait there until an admin binds each one to an OpexMX user. Messages from an approved number act as that user. A user with the Admin, Manager or Planner role creates a group by sending the bot "buat grup <name>".

Who Can Do What

PermissionAllows
notification.readView notification rules and logs (with user.read to see the Notifications page)
notification.createCreate rules
notification.updateEdit rules, manage recipients, send a test
notification.deleteDelete rules
system-settings.writeAdmin → WhatsApp and Settings → Email

Everyone receives their own personal alerts and inbox without extra permissions. By default only Admins can create, edit and delete rules and manage WhatsApp and email; Supervisors, Engineers, Technicians and Warehouse staff can view the rules and logs. Adjust it in User Management.

Getting Started

  1. Check email: in Settings → Email, pick the provider and send a test message, so emailed alerts actually leave the building
  2. Review the default rules under Notifications → Rules and set recipients: procurement for purchase requests, stores for low stock, planners for overdue PM
  3. Add calibration-due and qualification-expiry rules if you track calibrations and certifications
  4. Install the Field app on technicians' phones and test the siren with a corrective ticket
  5. Watch the Logs tab for a week and fix any recipient without an email address

Tips

  • Use push for alerts someone must act on today and email for daily digests like low stock
  • Keep recipient lists short: a rule that emails the whole plant gets filtered into a folder nobody reads
  • Ask technicians to set battery saver to "No restrictions" for the Field app; it is the most common reason a phone alert doesn't arrive
  • For WhatsApp, approve phone mappings promptly: until a number is bound to a user, the bot can't attribute that person's reports or closes

Related