Last updated: 10/24/2024
Last reviewed: 10/24/2024
...
Jira Ticket Status Descriptions
See this section of Confluence for explanations about Statuses and Task Assignment Ownership:
[New]
[In Progress]
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
NOTE: If we don’t hear back from the requestor for final draft approval after 1 week, we will mark the request as canceled, tag you in a comment, and ask that you resubmit a new ticket. |
...
Additional things to note:
ALL TEAMS (DG/CM/PM and Email/Media/WBN Ops) are responsible for checking in on Jira tasks/projects daily, regardless of whether you receive an email notification or not. If you are not receiving notifications, please reach out to your Manager.
Deliverables: DGM/CM/PM is responsible for providing all deliverables needed to execute an email project, including but not limited to email copy (e.g., subject lines, headers, body copy, demo footer copy, etc.), all images, all asset links (e.g., blog links, on-demand webinar links, demo links, Instapage links, etc.), so that we have all materials needed to build and launch the email on schedule.
If there are extenuating circumstances, please contact your Email Ops counterpart as soon as you are aware of something impacting the launch of your email so we can discuss options.
If DG/CM/PM is unable to supply all deliverables to Email Ops under the above agreed-upon timelines (assuming no extenuating circumstances that we previously discussed), then the send date can be pushed out at the Email Ops manager’s discretion.
...
| Warning |
|---|
Before any nurture/trigger can be submitted in Jira, Demand Gen/CM/PM must schedule an initial meeting with Email Operations to discuss the scope and plan for the project, as well as a feasible launch date based on the deliverables required. Please do not submit the request to Jira until you’ve had this planning meeting and identified all requirements/timelines! |
Triggers
*After the planning meeting has occurred and project scope/requirements have been confirmed, please allow for the following timeline at minimum*
8 business days: For 3 or less emails
10 business days: For 4 to 6 emails
NOTE: These timelines assume a linear trigger, more complicated triggers and triggers over 6 emails need to be discussed in advance with Email Operations Team.
Nurtures
*After the planning meeting has occurred and project scope/requirements have been confirmed, please allow for the following timeline at minimum*
20 business days (minimum)
This number is only applicable to one, linear nurture with approx. 8-10 emails. If additional nurtures are requested, or additional complexity is needed for the cadence (e.g., more action steps/rules/etc. are required for the build, etc.), additional business days might be required. This final launch date should be discussed during the initial planning meeting, before submitting to Jira.
NOTE: If requestor doesn't have all copy/links/images ready in time for the nurture to launch, then the email doesn't get added to the stream until it's ready, OR the nurture is on hold until all copy/links/images are provided. Emails that are in the nurture should be final emails; we will no longer use placeholders.
Deliverables we need to receive/info we need to know:
What’s the topic/theme? (e.g., Trauma-informed care; nurture for MCLs)
Who’s the audience? (e.g., All ACU prospects; PAC MCL prospects, etc.)
Does a list upload need to be considered, or are we referencing an existing list?
How many emails total?
Frequency of sends (1/week, biweekly, etc.)
Goal of Nurture (e.g., to score up into next content series; demo request)
Layout of Nurture (great example: https://miro.com/app/board/uXjVMlb1hnQ=/ ) - a visual plan in some form will be very helpful for us to figure out how we should best set up the nurture program
Intended launch date
...