This role only applies before their placement into a class.
We don’t want to overwhelm either party (volunteer by having too many people to try to reach out to, nor student by getting too much contact from us)
[QR code possibly for this that takes to brief vision video]
FYI: there is an automated response via email
➡️Receive or find the current list of those who have registered
- When you start this role, ask to add you to the mailing list for report of those who have registered but never come
- Each Monday, if you don’t receive that list via email, you’ll need to ask your school leadership for it.
➡️Reach out
- Differences based on time of year:
- During normal school year: Before reaching out, wait until after they have had one opportunity to come to class, and have not come.
- During summer: only reach out if you’re bored and available then. 🙂
- During Fall launch season: wait until October to start doing this, if for no other reason than the Ops team has a lot to do already.
- Via preferred contact method.
- Content
- Thank them for registering.
- We missed you in class.
- Use a simple question (assume language barrier) and ask them if they are ready to come to class. This would work: “Did you receive the welcome email?” or “When would you like to come to class?”
- May need to use Google translate and include it along with the English.
➡️When a person opts out or is unresponsive, have database updated
- We’d have a threshold such as trying them twice via their preferred method of contact.
- Send a last message via preferred method of contact that lets them know we are removing them from active list because we do not want to pester them. If they are still interested, they should reach out to us.
- Contact and tell them this persons registration status should be changed to “not responsive” or “opted out” (whichever is appropriate)