Schedules

How it works

1. The module can have several outputs: one per period you configure (open, closed, on-call, and so on)
2. Set the days of the week, Monday to Sunday, each with its own hours
3. Give every day its opening and closing time
4. Add extra periods, such as on-call duty or a lunch break, each with its own output
5. When a call comes in, the system checks the current day and time
6. The call leaves through the output matching the active period: 'open' between 9am and 6pm, 'closed' outside those hours
7. If no period matches, the call leaves through the default output

Use cases

• Run a company's opening hours, routing to a different dialplan depending on the time
• Play a recorded message outside business hours, through the 'closed' output
• Turn on an on-call service during set periods, through the 'on-call' output
• Change routing by day of the week: different hours on Saturdays
• Handle the lunch break with an output of its own
• Build complex schedules with several periods inside the same day

What you configure

Days of the week

The days these hours apply to: Monday, Tuesday, Wednesday, and so on. Each day can have its own hours.

Opening time

When the "open" period starts, in HH:MM (09:00, for instance). Between this time and closing time, calls leave through the "open" output.

Closing time

When the "open" period ends, in HH:MM (18:00, for instance). After it, calls leave through the "closed" output.

On-call period

An optional period with hours of its own (Saturday 10am to 2pm, for instance) routing to the "on-call" output.

Examples

• A company open Monday to Friday, 9am to 6pm, closed at weekends
• Customer service with on-call cover on Saturdays, 10am to 2pm
• A shop whose hours change from one day to the next