Work schedule

Overview

The Business Hours Verification Component is a clock-based conditional flow control node. Its main function is to intercept the customer journey and validate whether the exact moment of execution matches the business hours registered in the platform ecosystem. It acts as an automated path divider, ensuring that interactions receive different handling depending on the company's operational availability.

Configuration Parameters

The component configuration is lean and directly tied to the global definitions of the work environment:

• _Work Hours ( Required Field):_* Drop-down menu for selecting a preexisting schedule. The component does not store the hours locally; it performs a lookup and inherits the rules (days of the week, shifts, start and end times) that were previously configured in the workspace settings of the platform.

• Holidays (Toggle Switch Key): When enabled, the automation also begins to consult the holiday calendar associated with the workspace. If execution occurs on a day considered a holiday, the system will automatically classify the moment as outside business hours, even if it falls on a standard business day.

Visual Builder

The builder focuses on simplicity of configuration and data inheritance intelligence:

• Centralized Binding: The selector eliminates the need to retype schedule tables within each automation flow, allowing changes to the workspace schedule to update all orphaned components simultaneously.

• Conditional Output Mapping: Unlike linear action components, this node's interface visually changes the block structure in the flow editor, providing two physical output ports for branching connections:

  • Output A: Within business hours

  • Output B: Outside business hours

Special Operators

The logical properties of this component handle timezone synchronization and dynamic calendar processing:

• Local Timezone Resolution: The component evaluates the time based on the timezone defined in the workspace's general properties (e.g., America/Sao_Paulo), ensuring that cloud server time zones (usually in UTC) do not distort the business hours validation.

• Boolean State Evaluation: The flow engine processes this component in an instant binary manner. It captures the current timestamp, runs the validation function against the selected workspace matrix, and returns an immediate routing without keeping the user in waiting queues.

Practical Examples

The table below demonstrates classic use cases for this component to isolate and structure support flows:

Work Hours	"Holidays" Key	Output Triggered on Fire	Practical Use Case
Commercial Support	Enabled	Within business hours	Monday, 2:00 PM (normal business day). The flow continues to the human handoff component.
Commercial Support	Enabled	Outside business hours	Monday, 9:00 PM. The flow diverts to an absence message, informing the service hours and ending the cycle.
Technical On-Call	Disabled	Within business hours	Tuesday, 1:00 AM (configured as on-call hours). The system triggers the alert for the engineering team.
Commercial Support	Enabled	Outside business hours	Wednesday, 10:00 AM, but on a National Holiday. The flow blocks sending to humans and triggers the time-off response.