Skip to main content

Notification Delivery

Business Purpose​

Document how a resolved business intent becomes a channel-specific message and delivery result.

Actors​

Event producers, recipient-data owners, recipients, template owners, channel providers and support operators.

Business Flow​

Recipient references are normalized and upserted. Each distinct channel is handled separately. The service resolves the channel address, finds an active template, renders it, saves the pending message and uses the registered sender with retry.

Responsibilities​

Source modules provide usable recipient references and contact data. Administrators govern preferences and templates. Provider owners keep channel connectivity valid. Support distinguishes suppression, missing prerequisites and provider failure.

Business Rules​

Event-specific preference wins over wildcard preference; absence means enabled. In-app uses the external recipient reference, email uses email, and SMS/WhatsApp use phone. A message is persisted before its first attempt.

Integrations​

Delivery integrates the resolver, recipient directory, preference evaluator, template engine, message and attempt stores, audit trail, telemetry and channel registry.

Limitations​

No automatic alternative-channel fallback is evident. Missing address or template skips only that channel. Provider receipts and recipient acknowledgement are not modeled as external delivery confirmation.

Requires Confirmation​

Confirm mandatory-event preference exceptions, fallback rules, recipient validation, provider acceptance semantics and partial-delivery support procedures.

Source References​

  • microservices/src/notification-service/Application/NotificationDispatcher.cs
  • microservices/src/notification-service/Application/PreferenceEvaluator.cs
  • microservices/src/notification-service/Application/TemplateEngine.cs
  • microservices/src/notification-service/Channels/ChannelSenderRegistry.cs

See Also​

Keywords​

Delivery, recipient, address, preference, template, sender.

Revision Information​

Draft; reviewed 2026-07-21; next quarterly review 2026-10-21.