IVR Node: Schedule

The Schedule node branches the call flow based on the current time: business hours, after hours, or holiday. It's the typical building block for "if it's business hours, route to an agent; otherwise, leave a voicemail".

Requirements

• A Calendar created under Settings → Calendars (with days, hours, and holidays), or at least the workspace's general business hours set under Settings → General.
• If neither a calendar nor general hours are configured, the node defaults to out-of-hours (so a misconfigured IVR doesn't accidentally answer more than it should).

Configuration

• Calendar: choose "Workspace default business hours" or a specific calendar created for this flow (Settings → Calendars).
• Each calendar defines active days, opening/closing time per day, and a list of holidays.

Edges (outputs)

• in_hours: the call arrives within the configured hours.
• out_hours: outside hours (includes weekends or disabled days).
• holiday: if you wire this edge, dates flagged as holidays in the calendar go here instead of out_hours (optional).

Example

A sales IVR uses Schedule with the calendar "Quito hours, Mon–Fri 09:00–18:00": the in_hours edge goes to Route to sales team, out_hours goes to Voicemail, and the holiday edge (national holidays) goes to a special "closed for the holiday" message.

Tips

• If you have multiple locations or timezones, create one calendar per location instead of relying on the single workspace-wide default.
• Schedules that cross midnight (e.g. 22:00 to 02:00) are supported correctly.

Troubleshooting

If calls always fall to out_hours even during business hours, first confirm that the Calendar assigned to the node actually exists and belongs to the right workspace. Careful: if the assigned calendar was deleted or belongs to another workspace, the node does not automatically fall to out-of-hours — it falls back to the workspace's general business hours (Settings → General), and if those general hours say it's currently business hours, the call still follows in_hours, even though the specific calendar is broken. The node only defaults to out_hours by design when there is absolutely no calendar and no general hours configured at all (to make that misconfiguration visible). If you suspect a misassigned calendar, check it directly under Settings → Calendars instead of assuming the node will block the call for you.