EP-MEL-15 — Multi-Channel Notification (Email, SMS, WhatsApp, Push)
Companion: Backlog README ·
EPICS.md· canonical:07-epics-and-user-stories.md§17
Summary
| Wave | R1 (+ additional channels in R3) |
| Priority | P0 |
| Primary owner | notification-service |
| Participating services | ai-orchestrator-service, file-storage-service, all BFFs |
| Journeys realised | J-04 (Confirmation), J-08 (Reconciliation alerts), J-15 (Front-desk shift) |
| Workflows | WF-04 |
| Frontend surfaces | All consumer + tenant + control surfaces |
| Story count | 6 |
Outcome
A single notification surface supports email, SMS, WhatsApp, and push, with i18n + RTL/LTR templates, scheduled delivery, AI-drafted suggestions (HITL), retry-with-audit, channel abstraction (so adapters can be swapped per region), and recipient preference management.
Cross-cutting AC for this epic
- Templates carry locale variants and rendering tests for RTL/LTR.
- Delivery audit log immutable; retries idempotent via
notification_id. - AI-drafted templates require human approval before production use.
- Recipient preference (channel, locale, quiet hours) is a first-class concept; persisted per recipient.
Stories
| ID | Title |
|---|---|
| US-MEL-0116 | Templates with i18n + RTL/LTR variants |
| US-MEL-0117 | Scheduled notifications (pre-arrival, post-stay) |
| US-MEL-0118 | AI-drafted message suggestions |
| US-MEL-0119 | Delivery audit & retry |
| US-MEL-0120 | Channel abstraction (email/SMS/WhatsApp/push) |
| US-MEL-0121 | Recipient preference management |
Full AC in
../07-epics-and-user-stories.md§17.
Cross-references
- AI architecture:
../08-ai-architecture.md - Definition of Done:
../standards/DEFINITION_OF_DONE.md