Templates with a managed lifecycle
Organise channel templates, review revisions and validate content before publication. Keep message content independent of the delivery provider.
- Message templates
- Content review
Boiler Framework / Multichannel notifications
Boiler Informer
Deliver notifications through selected providers with shared templates, configuration and delivery records.
What you can do
- 01
Manage notification templates and versions.
- 02
Configure providers, credentials and routing pools.
- 03
Track dispatch attempts and provider outcomes.
A practical example
One notification, several delivery providers.
Built for · Application and customer operations teams
Your application needs to send a customer update without embedding provider-specific templates and connection settings throughout its business logic.
How the work moves
Prepare the channel template and validate its content.
Select an installed provider or provider pool with the required credentials and capabilities.
Track the dispatch attempt, provider acceptance and available delivery evidence separately.
What this gives your team
Shared notification operations with a clearer view of what was attempted and what was confirmed.
Illustrative workflow. Connections and deployment scope are agreed for your environment.
Inside the product
Boiler Informer
Providers and delivery pools
Manage provider endpoints, encrypted credential revisions, connection checks and provider pools. Inspect installed capabilities before selecting a route.
- Delivery providers
- Connection checks
Multiple channels, one delivery boundary
Use email, SMS, FCM push and installed chat or webhook adapters. Dispatch through standalone or Rabbit-based composition and distinguish provider acceptance from confirmed delivery.
- Email and SMS
- Push notifications
- Chat channels
Scope & availability
Provider and channel availability depends on the agreed configuration. Direct APNs is not implemented; provider acceptance does not by itself prove delivery.