notification-service

To send notifications across email, SMS, and in-app channels, this service enforces user preference resolution, channel-specific opt-in rules, and delivery contracts. It queues jobs for scheduled dispatch and automatically applies template rendering before sending communications.

Yes, quiet hours and unsubscribe rules are enforced during notification dispatch. The service manages user opt-out settings and ensures compliance by logging all dispatches, alerting administrators only when mandatory notifications encounter critical delivery failures.

Notification retry logic works by applying defined retry policies within the dispatch queue. When a delivery fails, the service tracks the notification state and automatically re-attempts dispatch based on configured retry rules before alerting administrators of critical failures.

Yes, a notification type registry is required to manage template rendering and enforce delivery contracts. The service uses this registry to validate notification types, apply template variables, and ensure mandatory compliance auditing before dispatching across any channel.

The best way to dispatch a submission outcome notification is to specify the notification type, recipient ID, tenant, and template variables. The service resolves user preferences, renders the template with the provided variables, and queues the job for delivery.

Mandatory notifications are still delivered because the service enforces compliance rules that override standard user opt-outs. It validates notification types against the registry, logs all dispatches for auditing, and ensures critical messages reach users regardless of preference settings.