Skip to content
Thirdlane

Schedules

A Time Range Group (Schedule) is a named set of date and time ranges - for example “business hours” or “holidays” - that the system can check against the current time to decide when something applies. You define a schedule once here and then reuse it as a time-based condition wherever the system needs to behave differently at different times: Inbound Routes, Routing Conditions, and end-user features in Thirdlane Connect and the User Portal.

This keeps time logic in one place: change your business hours once and every route and condition that references the schedule updates with it. A schedule matches when any of its time ranges matches the current time.

Create/Edit Time Range Group

Name. Alphanumeric unique Time Range Group name.

Descriptive name. Short user-friendly name of the Time Range Group.

Description. Time Range Group description.

Hide from end users. Specify whether this Time Range Group should be hidden from the end users in Thirdlane Connect and User Portal.

Using “Add” button you can add multiple Time Ranges, as many as you need.

Note that when defining Time Ranges an '' specifies ‘any’, so for example leaving month and Day-of-Month as '' and selecting from Monday to Friday would mean that the time range will be true Monday through Friday regardless of the month. Specifying the same Day-of-Week range and also selecting January in the “from” Month would mean ‘Monday through Friday in January’, etc.

Example

A typical “business hours” schedule has a single time range: Monday through Friday, 09:00-17:00, with month and day-of-month left as *. A “holidays” schedule instead uses one or more ranges pinned to specific months and days (for example December 25) with the time left open, so the whole day matches.

Best practices

  • Define business hours and holidays as separate schedules and combine them at the route level (put the holiday rule above the business-hours rule) rather than trying to encode every exception into one schedule.
  • You do not need an explicit “after hours” schedule - use the built-in All-hours (default) condition as the final catch-all in a route so anything that does not match business hours or holidays falls through to it.
  • Give each schedule a clear Descriptive name; that is what appears when someone picks a condition in a route, and it is what end users see in Connect and the User Portal unless you Hide from end users.
  • Remember schedules are evaluated in the timezone set on the Inbound Route - confirm the route timezone matches the location the schedule is meant for.