The Atlassian Email Marketing team's goal is to deliver incredible customer experiences with equally positive business results. To bolster this mission, they created an Email Playbook to help all Atlassians deliver the best marketing experience through increased email engagement that drives customer lifetime value.
In the following post, you'll learn the ins and outs of how the Atlassian Email Marketing team uses Confluence, Jira Service Desk, and Jira to send all the right messages.
The Email Marketing team's first step in helping Atlassian send emails is to send them to The Email Playbook Confluence page which serves as a hub for everything an email requester would need to know about sending an email, start to finish.
This page links out to 10 pages, detailed below:
As mentioned above, the Email Playbook (Confluence) links out to JSD for those who are ready to submit a ticket request to send an email. When a user clicks on the first icon, Request an Email, they're linked to a JSD page that looks like this:
The user can either search for their help topic or create a request for an email or an email task. (An email task could be analyzing an email test, querying a list to determine its size, etc.)
If they select Email Request, they will be prompted to fill out fields (summary, goals, email type, requested send, content urls, etc.) about their email:
If they request an email task, (for example help to analyze an email test or to query a list to determine its size), they will be taken to a page that prompts them for information on what they need, when they need it by, description, objective, and success metrics.
Once the JSD ticket is filed, it's reviewed by the email team and if accepted, turned into a Jira ticket.
Once the email request goes through Jira Service Desk to become a Jira ticket, the ticket filer + the Email team start collaborating, discussing the SLAs for the email and finalizing the design and content. The ticket will include the following fields:
Example of the a Jira ticket with all the fields that the email team needs
As noted above, the final Jira ticket will often link out to two more content pages that contain the draft copy/ assets for the email as well as the final copy/design once the email is sent. On the draft Confluence page, an email requester will typically include the following elements:
Along with the ultimate design of the email, the final Confluence page will include the following information, and is often commented on by a larger group:
The final page also includes a checklist that ensures the email's design + copy are up to standard:
Note: The team also uses Calendars to display what emails are scheduled for the days, weeks and months to come. Each Calendar event is linked to a Jira ticket and includes publish date/time. When a day reaches its send quota, an alert shows that says, “Full Calendar, no new requests."
Questions about the products or process that the Atlassian Email team uses? Ask them in the comments below!
Hey there! When you can pack so much information onto a Confluence page, it can be challenging to whittle down what’s most important. Here are a few of our favorite hacks for finding need-to-know i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events