codefordenver / codefordenver/Circular

1-week after follow-up email

Open
#372 0 comments 0 reactions 0 assignees View on GitHub
mini-motivator email series
Dominant language
JavaScript
Stars
15
Forks
19
PR merge metrics
No merged PRs in 30d

Description

As a campaign creator, I would like a reminder email to gauge my progress and recommendations for next steps.

Acceptance Criteria:
Given that user has created a campaign
- when a week has passed
- then an email like below is sent

Sample Email Text:

Talk to 3 neighbors? 6 neighbors? 9 neighbors?
How many signatures did your collection sheet collect? Did you meet neighbors who signed to say thank you?

Once you feel you have enough signatures, it's time to turn it in! This process can't last forever... unless they put up a fight or are locked in by a contract.

Go to your property manager and let them know about you and your neighbor's quest for obtaining recycling services. If possible, go with a neighbor or two.
Turn in your signatures and ask about next steps. When can you expect to hear back from them? Are they open to obtaining service? What has stopped them so far from obtaining service? Is there someone else in the organization you should email the petition to?

Use your campaign manager page to write about your journey. Write down what your property manager says. Feeling more investigative? Collect optional data, it's time to learn what size your bins are and think about it from a hauler's point of view. Can they easily access the dumpsters? Is there room in the enclosure? Submit pictures in your tracker.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by locating how campaigns are created and how existing emails or scheduled jobs are sent, then trace the one-week timing path. Done means an eligible campaign creator receives the specified follow-up email after a week, with coverage for the acceptance criteria.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.