Review Scenario Prompt History and Delivery Effectiveness
Coordinators need visibility into the scenario notification pipeline to understand whether automated prompts are driving behavior change. The prompt history repository stores a record of every evaluation that resulted in a notification dispatch, including the rule ID, target mentor, timestamp, delivery status, and subsequent activity (if any). The coordinator views this as a filterable list grouped by scenario rule or by peer mentor, allowing them to spot patterns — such as a mentor who has received three inactivity reminders without logging any activity — and escalate to a personal follow-up call.
User Story
Acceptance Criteria
- Given I am on the scenario configuration screen, when I tap on a specific scenario rule, then I see a detail view with the full prompt history for that rule including mentor names, delivery timestamps, and read status
- Given the prompt history list is displayed, when I filter by a specific peer mentor, then I see all scenarios that have been triggered for that mentor in chronological order
- Given a mentor has received a scenario prompt and subsequently logged an activity, when I view the prompt history, then the record shows a 'responded' indicator linked to the follow-up action
- Given I want to export the prompt history for reporting, when I select an export option, then a structured summary is generated covering the selected time period
- Given a prompt failed to deliver (e.g., no FCM token), when I view the history, then the record shows a failed delivery status with the reason
Business Value
Transforms the scenario prompt system from a fire-and-forget mechanism into a closed feedback loop. Coordinators gain actionable intelligence on which mentors are disengaged and which scenarios are working, enabling data-driven iteration on follow-up strategies. This is critical for organizations like HLF where certification compliance and ongoing engagement are directly tied to funding eligibility and service quality standards.