Notification Engine
Route supported operational events to configured recipients.
Neev can create notification records for supported events and route configured messages. External delivery depends on provider approval, credentials, templates, and availability.
Before Neev
Operational events need recipients
Each supported event needs a configured audience and a legitimate communication purpose.
Channels have separate requirements
WhatsApp, email, and other providers can require credentials, approval, and templates.
Delivery is not guaranteed
Provider acceptance, recipient details, and network conditions affect external delivery.
Messages need oversight
Templates, routing, consent, delivery status, and opt-out handling need operational owners.
What Neev does
Configuration required · WhatsApp
Requires Meta approval, provider credentials, appropriate templates, and recipient handling.
Configuration required · External delivery
Availability depends on the channel, supported event, and configured provider.
Available · Event-specific recipients
Supported events can use the explicit customer, business, or other recipient data defined for that workflow; recipient data must be reviewed.
Available · Notification records
Review supported message attempts and statuses recorded by Neev; provider status may be delayed or incomplete.
Configuration required · Templates
Business text and provider-approved template requirements must be configured per supported channel.
“Use configured notifications as an aid to operations, with human oversight and no delivery guarantee.”