email notifications
email notifications help users finish onboarding, return to desktop, review access requests, understand trial state, and receive useful voice summaries.
quick answer
emails should explain a real product event and give the user a simple next step.
use this for
- understanding product emails
- debugging why a user received an email
- keeping email copy aligned with product behavior
steps
- identify which product event triggered the email.
- check whether it is onboarding, reminder, access, billing, digest, or support related.
- use the linked wiki page for the exact behavior.
- unsubscribe from non-essential email if the user does not want it.
details to know
- welcome and onboarding emails help the user reach the product.
- mobile reminder emails help a phone visitor return on desktop.
- access emails belong to public document permission flows.
- digest emails summarize writing and voice progress when available.
limits and edge cases
- transactional emails may still be needed for account, security, billing, or access events.
- emails should not include private keys or sensitive draft content.
- email pages should stay aligned with the scheduler and templates.
ready to use the product instead of reading about it?
open app