TegBooks

Email Template Requirements Playbook

Issue link: https://activate.tegrita.com/i/1037906

Contents of this Issue

Navigation

Page 7 of 13

8 Email Template - Tegrita Designs Email Mock-up Provide a brand style guide. Provide a requirements document (if it exists). Provide examples of past emails and examples of emails client favors like for discussion. A end Requirements mee ng with Tegrita Design Resource to gather all details for email design for desktop and mobile: layout, fonts, colors, styling, CTAs, hyperlinks, images, etc. Provide any content or assets required as ac on items a er Design Mee ng. Provide content for email footer - physical address, privacy policy, unsubscribe verbiage, this will be included in the design. Provide informa on around what areas of the email should be editable and/or deletable for the protected template version. Image list or indicate Tegrita to use placeholders. CLIENT REQUIREMENTS: PROCESS: 1. Client provides brand style guide, requirements and email examples. 2. Design Requirements mee ng with Tegrita Design Resource. 3. Tegrita designs email mock-up. 4. Client reviews email mock-up/provides approval or revisions. 5. Tegrita builds email templates - Standard (user has access to the HTML) and Protected (user edits via a WYSIWYG editor). 6. Tegrita QA checks/runs Litmus tests on templates. 7. Tegrita schedules walkthrough of templates and Email Editors, or sends emails to client to review. 8. Revision cycle if needed (may require addi onal budget).

Articles in this issue

view archives of TegBooks - Email Template Requirements Playbook