Quotient Changelog: September 14, 2026

This release is about shortening the distance between something happening in Quotient and the person who needs to respond. You can now send a personalized Slack message directly from a Flow. We also made agent activity easier to scan, first drafts more complete, and a few everyday content and audience workflows faster.

Send the right message to Slack, straight from a Flow

Flows can now send personalized messages to a Slack channel or an individual workspace member. Add the new Send Slack Message step, choose a destination, and write a Slack-formatted message using Quotient variables.

That means campaign activity, customer follow-up, approvals, and internal alerts can reach the right place without a custom HTTP request or a webhook someone has to keep alive. The step uses your existing Slack integration, can join public channels when needed, and points you in the right direction if Slack needs updated permissions.

Cleaner agent activity

Long agent runs now stay easier to follow without taking over the conversation. Thinking summaries, searches, and routine asset work appear as compact activity you can expand when you want the details. Finished output remains front and center, while generated images, screenshots, errors, and moments that need your input stay visible on their own.

Other improvements

• More complete first drafts: New documents and blog posts now begin as substantive drafts when practical, rather than outlines that need an immediate second pass.

• Faster list updates: Quick Add now lets you select several existing subscribers at once. People already on the list are skipped, and list-triggered Flows only run for people who were actually added.

• Faster blog library: The blog list now loads lightweight summaries and supports pagination, so larger archives open faster and posts beyond the first 50 remain easy to reach.

Fixes

• Paste images into rich-text fields: Screenshots and photos copied from webpages and desktop apps now reliably embed in campaign briefs, task descriptions, audience notes, and comments, while non-image rich content such as tables keeps its normal paste behavior.

As always, let us know what would make Quotient fit more cleanly into the way your team already works.