Announce availability, delivery preview, glossary update, or support readiness.
Email Reactivation Runbook
Email can bring early users back when a study product is ready, but only after explicit consent, unsubscribe, deletion, support, and provider review are in place. This is a runbook, not a live mailing system.
Activation gate
- Use a WeAcuRe domain support email before any reactivation message is sent.
- Record explicit early access consent, source, date, market, language, and product interest.
- Confirm unsubscribe, deletion, export, provider boundary, Privacy, Terms, and Contact paths.
- Keep provider endpoints, API keys, list IDs, contact exports, and user email lists outside GitHub.
Allowed message types
Explain access, deletion, export, unsubscribe, support, or launch pause changes.
Tell users when checkout, forms, delivery, or policy review is paused.
Blocked segmentation
- Do not segment by birth date, birth time, birth location, chart output, or palace labels.
- Do not segment by payment status, support message, campaign identifier, or sensitive category.
- Do not send personal outcome, prediction, health, wealth, relationship, legal, or financial claims.
Cadence and footer
- No more than one readiness update per week during early testing.
- Pause if unsubscribe, refund, delivery, support, privacy, or policy questions increase.
- Every message needs an unsubscribe path, support email route, privacy link, deletion path, and why-you-received-this note.
Related pages
Continue with Email Consent Boundary, Early Access, Data Request Boundary, Support Readiness, Support Intake Boundary, Provider Readiness, Privacy, and Contact.