Scenario-based Follow-up Prompts
Feature Detail
Description
Intelligent, context-aware push prompts that surface at relevant moments in the peer mentor workflow — for example, prompting the peer mentor to log a follow-up call three days after recording a first contact, or suggesting they check in with a contact who had flagged a difficult situation in the previous report. These prompts are scenario-driven rather than time-only, using activity metadata (contact type, reported wellbeing flags, duration) to determine relevance. Coordinators can configure which scenarios trigger prompts for their chapter. The feature is designed to reduce the emotional labour of remembering follow-up obligations and is especially relevant for HLF, where dissatisfaction with peer mentor follow-up was measured at 40%. Prompts are actionable — tapping one opens directly into the activity registration wizard with pre-filled context.
Analysis
Directly targets the HLF finding that 40% of peer mentors felt follow-up was insufficient. Scenario-based prompts lower the cognitive load on peer mentors and increase the likelihood of timely, meaningful follow-up without requiring coordinators to micromanage.
Define scenario rules as JSON config per org (e.g., {trigger: 'first_contact_logged', delay_days: 3, prompt: '...'}). Evaluate rules in a scheduled Edge Function. Start with 3–5 hardcoded scenarios and expose config UI in Phase 3. Deep link into activity wizard via go_router with pre-filled route arguments.
Components (208)
Shared Components
These components are reused across multiple features
User Interface (59)
Service Layer (52)
Data Layer (33)
Infrastructure (54)
User Stories (5)
As a As a Peer Mentor (Likeperson)
I want to view a history of all scenario-triggered prompts that have been sent, including which peer mentors received them, when they were delivered, and whether any action was taken in response
So that I can assess the effectiveness of my configured scenarios, identify peer mentors who are repeatedly triggered by the same conditions without responding, and refine my follow-up strategy accordingly
- 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
- +2 more
As a As a Peer Mentor (Likeperson)
I want to compose the notification title and body for each scenario rule using a content builder that supports dynamic placeholders (e.g., mentor name, days since last activity, certification expiry date) and preview how the message will appear on a device before activating the rule
So that I can ensure scenario notifications are personalized, clearly worded, and action-oriented before they reach peer mentors — preventing confusing or generic messages that would undermine trust in the notification system
- Given I am editing a scenario rule, when I open the notification content section, then I see a text editor with a placeholder insertion toolbar listing available dynamic fields (name, days inactive, certification expiry, etc.)
- Given I insert a placeholder into the message body, when I view the preview, then the placeholder is replaced with realistic sample data appropriate to the placeholder type
- Given I submit a message template that exceeds the 100-character push notification title limit, when I try to save, then a validation error is shown indicating the title must be shortened
- +2 more
As a As a Peer Mentor (Likeperson)
I want to configure when scenario evaluation edge functions run and when resulting notifications are delivered — for example, restricting delivery to weekday business hours and avoiding evaluation runs during peak app usage times
So that peer mentors receive prompts at times when they are likely to be available to respond, reducing notification fatigue and respecting the voluntary nature of peer mentoring work
- Given I am configuring a scenario rule, when I set an evaluation frequency (e.g., daily) and a delivery window (e.g., weekdays 09:00–17:00), then those constraints are saved and applied to the edge function schedule
- Given an evaluation runs and a condition is met outside the configured delivery window, when the delivery window opens, then the queued notification is sent at the start of the next valid window
- Given I configure a blackout period (e.g., holiday freeze), when the delivery window would normally open, then no notifications are sent during the blackout and they are discarded rather than queued
- +2 more
As a As a Peer Mentor (Likeperson)
I want to monitor which scenario prompts my peer mentors receive and configure deep-link routing so that each prompt takes the recipient directly to the most relevant in-app action
So that peer mentors experience a frictionless response flow — tapping a notification immediately opens the correct screen (e.g., activity registration, certification renewal, or contact detail) — maximizing the likelihood that the prompted action is completed
- Given I am configuring a scenario rule, when I select a deep-link destination from a predefined list of valid routes, then that route is stored with the rule and included in the notification payload
- Given a peer mentor taps a scenario notification, when the app opens, then the deep-link router navigates directly to the configured destination screen without passing through the home screen
- Given the peer mentor's session has expired when they tap the notification, when authentication completes, then the app resumes navigation to the deep-link destination
- +2 more
As a As a Peer Mentor (Likeperson)
I want to define scenario-based rules that automatically trigger follow-up prompts for peer mentors based on specific conditions such as inactivity periods, upcoming certification expiry, or absence of reported contact
So that peer mentors receive timely, contextually relevant reminders that reduce administrative overhead on me while ensuring no mentor goes unsupported or unmonitored for extended periods
- Given I am logged in as a coordinator, when I navigate to the scenario configuration screen, then I see a list of all existing scenario rules with their active/inactive status
- Given I create a new scenario rule, when I define a trigger condition (e.g., inactivity threshold in days), message content, and target role, then the rule is saved and the scheduler is updated to evaluate it on the next cycle
- Given a scenario rule is active, when the evaluation edge function runs and the condition is met for a peer mentor, then a push notification is dispatched to that mentor within the configured delivery window
- +2 more