TegBooks

Email Template Requirements Playbook

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

Contents of this Issue

Navigation

Page 4 of 13

5 CLIENT REQUIREMENTS: Email Template - Client provides HTML PROCESS: 1. Client provides HTML and suppor ng files. 2. Eloqua development team reviews HTML and notes anything that may need upda ng or op mizing and alerts client. 3. Tegrita builds email templates - Standard (user has access to the HTML) and Protected (user edits via a WYSIWYG editor). 4. Tegrita QA checks/runs Litmus tests on templates. 5. Tegrita schedules walkthrough of templates and Email Editors, and/or sends email(s) to client to review. 6. Revision cycle if needed (may require addi onal budget). Provide HTML file, suppor ng images and any hyperlinks. Provide a requirements document (if it exists). If the HTML file is not responsive/op mized for mobile, provide a mockup of the mobile view or specific direc ons around how the email should render on mobile devices. If no mobile view is available, Tegrita can advise on best prac ces for mobile and client must sign off on recommenda ons. If not included in the HTML email, provide content for email footer - physical address, privacy policy, unsubscribe verbiage. Provide informa on around what areas of the email should be editable and/or deletable for the protected template version.

Articles in this issue

view archives of TegBooks - Email Template Requirements Playbook