Email Template Management

Use this module to create and maintain transactional/system email templates.

Interface Reference #

Purpose #

• Standardize outgoing communication.
• Keep messaging consistent across flows.
• Control template quality and localization.

Template Lifecycle #

1. Draft template.
2. Add variables/placeholders.
3. Preview and test send.
4. Approve and publish.
5. Track and revise when needed.

Field Notes #

• Subject: keep short and action-oriented.
• Body: use approved tone and placeholders only.
• Language: maintain EN/TR parity where required.
• Status: draft vs active must be explicit.

Validation Checklist #

• Placeholders render correctly.
• Links route to expected environment.
• No hardcoded personal or environment-specific data.

Troubleshooting #

• Broken variables: verify placeholder syntax.
• Wrong language output: check template-language mapping.
• No email delivered: confirm provider status and event trigger.

Best Practice #

Keep a small set of reusable templates and avoid one-off duplicates.