rubyforgood / rubyforgood/awbw

Post-event survey: reminder/nudge emails for incomplete surveys

Open
#2,110 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
15
Forks
26
Avg merge
12h 42m
Merged PRs (30d)
242

Description

🤖 From Claude: Filed while spiking the post-event survey feature (deferred from that PR).

Context

The post-event survey feature delivers survey forms inline on the registration ticket (Day 1 / Day 2 / Scholarship-recipient surveys), tracks completion, and sends an FYI email on submission. It does not nudge registrants who haven't completed a survey.

What's wanted

Reminder/nudge emails to registrants with an outstanding, past-drip, required survey — e.g. a scheduled reminder after the drip date, and/or a manual "send reminder" admin action from the registrants roster.

Notes

  • Reuse the readiness survey_pending signal to find who's outstanding.
  • Respect the survey's drip date (don't nudge before it's available) and the per-registrant applicability (day surveys for attendees, scholarship survey for recipients).
  • Follow existing mailer + preview conventions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the readiness survey_pending signal and the existing mailer and preview conventions. Trace how drip dates and per-registrant applicability are represented, then inspect the registrants roster entry point for a possible manual action. Done means eligible registrants with past-due incomplete surveys can receive an appropriate reminder without nudging ineligible or not-yet-available surveys.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.