Time condition
Routes the call based on the day and time. Each declared window creates its own output: the lunch break goes somewhere different from the evening closing, without stacking two modules.
At a glance
| Outputs | one per declared window, plus Within hours and Outside hours |
| Fields | per window: start and end hour and minute, days of the week, days of the month, months |
| Time zone | that of your installation, set in Settings |
How it works
You add as many windows as you want. Each window creates its own output in the editor, labeled with its content, for example mon-fri 08:30-12:00. You connect each one where it should go.
Two additional outputs always exist:
- Within hours is taken when the call falls within at least one window whose own output isn't connected to anything. It's a convenient fallback when all your windows lead to the same place: connect only this one and leave the others unconnected.
- Outside hours is taken when no window matches.
Order matters: it's the first matching window whose output is connected that wins. The following ones are not evaluated.
What to fill in
| Field | What's expected | If you leave it blank |
|---|---|---|
| Hour and minute | the window's start and end, on a 24-hour basis | the window covers the entire day |
| Day of the week | Monday through Sunday, as a range | every day |
| Day of the month | a date or a range, for example 24 to 25 | every date |
| Month | a month or a range | every month |
Step by step
- Place the Time condition module and connect the previous node to its input.
- Open it and declare your first window, for example Monday to Friday from 8:30 AM to 5:30 PM.
- Add one window per purpose: opening hours, the lunch break, closing days.
- Close the window. The module now shows one output per window, plus the two fallback outputs.
- Connect each output to its destination: the welcome menu, a lunchtime announcement, voicemail.
- Connect Outside hours, otherwise a night call will be hung up without a word.
- Click Apply changes, then call your number to check.
If it doesn't work
All calls go to Outside hours even though they fall within business hours. Check the time zone in Settings. Then check that the window actually covers the day of the week being tested: a window limited to Monday won't respond on a Tuesday.
The call is hung up without a word outside business hours. The Outside hours output isn't connected to anything. A module whose triggered output leads nowhere ends the call. Connect it to an announcement or to voicemail.
My lunch window is never taken. Another window that also matches is declared before it, and the first connected one wins. Move the lunch window up, or narrow the morning window so they don't overlap.
December 24 and 31 aren't taken into account. Fill in both the day of the month and the month. A date alone applies to every month of the year.
How the call flow is built, explained in pictures
See the Dial plans page