Communication Scenarios
1. Overview
This document defines specific communication scenarios, message sequences, and timing rules for the async communication system. Each scenario describes the trigger, message flow, timing, and channel selection.
2. Scenario Categories
| Category | Description | Priority |
|---|---|---|
Registration |
Messages related to event/membership registration flow |
High |
Payment |
Payment reminders and confirmation messages |
High |
Membership |
Membership lifecycle communications |
Medium |
Event |
Pre-event, day-of, and post-event communications |
High |
Emergency |
Urgent broadcasts for cancellations and alerts |
Critical |
3. Registration Scenarios
3.1. REG-001: Registration Confirmation
| Scenario ID | REG-001 |
|---|---|
Trigger |
Registration created (any payment status) |
Channel Priority |
Email > WhatsApp > SMS |
Timing |
Immediate (within 5 minutes of registration) |
Message Content |
|
Conditions |
|
3.2. REG-002: Abandoned Registration Recovery
| Scenario ID | REG-002 |
|---|---|
Trigger |
Registration created but not paid within 24 hours |
Channel Priority |
Email > WhatsApp |
Message Sequence |
|
Cutoff Rules |
|
Content Variables |
|
4. Payment Scenarios
4.1. PAY-001: Payment Reminder Sequence
| Scenario ID | PAY-001 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Trigger |
Unpaid registration exists |
||||||||||||
Channel Priority |
Email > SMS > WhatsApp |
||||||||||||
Message Sequence |
|
||||||||||||
Business Rules |
|
||||||||||||
Escalation |
If unpaid after final reminder, flag for manual review |
4.2. PAY-002: Payment Confirmation
| Scenario ID | PAY-002 |
|---|---|
Trigger |
Payment successfully processed |
Channel Priority |
Email (required) + WhatsApp (if opted in) |
Timing |
Immediate (within 2 minutes) |
Message Content |
|
4.3. PAY-003: Payment Failed
| Scenario ID | PAY-003 |
|---|---|
Trigger |
Payment attempt failed |
Channel Priority |
Email > SMS |
Timing |
Immediate |
Message Content |
|
Follow-up |
Enter PAY-001 reminder sequence if not resolved within 4 hours |
5. Membership Scenarios
5.1. MEM-001: Welcome Sequence
| Scenario ID | MEM-001 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
Trigger |
New membership activated (payment confirmed) |
||||||||
Channel Priority |
Email (primary) + WhatsApp (optional) |
||||||||
Message Sequence |
|
5.2. MEM-002: Expiry Warning Sequence
| Scenario ID | MEM-002 | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Trigger |
Membership expiry approaching |
||||||||||||||||||
Channel Priority |
Email > WhatsApp > SMS |
||||||||||||||||||
Message Sequence |
|
||||||||||||||||||
Business Rules |
|
5.3. MEM-003: Expired Membership
| Scenario ID | MEM-003 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
Trigger |
Membership has expired |
||||||||
Channel Priority |
Email > WhatsApp |
||||||||
Message Sequence |
|
||||||||
Business Rules |
|
6. Event Scenarios
6.1. EVT-001: Pre-Event Sequence
| Scenario ID | EVT-001 | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Trigger |
Participant registered and paid for upcoming event |
|||||||||||||||
Channel Priority |
Email (detailed) + WhatsApp (reminders) |
|||||||||||||||
Message Sequence |
|
|||||||||||||||
Content Variables |
|
6.2. EVT-002: Seeding Notification
| Scenario ID | EVT-002 |
|---|---|
Trigger |
Seeding/heat allocation published |
Channel Priority |
Email + WhatsApp |
Timing |
Within 1 hour of seeding publication |
Message Content |
|
6.3. EVT-003: Results Notification
| Scenario ID | EVT-003 |
|---|---|
Trigger |
Event results published |
Channel Priority |
Email (full) + WhatsApp (summary) |
Timing |
Within 2 hours of results publication |
Message Content |
|
7. Emergency Scenarios
7.1. EMG-001: Event Cancellation
| Scenario ID | EMG-001 |
|---|---|
Trigger |
Event cancelled (admin action) |
Channel Priority |
All channels simultaneously (SMS + WhatsApp + Email) |
Timing |
Immediate - bypass all scheduling rules |
Message Content |
|
Target Audience |
All registered participants (paid and unpaid) |
Special Rules |
|
7.2. EMG-002: Venue Change
| Scenario ID | EMG-002 |
|---|---|
Trigger |
Event venue changed (admin action) |
Channel Priority |
SMS + WhatsApp (immediate) + Email (detailed) |
Timing |
Immediate |
Message Content |
|
8. Timing Rules Summary
8.1. Quiet Hours
| Rule | Details |
|---|---|
Night quiet hours |
No messages between 20:00 and 08:00 local time |
Weekend handling |
Payment reminders pause Sat-Sun, resume Monday 09:00 |
Holiday handling |
To be defined per region |
9. Channel Selection Logic
10. Open Questions
The following timing and rule details require stakeholder input:
-
Specific quiet hours for different regions/timezones
-
Holiday calendar for pausing non-urgent communications
-
Exact retry intervals for failed deliveries
-
Auto-cancellation timing for unpaid registrations
-
Grace period for expired memberships
11. Related Documentation
-
Functional Requirements - Core system requirements
-
Communication Integration - Platform integration
-
Design Thread:
design-journal/2026-01/async-processing-communication.adoc