A queued reminder is not a current instruction
Synthetic expiry reminders are eligible only for the current issued quote awaiting response. N-320 was queued for Q-320 r1; the customer accepted it before release. N-321 refers to an offer superseded by r2. N-322 refers to the still-current offer awaiting response. Rechecking business eligibility suppresses the first two. It does not delete historical queue evidence or send a replacement reminder for r2 automatically.
| Reminder | Referenced offer | State at release | Decision |
|---|---|---|---|
| N-320 | Q-320 r1 | Accepted | Suppress; acceptance reason recorded |
| N-321 | Q-321 r1 | Superseded by r2 | Suppress stale reminder |
| N-322 | Q-322 r1 | Current issued; awaiting response | Eligible subject to content checks |
Recheck eligibility at the sending decision
- Read queued quote reference
- Read current quote business state
- Suppress irrelevant reminders
- Release only still-eligible content
A state read that fails leaves eligibility unresolved; it is not permission to send a possibly misleading reminder.
How many of the three reminders remain eligible in the shown fixture?
Show the worked answer
One: N-322. N-320 and N-321 are suppressed for different recorded business reasons.
These are local sales eligibility rules, not messaging consent rules, transport retry logic or a provider scheduler feature.