Steinvar NotifyCommunicationsCustomer wording under the same control as code.
Every message the platform sends, from a sign-in code to a formal demand, comes from a template a second person approved. Steinvar Notify routes each event to its channels and keeps a log of what was sent, to whom and whether it arrived.
The HQ back office; the workplace and people’s names are blurred.
- 4
- channels: e-mail, SMS, Slack and in-app
- Approved
- templates, versioned under maker-checker
- Logged
- delivery of every message
Templates
Versioned and approved
A template change is a draft until a second person approves it.
Per event
Rules connect platform events (a payment, a statement, a missed instalment) to templates and channels.
Delivery
Channels
E-mail over SMTP, SMS through any HTTP gateway, Slack and in-app messages.
Delivery log
Every message with its recipient, channel, template version and outcome.
Operations alerts
Platform alerts reach the operations team through the same engine.
Used by the platform
Security
Sign-in and payment codes and passkey mail.
Products
Statements, deposit and loan notices, standing-order notices and collections letters.
How a message is sent
Event
Something happens: a statement is filed, a payment is missed.
Rule
The event’s rule picks the template and channels.
Render
The approved template version is filled in.
Deliver
The message is sent and its outcome logged.
Controls built in.
Maker-checker wording
No customer-facing text changes without a second person.
No internal reasons
A standing order the bank ends tells the customer it ended, without the bank’s reason.
Standards and formats
- SMTP
- HTTP SMS gateways
- Slack
Not in this module today
- Push notifications to mobile apps (APNs, FCM) are not built.
Questions about Steinvar Notify
Can we use our own SMS provider?
Yes: SMS goes out through any provider with an HTTP API, set up as a provider in the back office.