Multichannel Notification System (Pulse)
SMS, email, push and an in-app inbox from one point. Each service submits a send request, and Pulse selects the right provider and template according to the company.
- Domain
- Customer messaging and notifications
- Target customers
- All platform services that need customer notification, marketing team, product management
- Main capabilities
- Unified SMS/email/push, multi-company, template SMS, one-time code recovery, in-app notification inbox, traceable log
Pulse is the platform's shared infrastructure for sending messages to customers: SMS, email, push notifications and an in-app notification inbox, all from one point. Instead of each service (wallet, financing, marketing, support) building its own separate connection to an SMS panel or Firebase, all of them request delivery from Pulse, and Pulse selects the right provider and template according to the company that owns the message.
The system is designed to be fully multi-company: each subsidiary can have its own SMS account, email profile and Firebase settings, with a platform-level default configuration for companies that have not yet set up a dedicated account. This means that several independent brands can share the same technical infrastructure without their credentials or sender numbers getting mixed up.
Another important part is the in-app notification inbox, which works independently of push notifications and keeps notifications persistently, for one user or for all users of a company (company-wide announcement), together with read status and the ability to dismiss a notification.
Key capabilities
Unified multichannel delivery
SMS (Kavenegar as the primary provider), email via SMTP and push notifications via Firebase, all with a single message structure.
Full separation of each company's settings
Each company has its own SMS account, sender number, email profile and Firebase settings; where no dedicated account exists, the platform default is used.
Approved template SMS
For SMS messages that must use a template registered in the provider's panel (such as a verification code), Pulse calls the template-based send operation instead of sending free text.
Semantic send endpoints for common business scenarios
One-time login code, purchase code, wallet deposit and withdrawal notice, support ticket notice, and financing status notice; other services send only business parameters and do not manage the SMS text and template themselves.
One-time code recovery channel
When an SMS arrives late for any reason, the same code is kept in a short-lived encrypted store so that the user can retrieve and enter it by another route (the app); final verification still takes place in the issuing service.
In-app notification inbox
Personal or company-wide notifications, separate for the mobile app and the admin panel, with unread counts, mark as read, and removal from the list.
User notification preferences
A user can turn the receipt of each notification category (wallet, tickets, financing, security, marketing) on or off separately.
Real-time delivery
A new notification reaches the user's open browser tab or app immediately, with no need to refresh and without delay.
Complete, traceable log of every message
Every send is recorded with a masked phone number or address (to protect privacy), the delivery status and a trace ID shared with the sending service; it can be cited when handling a customer complaint or dispute.
Central message templates editable without code
The title and body text of notifications and campaigns can be defined as templates with parameters, both at company level and as the platform default.
Event-driven integration with other services
Services such as micro-credit and marketing can publish a send-message event, and Pulse delivers the message without a direct connection.
Business value
Every new financial service on the platform needs to notify customers. Without shared infrastructure, each team has to reimplement connections to the SMS panel, SMTP and Firebase and maintain the credentials of each provider separately. Pulse does this once, and the other services simply submit a request from one point, which greatly shortens the time to launch notification capability in a new product. Separating each company's settings lets the group run several independent brands on one infrastructure without exposing one brand's credentials to another. The one-time code recovery channel directly prevents a drop in login and purchase success rates at moments when the SMS panel is slow or unstable, which in a financial business means lost transactions. The complete, masked log of every message provides a tool for handling customer complaints (“I did not receive the SMS”) and for responding to supervisory bodies.
What sets it apart
- Genuine separation of each company's credentials and sender number, instead of one shared SMS account for the whole platform.
- Semantic send endpoints that separate the template and SMS text logic from the consuming services, so changing a message's text needs no code change in other services.
- A dual delivery channel for the one-time code (SMS together with encrypted recovery), which directly affects login and purchase success rates.
- A complete, masked log of every exchange with the provider, for fast dispute handling and end-to-end tracing with a trace ID shared between services.
- Real-time delivery of in-app notifications separate from push, with precise channel control (mobile app versus admin panel).
Solutions that use this module
See this module on demo data
In a demo session we walk through your organization's scenarios on Dara's demo environment and answer your technical and finance teams' questions.