Time Conditions — Schedules That Drive Call Routing
A time condition is a named schedule — days and hours — that routes test against the current time. Routes evaluate their conditions top-down and the first match wins, which makes ordering a design tool: specific windows (lunch, holidays) sit above general ones (business hours), with the all-times catch-all last.
Creating conditions
- Features → Time Conditions → Create New.
- Name for intent: "Weekday-Business-Hours", "Saturday-Half-Day" — a condition named "TC2" will outlive everyone who remembers what it does.
- Define day-of-week and time ranges. Split schedules (8–12 / 13–17) are two ranges in one condition.
- Reuse conditions across routes — one "Business Hours" shared everywhere means one edit when hours change.
The evaluation model
Priority | Condition | Effect |
|---|---|---|
1 (top) | Holiday list | Intercepts everything on listed dates |
2 | Lunch window | Intercepts midday |
3 | Business hours | The main daytime path |
last | All times | Catch-all = after hours, weekends |
Timezone follows your account setting — multi-timezone organizations should confirm each site's routes reference schedules expressed in the site's local reality.
Testing boundaries
Change a schedule, then call the number at both sides of a boundary (a minute before and after opening). Schedule bugs are boundary bugs — the middle of the day always works.
Related articles
Last reviewed August 6, 2026. Still stuck? Contact Signal Support from your portal — include what you expected, what happened instead, and one example phone number or extension.