Improve Post-Event Follow-Up Email Template Clarity and CTA #4742
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Description
Updates the Post-Event Feedback Follow Up Email template preview UI to improve clarity, personalization scaffolding, and engagement. The previous layout had competing links, unclear CTA hierarchy, and limited context for why users should complete the survey. This PR restructures the content to make the survey action obvious, reduce cognitive load, and ensure required footer information is preserved.
Fixes # (high) Email follow-up CTA hierarchy unclear and secondary links compete for attention (1.1.1)
Fixes # (medium) Missing visible preview text in template preview and no clear time-to-complete expectation (1.1.2)
Fixes # (medium) Unsubscribe referenced but not clearly actionable in template preview (1.1.3)
Related PRS (if any):
Related PR: #3841
This PR is frontend-only (template preview/UI). No backend changes included.
Main changes explained:
How to test:
Screenshots or videos of changes:
PR.4742.mov
Note:
This PR improves the frontend template preview/UI only. If the actual outbound email is generated/sent via backend templates, those sender-side subject/preheader and dynamic event name/date insertions must be handled in the backend email service as a separate change.