We've added two in context safeguards to the Contact Tag trigger to prevent the most common configuration mistakes and protect users from unexpected workflow behavior.

What's New

Retroactive Enrollment Info Banner

When a tag is added to the Contact Tag trigger, a subtle info banner now surfaces to clarify that the trigger only applies to tags added after the workflow is published. The banner links directly to the retroactive enrollment guide, where users can follow the steps to bulk import existing tagged contacts into the workflow.

No Filters Warning

If a user attempts to save the Contact Tag trigger without configuring any filters, a warning now surfaces explaining that the workflow will trigger for every tag added or removed across all Contacts, which may cause unexpected behavior. The warning offers two clear paths forward:

• Add Filter (primary CTA) — returns the user to filter configuration
• Save without filters — preserves the option for advanced use cases

How It Works

Retroactive Enrollment Info Banner

• Appears when a tag is added inside the Contact Tag trigger filters
• Includes a link to the retroactive enrollment support article
• Dismissible via the close icon. Once dismissed, it will not appear again for that user
• If not dismissed, it follows a frequency cap of 3, after which it stops appearing automatically

No Filters Warning

• Triggered when the user attempts to save the Contact Tag trigger with zero filters configured
• The Add Filter CTA returns the user to filter configuration
• The Save without filters CTA preserves the option for advanced use cases

Why This Matters

• Reduces confusion around post-publish trigger behavior by setting clear expectations upfront
• Prevents accidental workflow runs across the entire contact base
• Surfaces the retroactive enrollment path right where users need it, instead of leaving it buried in documentation
• Keeps power users unblocked by making every guardrail dismissible or overrideable

We've added two in context safeguards to the Contact Tag trigger to prevent the most common configuration mistakes and protect users from unexpected workflow behavior.

What's New

Retroactive Enrollment Info Banner

When a tag is added to the Contact Tag trigger, a subtle info banner now surfaces to clarify that the trigger only applies to tags added after the workflow is published. The banner links directly to the retroactive enrollment guide, where users can follow the steps to bulk import existing tagged contacts into the workflow.

No Filters Warning

If a user attempts to save the Contact Tag trigger without configuring any filters, a warning now surfaces explaining that the workflow will trigger for every tag added or removed across all Contacts, which may cause unexpected behavior. The warning offers two clear paths forward:

• Add Filter (primary CTA) — returns the user to filter configuration
• Save without filters — preserves the option for advanced use cases

How It Works

Retroactive Enrollment Info Banner

• Appears when a tag is added inside the Contact Tag trigger filters
• Includes a link to the retroactive enrollment support article
• Dismissible via the close icon. Once dismissed, it will not appear again for that user
• If not dismissed, it follows a frequency cap of 3, after which it stops appearing automatically

No Filters Warning

• Triggered when the user attempts to save the Contact Tag trigger with zero filters configured
• The Add Filter CTA returns the user to filter configuration
• The Save without filters CTA preserves the option for advanced use cases

Why This Matters

• Reduces confusion around post-publish trigger behavior by setting clear expectations upfront
• Prevents accidental workflow runs across the entire contact base
• Surfaces the retroactive enrollment path right where users need it, instead of leaving it buried in documentation
• Keeps power users unblocked by making every guardrail dismissible or overrideable

We've added two in context safeguards to the Contact Tag trigger to prevent the most common configuration mistakes and protect users from unexpected workflow behavior.

What's New

Retroactive Enrollment Info Banner

When a tag is added to the Contact Tag trigger, a subtle info banner now surfaces to clarify that the trigger only applies to tags added after the workflow is published. The banner links directly to the retroactive enrollment guide, where users can follow the steps to bulk import existing tagged contacts into the workflow.

No Filters Warning

If a user attempts to save the Contact Tag trigger without configuring any filters, a warning now surfaces explaining that the workflow will trigger for every tag added or removed across all Contacts, which may cause unexpected behavior. The warning offers two clear paths forward:

• Add Filter (primary CTA) — returns the user to filter configuration
• Save without filters — preserves the option for advanced use cases

How It Works

Retroactive Enrollment Info Banner

• Appears when a tag is added inside the Contact Tag trigger filters
• Includes a link to the retroactive enrollment support article
• Dismissible via the close icon. Once dismissed, it will not appear again for that user
• If not dismissed, it follows a frequency cap of 3, after which it stops appearing automatically

No Filters Warning

• Triggered when the user attempts to save the Contact Tag trigger with zero filters configured
• The Add Filter CTA returns the user to filter configuration
• The Save without filters CTA preserves the option for advanced use cases

Why This Matters

• Reduces confusion around post-publish trigger behavior by setting clear expectations upfront
• Prevents accidental workflow runs across the entire contact base
• Surfaces the retroactive enrollment path right where users need it, instead of leaving it buried in documentation
• Keeps power users unblocked by making every guardrail dismissible or overrideable

The Drip action has been upgraded with a set of transparency and reliability improvements, giving users full visibility into how their drip schedules will run and ensuring pacing is preserved across workflow state changes.

What's New

Drip Preview

A live schedule preview is now available inside the Drip action during configuration. Users can see exactly when each batch is projected to run before publishing.

• Batch table displaying batch number and scheduled send time, with up to 10 batches previewed
• Inline warning surfaced when a Workflow Time Window is active, so schedule conflicts are caught before publishing: "Workflow time window (8 AM – 7 PM, Mon-Tue-Wed-Thu-Fri) is shifting some batches to the next available slot." The time window is a clickable link that opens the relevant setting directly.
• The preview is shown during first-time setup and is hidden when contacts are already queued in the drip, keeping the editing view clean

Action Statistics, Batch Schedule & Insights

The statistics icon on the Drip action has been redesigned as a proper, discoverable button. Clicking it opens a detailed view of everything happening inside the drip.

• Summary cards showing contacts currently in the drip, next batch details, and ETAs
• Full batch schedule table with every batch, its scheduled send time, and any active constraints affecting timing
• Time Window setting surfaced directly inside this view, with a redirection link to jump into the setting without leaving the screen
• Status column, pagination, and existing capabilities (move to next step, delete, contact hyperlink) consolidated in one place
• When drip settings are edited on a workflow with contacts already queued, a clear note clarifies that updated settings will apply only to new contacts entering the workflow

Batch Size Change Warning

When batch size is updated on a previously published workflow with contacts already queued, a soft blue informational note is shown:

"Note: Contacts already queued in this drip will use the previous batch size. New contacts will use the updated batch size."

This appears only when the workflow has been published at least once and contacts are actually present in the Drip action, keeping the message relevant and non-intrusive.

Auto-Pause on Draft, Auto-Resume on Publish

When a workflow moves from Published to Draft with contacts queued in a Drip action, those contacts are now paused for the full duration the workflow remains in Draft. Once republished, the drip resumes from where it left off instead of bursting all queued contacts out at once, preserving the original pacing and protecting sender reputation.

Drip Narration on Hover

A tooltip now appears on hover of the Drip action (similar to the Wait step), allowing users to read the full configuration without opening the action. Examples:

• "Batches of 100 contacts, every 5 minutes"
• "Batches of 1.5K contacts, every 30 minutes"

Updated Field Tooltips Inside the Drip Action

Tooltips on the individual fields inside the Drip action have been refreshed with clearer descriptions and examples, so users can understand what each field does directly in context.

Why This Matters

Drip schedules previously behaved in ways users couldn't easily explain, driven by three recurring gaps: 1)Active Workflow Time Windows silently shifting batch times

2)Mid-run setting changes applying only to new contacts without clear indication.

3)Workflows toggling between Published and Draft causing queued contacts to burst out all at once.

This release closes those gaps by surfacing constraints directly in the product, preserving drip pacing across publish state changes, and delivering reduction in guesswork around drip scheduling.

Good to Know

• The schedule preview shows a maximum of 10 batches; if fewer exist, all are shown
• The preview is hidden while editing a Drip action that already has contacts in it
• The batch size warning only appears on workflows that have been published at least once and currently hold contacts in the drip
• The "settings apply to new contacts only" note is shown only when drip settings are edited on a workflow with contacts already queued

We’re excited to introduce Nested Folders, a powerful new way to organize your assets across Campaigns, Templates, and Sequences.

✅ What’s New

You can now create subfolders within folders, allowing for a more structured and scalable organization system. Whether you're managing multiple clients, campaigns, or content types, nested folders make it easier to keep everything neatly arranged.

🔐 Key Benefits

• Improved Organization – Group related assets into hierarchical folder structures

• Better Navigation – Quickly locate campaigns, templates, or sequences without clutter
• Scalable Structure – Ideal for agencies and teams managing large volumes of assets
• Consistent Workflow – Apply the same folder logic across Campaigns, Templates, and Sequences

🎯How It Works

• Create a folder as usual
• Click on New Folder inside a folder view
• Move items to the nested folder

• The folder path would confirm the nesting/ structure

💡Note: This release supports more than 5 layers of nesting as well for better organisation.