Use Case
Run a weekly changelog campaign

Keep your users informed about product improvements with a recurring multi-channel campaign — blog post, email broadcast, and social posts that showcase momentum and keep your audience engaged.
How it Works
Before you start
This use case works best when you've already set up some foundational elements in Quotient:
- Knowledge Store populated: Add your product overview and brand voice so the agent can describe features in language that's consistent with your positioning.
- Email template created: Set up a reusable changelog email template so each week's broadcast starts from a consistent design. The Email Agent can help you build one.
- Social accounts connected: Connect your LinkedIn and X accounts so social announcements can be published directly from Quotient.
How to do it in Quotient
1. Start a conversation with the Campaign Agent
Open a new chat and describe the changelog campaign. Share the features and updates you want to highlight. For example:
"Create a changelog campaign for our weekly product updates. The campaign should include a blog post summarizing new features and improvements, an email broadcast to all active users, social media posts on LinkedIn and X highlighting the key updates, and follow-up tasks to coordinate in-app notifications."
2. The agent creates the campaign and deliverables
The Campaign Agent creates a campaign with tasks for each channel — blog post, email broadcast, and social posts (typically company + personal accounts on both LinkedIn and X). It writes a brief that captures the key updates and messaging angle for the week.
3. Provide the details
Share the specifics of what changed this week:
- "Here are the 3 main features we shipped — [describe each one]"
- "Include screenshots of the new dashboard — I'll upload them"
- "We also fixed a few bugs — list those in a separate section"
- "The marquee feature is the new analytics view — lead with that"
4. Review and publish
Review the blog post and email, then approve for publishing. The social posts should go out after the blog is live so there's a link to share. For automation, create an Agent Job that runs weekly and creates a campaign (brief with this week's updates — you can provide the feature list in the job prompt or when it runs) and adds tasks for the blog post, email broadcast, and social posts. Review the campaign and kick off the tasks each week.
What you'll get
A typical changelog campaign includes:
- Blog post — concise, scannable summary of features and improvements with screenshots
- Email broadcast — mirrors the blog content, sent to active users and subscribers
- Company social posts — LinkedIn and X posts from the company account highlighting key updates
- Personal social posts — LinkedIn and X posts from founders sharing their perspective on the updates
- Bug fixes section — transparent list of resolved issues when applicable
Tips for better results
- Be concise. Changelogs should be scannable, not essays. Lead with the 2-3 most important updates and keep descriptions to 1-2 sentences each.
- Lead with user value. "You can now export reports in one click" is better than "We added an export button." Frame every update in terms of what it means for the user.
- Include visuals. Screenshots and short recordings make changelogs dramatically more engaging. Provide these to the agents when possible.
- Make it a habit. Consistency builds trust. Whether it's weekly or bi-weekly, stick to a regular cadence so users know when to expect updates.
- Use personal voices for social. Founder posts about product updates consistently outperform company posts. Include personal perspectives on why each feature matters.
Get Started
Create a changelog campaign for our weekly product updates. Include a blog post summarizing new features and improvements, an email broadcast to all active users, and social posts on LinkedIn and X highlighting the key updates. I'll share the specific features we shipped this week.