N
member badge
Norhan Eid from SleekFlow
The current Broadcast module is too limited for customers running large-scale, automated engagement programs.
Today, broadcasts primarily follow a simple workflow:
Select contact list
Select template
Send or schedule
For more advanced use cases, customers are forced to move into FlowBuilder because Broadcasts do not support dynamic audience management, trigger-based sending, or recurring automated campaigns.
This creates several challenges:
  • Increased Flow Builder complexity.
  • Higher maintenance overhead.
  • Excessive use of flows for use cases that are fundamentally campaign/broadcast activities.
  • Additional MAC consumption as contacts must enter flows to receive automated outbound communications.
Requested Enhancement:
Expand the Broadcast module to support advanced automation capabilities, including:
Dynamic Audiences
  • Automatically updated recipient lists based on contact properties, labels, lifecycle stages, custom objects, or segmentation rules.
  • Dynamic inclusion/exclusion criteria.
Recurring Broadcasts
Daily, weekly, monthly, and custom recurring schedules
Automated re-send logic based on audience conditions.
Trigger-Based Broadcasts
  • Send broadcasts when a contact meets specific criteria.
  • Send broadcasts based on lifecycle stage changes.
  • Send broadcasts based on labels, custom object updates, or contact property changes.
  • Send broadcasts after a defined period of inactivity.
Campaign Journey Automation
  • Ability to create lightweight campaign journeys for engagement and re-engagement use cases.
Business Impact:
Many outbound marketing and customer engagement scenarios do not require a full FlowBuilder journey.
A more powerful Broadcast module would:
  • Reduce operational complexity.
  • Improve scalability.
  • Reduce reliance on Flow Builder for campaign automation.
  • Provide a more intuitive experience for marketing and lifecycle teams.
  • Better support enterprise-scale outbound programs.
Customer Example:
MVF currently uses FlowBuilder for many automated outbound campaigns because Broadcasts cannot support dynamic audiences, recurring sends, or trigger-based execution. These use cases would be more naturally managed within an enhanced Broadcast .module.