Transactional Email Scope¶
Prepared: 2026-06-25
This document defines the email events required for the paid pilot. It is the scope contract for Epic 6 implementation. It excludes marketing, newsletters, CRM nurture, and legal-notice automation.
Product Boundary¶
Transactional email is allowed when it helps a user complete an app workflow or recover account access. It must not be used for promotional campaigns.
Email must not claim that MamNajem has delivered a statutory notice. Formal rent increase, termination, arrears warning, enforcement, or vacate-demand flows stay outside the paid pilot unless counsel approves a separate workflow.
Preference Rule¶
Use account notification preference notifyEmail for app workflow emails.
Exceptions:
- Cognito sign-up verification, password reset, and account recovery are account security emails and continue through Cognito.
- Stripe invoice, receipt, payment-failed, and tax emails remain Stripe-owned unless a later billing gap requires app-owned email.
- Legally required account or policy emails, if introduced later, must have a separate compliance rule.
Launch Email Events¶
| Event key | Required for launch | Trigger | Recipient source | Preference | Template language |
|---|---|---|---|---|---|
TENANT_INVITATION |
Yes | Owner creates tenant invitation | invitation email address and lease tenant record | always send; invitee may not have an account yet | Polish primary, English fallback |
RENT_REMINDER_DUE_BEFORE |
Yes after EP6 sender works | EP5 rule rent_due_before_N |
accepted tenant users on payment request lease | respect notifyEmail |
recipient language, Polish fallback for Poland pilot |
RENT_REMINDER_DUE_TODAY |
Yes after EP6 sender works | EP5 rule rent_due_today |
accepted tenant users on payment request lease | respect notifyEmail |
recipient language, Polish fallback |
RENT_REMINDER_OVERDUE_1 |
Yes after EP6 sender works | EP5 rule rent_overdue_1 |
tenant users and lease owner | respect notifyEmail |
recipient language, Polish fallback |
RENT_REMINDER_OVERDUE_7 |
Yes after EP6 sender works | EP5 rule rent_overdue_7 |
tenant users and lease owner | respect notifyEmail |
recipient language, Polish fallback |
PAYMENT_PROOF_RECEIVED |
Yes | Tenant or lease participant adds receipt/proof | lease owner; exclude actor if owner uploaded proof | respect notifyEmail |
recipient language, Polish fallback |
HANDOVER_CONFIRMATION_REQUEST |
Yes | Handover protocol is ready for the other side to confirm | owner or accepted tenant users who still need to confirm | respect notifyEmail |
recipient language, Polish fallback |
FINAL_SETTLEMENT_REQUEST |
Yes | Owner initiates final settlement or sends revised settlement | accepted tenant users on lease | respect notifyEmail |
recipient language, Polish fallback |
SUBSCRIPTION_BILLING_STRIPE |
No app email in launch | Stripe invoice/payment/subscription lifecycle | Stripe customer email | Stripe-managed | Stripe-managed |
ACCOUNT_SECURITY_COGNITO |
No app email in launch | sign-up verification, password reset, account recovery | Cognito user email | Cognito-managed | Cognito-managed |
LEGAL_POLICY_NOTICE |
Not launch scope | future counsel-approved requirement | account email | separate compliance rule | counsel-approved |
Event Details¶
Tenant Invitation¶
Purpose: get a tenant into the lease workspace.
Required fields:
- invitation code or link;
- property name;
- owner/display sender name when available;
- tenant email;
- expiry date when available;
- support contact or help route.
No marketing pitch. No claim that accepting an invite signs a lease or changes legal status.
Rent Reminders¶
Purpose: remind tenant/owner about an open off-ledger payment request.
Use Rent reminder rules for timing, payload, and copy. Email uses the same rule keys as in-app/push and is enabled only after the email sender is verified in integration.
No statutory warning wording. No wezwanie do zapłaty, termination, penalty,
interest, eviction, or debt-collection language.
Payment Proof Received¶
Purpose: tell the owner that a payment proof/receipt was attached.
Required fields:
- property name;
- payment title or period;
- amount and currency;
- actor display label when safe;
- link/deep link to payment request.
Copy must say proof was added, not that rent is legally settled. Owner mark-paid remains the confirmation step.
Handover Confirmation Request¶
Purpose: ask the other side to review and confirm a handover protocol.
Required fields:
- property name;
- lease or handover date when available;
- requested action: review and confirm in app;
- link/deep link to protocol.
Copy must describe an evidence review workflow, not a qualified signature or formal written-form document.
Final Settlement Request¶
Purpose: ask tenants to review a final settlement statement.
Required fields:
- property name;
- settlement status;
- amount/refund/payment direction when available;
- requested action: review in app;
- link/deep link to settlement.
Copy must not say the tenant accepted a debt, waived claims, or signed a legal settlement. The app records review/confirmation unless a later formal settlement agreement workflow is approved.
Out Of Scope¶
Do not implement launch emails for:
- newsletters, win-back, product education, feature announcements, referral campaigns, or agency waiting-list nurture;
- generic owner dashboard summaries;
- repeated overdue escalation after EP5
rent_overdue_7; - legal notices, rent increase notices, termination notices, arrears warnings, enforcement demands, or certified-delivery workflows;
- Stripe subscription receipts, invoices, or payment failure notices already handled by Stripe;
- Apple/Google billing emails handled by app stores.
Implementation Notes¶
- Sender identity and provider setup are owned by EP6-T2.
EMAILchannel delivery implementation is owned by EP6-T3.- Email templates and Polish copy are owned by EP6-T4.
- Workflow wiring and recipient tests are owned by EP6-T5.
- Backend logs must record event key, notification id/group id, provider result, and non-PII recipient identifier hash or user id. Do not log full email body.