Answer team questions, send notes, open channels. Every one is ready to run, and you can adjust it in plain language.
Share newly published articles with interested readers each week.
Your weekly newsletter shares new articles that fit readers' interests, with links and send results ready for your review.
Draft the audience newsletter from contributor updates for review.
You get a themed Monday newsletter draft from contributor emails, without repeated news. Review uncertain details before you send.
Draft a staff newsletter from checked department updates.
Your weekly internal newsletter draft arrives ready to review, with source links beside staff updates and questions about unclear submissions.
Email stakeholders key changes and actions from approved release notes.
Your stakeholders get key changes and action items by email, with a link to the full release note page.
Email stakeholders the finished note from an approved release brief.
Your stakeholders get release notes in your team's format, and the release owner gets a copy of the sent note.
Shape chapter submissions into a readable member newsletter draft.
Your weekly member newsletter comes together from chapter emails, with unclear details flagged for your review before you send it.
Send each employee relevant news and flag unclear announcements.
Your team gets the updates that matter to them, while you get every department version and a clear send report.
Explain shipped changes to the teams who speak with customers.
Your customer-facing teams get a clear release update, while your launch owner gets the sent email and recipient list.
Keep stakeholder release emails aligned with the published summary.
Your stakeholders get clear release notes with dates and links from the published summary. Engineers see the exact email that went out.