🕒 Control of shipments with the "Time Window"
Ensuring that your customers receive messages at an appropriate time is essential to maintain a good experience and protect your brand's reputation. To avoid sending messages in the early morning or on non-business days, FlowBuilder has the Time Window function within the Wait Time component.
This setting allows you to define strict timing rules before a message is triggered:
Time range: Select a start and end time (e.g. 8:00 AM – 5:00 PM).
Active days: Choose which days of the week sending is allowed (e.g. Monday to Friday).
Time zone: The system will respect the time zone configured in Settings > My Company.
How does it work? If a contact enters the flow outside the allowed window (for example, at 3:00 AM), the component will stop their progress and the system will automatically wait until the next valid period to continue with the sending.
🔀 Advanced logic in Outbound Flows
In your outbound flows with triggers (Webhooks, Dynamic Lists, or Typification), you are not required to connect the start directly to a Template. You have complete freedom to insert any FlowBuilder component in between, allowing you to create complex flows, transform data, and personalize the experience before final delivery.
💡 Practical use cases
By chaining multiple components before your Template, you can solve scenarios such as:
A/B Testing (Conversion testing):
Structure: Trigger → Conditional → Template A / Template B
Use: Bifurcate your contacts using a Conditional component to test which template version generates more responses or conversions.
Data enrichment and cleaning:
Structure: Trigger → Format → Template
Use: Use the Format component to clean a name or transform data from your CRM (Webhook) before injecting it as a dynamic variable in the template.
Time control + Personalization:
Structure: Dynamic List → Wait Time (Time Window) → Conditional → Template A/B
Use: You ensure that the contact receives the message only during business hours and, in addition, you send them hyper-segmented content based on their data.
⚠️ Note about data evaluation: The system engine executes each node sequentially. If you place a Conditional before the templates, the system will evaluate the rules and send the contact down the correct branch, ensuring that results tracking (read, delivered, replied) is captured accurately on the first template they touch.
🛑 Restrictions and important considerations
To ensure your automations work without conflicts, keep in mind the following operational rule:
Campaigns with Template trigger: If the start of your flow is a Template (direct campaigns), it is not allowed to use the Wait Time component with "Time Window" afterwards.
Reason: Time control, time zone, and batch sending of campaigns is configured at the campaign level itself. Attempting to add an extra time node would create an overlap of rules (e.g. the campaign says to send at 10:00 AM, but the node says to wait until 2:00 PM). If you try to connect it, the system will indicate to you through a message that the sending configuration should be set at the time of creating the campaign.
Take full control of your outbound flows! 🚀
By mastering time windows and component chaining, you ensure that your contacts receive highly personalized messages, with clean data and, most importantly, always respecting your business's business hours. ✅