These are detailed guidelines on how to work with our team from email planning to sending.
Last Revised: 12.20.17
Kickoff meeting — where all steps below including reviews for editorial and design, proofing, and review of performance metrics are scheduled — with the following present:
Partner-Client(s)
Editor
Designer
Developer if needed
Copy creation, review by partner-client, revision by editor (repeat as needed, noting that a maximum number of reviews may be established at kickoff); copy in this case includes subject header text, pre-header text, body text, all link URLs, button text, and “from” address
Copy final for layout according to partner-client and editor (and others if needed), handed off to designer
Partner-client collects CADS IDs for target audience and uploads to Salesforce Marketing Cloud (SFMC).
Design created in SFMC tool by designer, who sends test to editor and partner-client. This design consists of either:
A single template email that will be copied and altered by the partner-client once final (e.g. Charter Hill holiday emails, DRM end-of-year emails, ERMC Homecoming and Brilliance of Berkeley emails) and multiple banners or other assets for partner-client to change out, or
Multiple, distinctly designed emails that make up a single campaign, e.g., Big Give.
Design review by editor and partner-client; revision by designer (repeat as needed, noting that a maximum number of reviews may be established at kickoff)
If they have access, editor makes copy edits inside SFMC; otherwise designer makes copy edits with design changes.
Design and copy of email(s) final according to partner-client, designer, and editor
Designer tests email’s look and functionality in various email clients and devices using Email on Acid tool.
Final, tested email along with additional assets, if any, are (symbolically) handed over to partner-client, with location of where assets can be found on the SFMC tool.
Partner-client applies subject headers and pre-header text, creates multiple emails, and tests with client review group as needed.
Partner-client schedules email delivery in SFMC.
After delivery, partner-client pulls metrics from SFMC and shares with editor; editor makes note of performance (in “additional project notes” in current database, “Project Notes” in new database to come).